Andreas Hartmann wrote:
Bob Harner wrote:
[...]
As usual I may not be following all the subtleties of this discussion,
but the fallback mechanism seems to me a very good thing to apply to
content, if done properly. Yes, shared resources *should* be managed
by the GUI (!), and the obvious implementation would be to have a
special publication, maybe called "shared" or "global" or something,
that contains that content. Then those people with permission to edit
content for that special publication could use the GUI to manage the
shared content just like the content of any other publication. The
fallback mechanism should be used to let individual publications
override such shared content. This would be a beautiful thing if done
properly.
This raises the issue of addressing documents. At the moment,
content-related fallback would certainly be based on the document ID:
- look in <mypub> if document /foo/bar:en exists
- if not, look in <sharedpub> if document /foo/bar:en exists
- if not => 404
But how would it work with UUIDs?
----
Actually I don't like this very much, because website editors are
confronted with the fallback concept (which should IMO be a purely
internal concept).
I'd rather allow to include content from other publications (e.g., from
the shared publication) explicitly.
+1
can't xinclude be used for this
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
