I am considering adding wiki pages in a heirarchy, e.g.,
wiki/program/doc/a
wiki/program/doc/b
wiki/program/doc/c
wiki/program/options/a
wiki/program/options/b
wiki/program/options/c
or some such arrangement. Part of this is that I want to do things like
use the Include macro to include, say, wiki/program/options/a in
wiki/program/doc/a. One reason for this is that some parts are generated
by a program, and some by users. This layout allows me to change them
independently. The exact reason, nonetheless, it not the real issue.
The Page Template part of the wiki is what lead me down this path: it
uses a hierarchy in the wiki name space. Perhaps that is not generalized
to all pages? Like how the pages are listed in the Index.
Two questions:
1) Any obvious cons to this? Or better ways to get a hierarchical
organization? I had tried names, like ProgramDocXa, ProgramDocXb,
ProgramOptionsXa. But this was not to local tastes.
2) Should it be possible, with trac-admin, to include wiki pages that
are in a directory hierarchy and have that hierarchy be maintained in
the wiki pages, as described above? I think the 'wiki load' command only
takes files from the current directory and places them in project/wiki.
I am considering moving some program documentation from OpenOffice docs
into a trac wiki. Printed versions are to be done via the
TracWikiPrintPlugin.
Anyone else gone this route?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
