From Amarok Wiki
I probably should have written this a while back, but either way, here goes.
The wiki is currently in the process of being migrated from the "old" wiki (=shudder=) to a new design as described below.
Contents |
New design
There are two primary changes to how the wiki will be laid out, though both inherit from similar ideas.
Old pages
One of the main problems the Amarok wiki faces is an avalanche of outdated pages. The Amarok wiki is especially unique in that the project took a large turn several years ago, which resulted in nearly the entirety of the wiki becoming obsolete. As this was never cleaned up properly (though attempts were made through the years), the lint has accumulated, and, in some places, has even begun to effect pages that would otherwise be useful, pertinent, and up-to-date.
A primary goal of this cleanup will be to segregate and corral the information related to Amarok pre-2.0 in a well defined page structure.
Two notes of terminology. The group of releases considered Amarok pre-2.0 (primarily Amarok 1.4) will be hereafter referred to as Amarok 1.4 for the sake of simplicity and also as the majority of the pages on this wiki were, at the time of the release of Amarok 1.4, updated to reflect as much. In addition, please note the that terms "page structure" and "directory structure" may be used interchangeably as they represent the same idea, although a wiki has no inherit understanding of a "directory" per se.
The general idea is that the structure of the wiki's main namespace will be recreated underneath the page Amarok 1.4. Graphically, the structure will be similar to the following:
Main:
Amarok 1.4/
Development/
Community/
Promotion/
... etc.
Development/
Community/
Promotion/
... etc.
For example, the page Development/DCOP Functions will be moved to Amarok 1.4/Development/DCOP Functions.
Localisation
Another problem that many projects suffer from is translation rot (borrowed from the term bit rot), and the Amarok wiki is no exception. In addition to this unfortunate, yet inevitable, force of nature, the Amarok wiki's organisation of the translation pages has aided in the downfall of its own translations. The second part of this cleanup will be focusing on improving the layout of the translation pages, the templates used to link to them, and, hopefully, the translations themselves (if only by removing obsolete, and thus confusion-inducing translations). As a point of terminology, the term translation page refers to a page which is a translation of a primary English page on the Amarok wiki (e.g., Main Page/fr would be a translation page, whilst the primary page is Main Page).
Layout
Translation pages will now be identified as such by their page title with a strict generation. All translation pages should reside at a subpage of their primary page, with the subpage name being the translation's language's ISO code (as retrieved from here). For example, a French translation of Main Page should reside at Main Page/fr, and a Japanese translation should reside at Main Page/ja.
Linking
With a strict translation page layout as described above, it will be possible to generate the language bars (such as the one seen at the top of Main Page) programmatically. All translated pages should include the code "{{LanguageBar}}" which will generate a language bar for that page, auto-filled with links to the translations of the including page.
Migration plan
To ease migration, the rollout will happen in (approximately) the following order. Care should be taken to maintain consistency within the wiki whilst carrying out the migration. In addition, steps should be completed agnostic to following steps so as to (hopefully) keep confusion and breakage to a minimum.
- Old pages:
- Move pages clearly relating to Amarok 1.4 to beneath Amarok 1.4
- Update links to the moved pages and delete generated redirects
- Localisation
- Layout
- Move translation pages to their proper places
- Update i18n templates to reflect the moved pages
- Update links to the moved pages and delete generated redirects
- Linking
- Layout