Comment 5 for bug 114266

We could probably implement most of this *today* using includes. While not ideal, it should work OK and I concede that it'll be less work than writing our own macros...

 1. Create a new 'Tag' wiki page and have the following sub-pages: Tag/SystemDoc, Tag/CommunityDoc, Tag/Unreviewed, Tag/Cleanup
 2. Create a new 'Version' wiki page and have these sub-pages: Version/Feisty, Version/Gutsy etc.
 3. Include these Tag and Version pages where appropriate (see https://wiki.ubuntu.com/Philbull/Test for an example)

An upshot of this approach is that we should be able to search for '[[Include(Tag/SystemDoc' and have all of the pages with that tag appear. Note that we have to miss off the last bracket of the search string because of the way Moin parses it. See https://wiki.ubuntu.com/Philbull, section 'Testing' at the bottom, for an example. We'd need to protect the Tag and Version pages from edits, too.

As for structure, just stick the whole ubuntu-doc tree under Official/$RELEASE or maybe just $RELEASE/. For example, internet.xml would be found at https://help.ubuntu.com/community/Official/Gutsy/Internet. This has the advantage of fully containing all of the system docs and handling different versions gracefully, which should make it easier to maintain or push updates. The path is also quite meaningful, so a Dapper user stumbling on Official/Gutsy/Internet could just edit the URL to be Official/Dapper/Internet.

What do you think?