Jörn Nettingsmeier wrote:
[...]
root document in this case means "the page that is displayed by default
in the live area". note that i'm talking about this mystical immutable
root page only for authoring.
That sounds very useful and would probably answer quite a lot of questions.
there is no conceivable reason to ever
want to delete the that, because it has no meaning in live.
perhaps the root document should have different characteristics per
area: in authoring, it should display some informational text similar to
publication.xml,
We could even merge it with the publication.xml (introduction.html) page.
but in live, it should contain a redirect to the first
node in the sitetree. this could be easily done with some pipeline magic
in cocoon.
and my suggestion is not only to fix the "missing /index" problem. it
also ensures that *every* page has a parent, which cleans up the tree
semantics and makes the sitetree overview nicer to use when moving pages
around. right now, iiuc you *cannot* cut a document and paste it as a
first-level document. it will always become a child of your current doc,
because you can't click on "[+]authoring" , where you want the page to be.
That was possible in 1.2, but the implementation was not very clean
because the page you're proposing was missing. Maybe we can really
solve the problem by introducing this "root page".
Do you think you could implement this, or give an estimation
what needs to be done?
Should this issue be addressed before 1.4 is released?
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
