Re: [Cooker] [WIKI] Wiki topical structuration

[Warly]

Guillaume Rousse <Guillaume.Rousse@inria.fr> writes:

> 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...

Yep, I agree, I added this BuildSystem pages because I found it
difficult to access those pages rapidly, and I often paste them for new
maintainers 'must read'.

> 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 ?

I agree with the index-like top level pages.

We should keep most viewed topic easily accessible, though, so I propose
to clear the main index and keep the 5 main sections

Releases / Packaging / Translating / Tools / How to... / Miscellaneous 

Maybe should we merge "Tools" and "How to", I'd like too to add a 'How
to help' entry on the main pages.

I'd like to create a more up to date 'EmergencyContacts' page. It is
right now manually edited, but once the LDAP server will be ready on
kenobi, creating groups automatically inserted into this page would
help, or maybe could we use the bugzilla database to store such groups
information (and sync them to ldap afterwards).

Try to clean and elaborate subsection in each of these topics, maybe
keep the 3 or 4 most important subpages for each sections.

Subsection should be structured the same way, for example the
http://qa.mandriva.com/twiki/bin/view/Main/ReleaseInfo would benefit a
rework to includes more link to each releases info (such as release
notes which are very popular)

-- 
Warly