Return to the main archive index.
Mandrake Linux: cooker@mandrivalinux.org
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
I'm regulary ennoyed by the way the wiki turns into a giant flat collection of individual pages with too few relationship (apart insane crosslinking to my-own-page-that-is-really-really-important). It leads to duplicated content as new writer prefer to start a new page rather than try to think about where to put what they need to say, and make impossible for readers to find sensible information excepted by searching for a given topic... Some times ago, I tried some basic reorganisation of content related to packaging, by creating a few topical pages, enforcing a unified naming scheme,and linking all them together directly from the index page. However, this is not enough: see how the new 'Build System' page outside this hierarchy duplicates many content... This is both an organisational issue (we should have topical sections with someone in charge of ensuring coherency) and a technical issue (those sections should be clearly identified, both for readers and writers). I am volonteer for maintaining the packaging section, meaning trying to keep everything related to this issue inside a logical, balanced and clear structure. I was thinking about creating a top-level page for this section, describing this organisation, with a few mention about putting correct content into correct place, and asking me in case of doubt. This top-level page would mostly include links to real content, meaning it would replace the current link block at index page. ooes it makes sense ? And could wiki css-wizards try to design a specific look'n'feel for this kind of structural pages, to clearly distinguish them from content pages ?