(categorise) |
|||
| (2 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
Each page to be included in the developer guide should include categories to enable people to find/group it, for example: | Each page to be included in the developer guide should include categories to enable people to find/group it, for example: | ||
| - | * The fact it's a MeeGo SDK documentation page ( | + | * The fact it's a MeeGo SDK documentation page (devguide) |
* MeeGo version it's applicable to (e.g. meego-1.0, meego-1.1, maybe even meego-1.0+) | * MeeGo version it's applicable to (e.g. meego-1.0, meego-1.1, maybe even meego-1.0+) | ||
* Documentation type (e.g. tutorial, use-case, recipe) | * Documentation type (e.g. tutorial, use-case, recipe) | ||
| Line 30: | Line 30: | ||
We don't have to have one navigation system, of course, but grouping the material like this gives people somewhere to start. | We don't have to have one navigation system, of course, but grouping the material like this gives people somewhere to start. | ||
| - | + | == Documentation types == | |
* Tutorials: Longer, narrative-based sets of instructions supporting a particular workflow. | * Tutorials: Longer, narrative-based sets of instructions supporting a particular workflow. | ||
* Recipes: shorter, less narrative, standalone sets of instructions to accomplish a particular goal. | * Recipes: shorter, less narrative, standalone sets of instructions to accomplish a particular goal. | ||
| + | |||
| + | [[Category:Devguide]] | ||
Each page to be included in the developer guide should include categories to enable people to find/group it, for example:
This gives several axes for slicing up the documentation. We'd probably want to use those categories to carve out some very high-level navigation, e.g.
We don't have to have one navigation system, of course, but grouping the material like this gives people somewhere to start.