I also wonder how important is the subfolders when for example we use Categories which works more like a metatag.
Subfolders help us a lot with just simple organization... particularly in the documentation.
When you have a small topic with only a few Wiki pages, subfolders don't add a lot (ie are not that important), but when you are dealing with a behemoth like the Developer's Guide or the larger documents like the User Guide and BASIC Guide, grouping into subfolders helps the maintainers visualize where they are in the book structure etc.
I have also found that Categories can be forgotten or accidentally deleted. If this happens to a page belonging to a documentation set, it can easily be lost in the thousands of Wiki pages if everything is stored in one big pile... whereas if it is in subpages, it can be easily found again, or discovered during routine maintenance (which is more likely, since noticing random missing info in a large document like the Developer's Guide which is hovering around 1000 Wiki pages is difficult).
Outside of the documentation world... that's up to personal/group choice. Most non-documentation pages stand on their own or belong with just a few associated pages. In this case, a Category is a reasonable choice.
Of course this is all my observations :-) If anyone has a better idea of how to handle something like the Developer's Guide (which is really the driver for all this), and keeping the various translations in line with the source documentation... please speak up.
Ultimately we need to establish some basic and simple guidelines so that: - L10N is manageable for both the translators and the readers. - we can easily identify translations that have been done. - we can easily link from one translated doc to the next. C. -- Clayton Cornell [EMAIL PROTECTED] StarOffice - Sun Microsystems, Inc. - Hamburg, Germany --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
