Talk:Main Page

This Wiki is for the whole of LEAF. At the moment the focus is on documenting Bering-uClibc 4.x but we need to cater for other LEAF variants- both existing and future. Since a Wiki has a very "flat" structure we need to follow some conventions to separate content which relates specifically to one LEAF variant from other LEAF variants.

For the more formal documentation like the Developer Guide I propose a structured hierarchy of Wiki pages:

• Bering-uClibc 4.x - an "overview" page for Bering-uClibc 4.x
  • Bering-uClibc 4.x - Developer Guide - a "Table of Contents" page for the Developer Guide
    • Bering-uClibc 4.x - Developer Guide - Introduction - a page for the Introduction chapter
    • Bering-uClibc 4.x - Developer Guide - Preparing the Build Environment - a page for the Preparing the Build Environment chapter

and so on. This makes for long page names, but at least the structure is clear, and similar to what we have with the formal Bering-uClibc 3.x documentation (derived from DocBook).

I would also expect a separate page for each Release of each LEAF Branch, e.g.

• Bering-uClibc 4.0
• Bering-uClibc 4.0 - Release Notes
• Bering-uClibc 4.1 - would cover changes from 4.0 etc.
• Oxygen

We will probably also want a page for each Package. We could have a "Package -" prefix (e.g. "Package - shorwall.lrp") but I'm not sure that's any benefit, so maybe just plain shorwall.lrp as the page name? We definitely want a Category called "Category:Package" which will group all the package pages together. The drawback of this is that there is only one page for e.g. shorwall.lrp] for *all* LEAF variants. If there are differences between Bering-uClibc 3.x shorwall.lrp and Bering-uClibc 4.x shorwall.lrp (and there will be!) these will have to be covered on the one page. I think that's OK though. Davidmbrooke 08:57, 20 September 2010 (UTC)