Structuring DevNet Wiki
This document is meant to be a platform for finding an optimized structure for the DevNet wiki. DevNet wiki relies on categories, tags and full text search to make documents accessible.
What is wrong with categories? There are 2 problems: Categories are a non-sorted tree, like a file system. For documents a sorted tree, like a table of content makes more sense. Moreover page editors do not find enough help to assign a page to an existing category which bears the dangers that categories proliferate.
Therefore here is a suggestion to introduce a fixed table of content: One table of content item should be selected from a list when a new document is about to be created. At the time being a one level table of content is sufficient. However it must be possible to add sub items when needed.
Table of Content
- Database: QtSql
- Qt for ActiveX
- Qt Creator and Qt Designer
- Qt Mobility
- AddIns (Visual Studio & Eclipse)
- Building (qmake, cmake and friends)
For each document a type should also be specified.
- HowTo and Best Practice
- Tips, Tricks and Snippets
- Qt Jambi
- In Foreign Language
Status should be an attribute that can be changed as the document progresses. The attribute should be shown in the document list.
- Work in Progress