The overall information architecture of the site is contained in the following diagram. Please be aware that although the information architecture looks horizontal, the content in the guides and reference sections will dwarf the other content. Please also be aware, that this is how the information is structured, not how it is presented. For example, the Tools/SDK link will appear in most of the pages on the top level to encourage developers to download the SDK and other tools.
Here is a brief overview of the sections:
An introduction to the MeeGo Developer Ecosystem. This features highlights which can be used to present new applications, news, and other information to spark interest in the MeeGo Developer Ecosystem. It has a section on the community to introduce a new user to the MeeGo community, describe what it is and how it functions. The sections "Top Apps" and "Demos" can be used to present community applications and demonstrations of MeeGo functionality. Finally, the "Ecosystem" section should describe the MeeGo value proposition, and players in the MeeGo ecosystem.
This section contains all the guides relevant to a developer working on the MeeGo platform. It has a section called "Tools" to capture the user manuals for the actual tools used in MeeGo application development. The subsection titles are self-explanatory.
This contains the official MeeGo API reference documents, MeeGo release notes, glossary etc.
This contains links to download MeeGo Tools and SDK.
This contains links to the applicaiton developer forums on forum.meego.com, and can contain community news, feeds, etc. One idea here is to display the latest Forum posts, newest threads etc.
This is a draft architecture for the developer.meego.com site. Feedback can be given in several ways:
Of particular interest opinions on:
Some things can be adjusted on the presentation level, but the information architecture should contain all the information on the site.