From Amarok Wiki
A few proposals regarding the organisation of the wiki. Between using subpages and categories, I probably personally prefer subpages as there would be no need to write a MediaWiki extension to generate breadcrumbs. In addition, it is probably the more maintainable of the two; a quick perusal of Special:AllPages would easily show the pages that are out of place (granted, the category proposal could use Special:UncategorizedPages), and it is probably the one of the two that newcomers would learn/get used to the quickest. Though the two techniques could be used together, I would personally advise against it, as doing such would create twice as much structure, all of which would need to be maintained by hand.
Contents |
Subpages
Using subpages would keep Special:Allpages organised and neat, as well as provide automatic breadcrumb navigation. However, there is no way for a page to show all of its subpages (i.e., without redirecting to, e.g., http://amarok.kde.org/amarokwiki/index.php?title=Special:PrefixIndex&prefix=Development&namespace=0). A possible solution would be to put every page that exists under, say, Development/ in Category:Development, except that that category page would list every page in that category under the heading "D". (Edit: This can actually be remedied by using Category Sort Keys.)
Main: * Amarok 1.4/ # all pre-2.0 pages as subpages here * Community/ # and tagged with Category:Amarok 1.4 * Development/ # structure recreated underneath parent folder * Proposals/ * ... etc. * Community/ * Development/ * Proposals/ # all proposals as subpages here * Rokymotion/
Categories
Another option would be to use categories to create a hierarchical structure by which to organise the wiki. Unfortunately, there is no MediaWiki extension (that I can find and that appears to work) that creates breadcrumbs from nested categories. However, getting a list of every page/sub-category of a particular category is trivial.
Translated pages
Right now, translations of pages are placed under a pseudo-namespace (the language code) and named with a localised title. Though this does have the advantage of grouping all pages in a certain language together in any page list (e.g., Special:AllPages), it has the marked disadvantage of separating every translation of the same page. For example, one effect of this is that there are 4 pages that are supposed to be Georgian translations of Main Page. This system would be fine if it was actively, and aggressively maintained, but as some languages (e.g., Georgian) are rarely touched, it can lead to translated pages being left by the wayside, with no one knowing.
Possible alternative
A possible alternative would be to place the translation of, say, Main Page into ქართული at Main Page/ka (ka is the ISO language code for Georgian). This would result in all translation of the same page being naturally grouped together. A nice side affect is that this would significantly simplify the translation templates (rather than having one per page, a single general template that synthesises the title of the translation pages would be possible; requiring the ParserFunctions Extension). However, such a design would make it more difficult to localise the page titles, as well as get a list of all of the pages translated into a certain language (which could be another use for categories).
Language codes (ISO)
A list of language codes standardly used by MediaWiki is here. This isn't too important, but it would be nice if the capitalisation of the language codes could be consistent (I think lowercase is most common, but don't quote me on that). Some interesting thoughts on translation pages (MediaWiki) here and here.