Le Jeudi, 3 avr 2003, � 09:29 Europe/Zurich, Tony Collen a �crit :

...Navigation isn't really a concern either,
except for maybe linking to other documents....

By Navigation I mean Forrest tabs and the like, that is "how do users see the docs", something like the table of contents that you suggested. I think this is what you call Organization.


But instead of making more suggestions about this Navigation I'd go for actually implementing one or several (using CVS branches) new versions of the web site with minimal content, just to judge the Navigation (or whatever we want to call it) before inserting more content (which would mostly be copied from the existing docs I assume).

...So perhaps it's not knowing
how documents are rendered/named/whatever in relation to their position in
the CVS tree....

Ok - that's where a sandbox would help too.

...How about a new-docs block or something?  Then when we think they're
'ready', switch them over to replace what's there.

If not a block, let's at least get a new-documentation directory setup...

In view of a possible cocoon-docs repository mapped to the existing src/documentation subtree, I think the new-documentation directory has to be under src/documentation. But let's focus on concepts and goals instead of tools ;-)


-Bertrand

Reply via email to