From the experiences of Apple and Android, we can assume that, if we are successful, there will be many more application developers than platform developers. Their needs will be different, as they are more interested in using APIs than designing them. The audience will consist of both beginners who need simple, clear, tutorials/walkthroughs, and experienced developers more interested in code samples and reference documentations.
The goal of the developer.meego.com site is to present and market the Meego Application Developer offering. This needs to be of high quality on par with other application developer sites (Android, Palm, Drupal, KDE, Apple).
The current status can be found here.
A bugzilla version is available here.
|ID||P||Severity||Status||Summary (50 tasks) ⇒|
|17896||High||normal||ASSIGNED||API References - Restructure API references page|
|18762||High||normal||ASSIGNED||Configuration - Improve and simplify input formats and wysiwyg|
|19516||High||normal||NEEDINFO||Guides - create tree navigation block|
|20407||High||normal||ASSIGNED||API References - add active-trail state CSS to api menu|
|20412||High||normal||ASSIGNED||General - upgrade to latest drupal version|
|16305||Low||major||ASSIGNED||Guides - Suggest new guide page or topic|
|20508||Low||major||ASSIGNED||Broken link on /guides/guidelines/meego-compliance-tools|
|16435||Low||normal||ASSIGNED||Content - packaging video|
|16439||Low||normal||ASSIGNED||OBS / packaging content for DMC|
|19528||Low||normal||ASSIGNED||SDK & Tools - allow for external app store SDK references|
|19530||Low||normal||ASSIGNED||SDK & Tools - define new content type fields|
|19531||Low||normal||ASSIGNED||SDK & Tools - views for tools lists (block and page)|
|19532||Low||normal||ASSIGNED||SDK & Tools - 2 categories for tools (commercial and open source)|
|19534||Low||normal||ASSIGNED||Community - design block for additional community forums promotions|
|19535||Low||normal||ASSIGNED||Community - commercial support|
|19537||Low||normal||ASSIGNED||Publish - app compliance checker|
|19538||Low||normal||ASSIGNED||Publish - - wireframe new section|
|19539||Low||normal||ASSIGNED||Publish - new content type for app store list|
|19540||Low||normal||ASSIGNED||Publish - app compliance checker; front end for app compliance checker|
|19541||Low||normal||ASSIGNED||Publish - app compliance checker; provide web service api for external submission of apps|
|19542||Low||normal||ASSIGNED||Publish - app compliance checker; provide logging of apps status for user|
|19543||Low||normal||ASSIGNED||Publish - app compliance checker; ensure privacy of app status|
|20199||Low||normal||ASSIGNED||Content - Details on setting up an internal OBS for meego|
|20318||Low||normal||ASSIGNED||Broken link on developer.meego.com/guides/deployment/packaging-guidelines|
|20535||Low||normal||ASSIGNED||Broken link on /guides/getting-started/application-development-lifecycle|
|20536||Low||normal||ASSIGNED||Broken links on /guides/samples/qt-quick-examples-forum-nokia|
|20537||Low||normal||ASSIGNED||Broken links on /guides/devices/installing-meego-nokia-n900-external-mmc-card|
|20538||Low||normal||ASSIGNED||Broken links on /guides/getting-started/developing-qt-simulator|
|20766||Low||normal||NEEDINFO||Add additional filters to Guides page|
|6340||Medium||enhancement||ASSIGNED||Developer.MeeGo.Com content process|
|11439||Medium||enhancement||REOPENED||Extra tools - copy deeper content from maemo.org|
|13222||Medium||enhancement||NEW||meego docs search term should lead to our devel guide/corner when published.|
|14757||Medium||enhancement||ASSIGNED||Content - Motivational material/incentives needed|
|3680||Medium||normal||REOPENED||Typos and image problem in UI Design Guidelines - Handset|
|8703||Medium||normal||ASSIGNED||"Getting started" link is broken|
|11787||Medium||normal||ASSIGNED||Content - Detailed architecture should be under guides and not references|
|12681||Medium||normal||ASSIGNED||Content - Define the DMC website roles|
|17364||Medium||normal||ASSIGNED||Guides - Restructure Guides area to provide both a tree view and list view|
|17366||Medium||normal||ASSIGNED||API References - evaluate entire API references workflow and generation|
|19513||Medium||normal||ASSIGNED||Guides - theme/style tabs like meego.com tabs|
|19518||Medium||normal||ASSIGNED||Guides- improve guide node pages|
|19521||Medium||normal||ASSIGNED||API References - refactor API menu navigation so reliance on menu items doesn't exist|
|19522||Medium||normal||ASSIGNED||API References - autocomplete search for functions|
|19524||Medium||normal||ASSIGNED||API References - look at other ways to pull in api docs|
|19525||Medium||normal||ASSIGNED||API References - provide place for commercial tool APIs|
|20224||Medium||normal||ASSIGNED||General - look at different solution to the use of nice-menus for sub-site navigation|
|20227||Medium||normal||ASSIGNED||General - enable breadcrumbs for site navigation|
|20999||Medium||normal||NEW||Guides - add "advanced toggle" to the filter block for all filters below the keyword filter|
|12877||Undecided||major||ASSIGNED||First Stop at Becoming a Hero: A guide for first *non* hello world app on MeeGo.|
All bugzilla tasks/bugs for developer.meego.com.
See bugzilla list above.
The content description can be found from here.
The site should link to the related content listed here.
The proposed content management process is based upon several community roles. These roles must first be defined before introducing the proposed content management matrix.
Note: In the future, this role may also be broken up by content area (example: Guides and tutorials editor, SDK and tools editor) or consist of an editorial team with members spaced over all the major geographic regions.
Analytics manager Responsibilities include:
Process for community-driven content.
|1. Content staged on Wiki as draft||Content creator||Content creator||Content editor||Wiki|
|2. Content drafted and staged on site (content source referenced, eg: Wiki revision referenced)||Content editor||Content creator||Content editor, Concept owner||Content plan, Bugziila, CMS|
|3. Content approved and released||Business owner||Content editor||Content editor, Concept owner||Community||CMS, Bugzilla|
Draft version of the content management process below is as follows. Note: that steps 1-5, 9-10, are for editor-driven content.
This is a highly detailed description based on the Scrum Use Story process, (1-5: Analyze need, prioritize, 6-8: Implement, 9-10:Test). In most cases these steps merged (for example steps 1,3,4,5 could be done in parallel by the Content editor).
(Suggestions on how to improve this, and make it more appropriate to a community driven site are welcome).
|1. Community or user need identified||Stakeholders||Content creator/editor||Concept owner, Analytics manager, Content editor||Community||Survey and other tools as input Bugziila|
|2. Need recorded and classified||Content editor||Content editor||Stakeholders Community||Bugziila|
|3. Business prioritization done||Business owner||Business owner||Concept owner, Content editor , Design owner, Analytics manager||Community||Bugziila|
|4. Effort analyzed for Bugzilla items||Content editor||Content editor||Analytics manager, Design manager||Bugziila|
|5. Site and ecosystem analysis to position content||Content editor||Content editor||Design owner, Concept owner||Bugziila|
|6. Content staged on Wiki as draft (optional)||Content creator||Content creator||Content editor||Wiki|
|7. Content drafted and staged on site (content source referenced, eg: Wiki revision referenced)||Content editor||Content creator||Content editor, Concept owner||Content plan, Bugziila, CMS|
|8. Content approved and released||Business owner||Content editor||Content editor, Concept owner||Community||CMS, Bugzilla|
|9. Site conversion goals reviewed||Content editor||Analytics manager||Concept owner, Business owner||Community||Google analytics|
|10. Need tested (did this change satisfy the need)||Content editor||Content editor||Concept owner, Analytics manager||Business owner, Community||Bugzilla|
About the tools used in the content management process
A wiki version of the information architecture with draft content is available here.
The current site could be enhanced with the following content.
The process used to develop the site can be found here
The original schedule was to have an initial site ready for Nokia Developer Summit, and Intel Developer Forum in mid-September. This has been change to match the schedule of the underlying project, so the site should be available in October aligned with the MeeGo 1.1 release.
The draft information architecture can be found here here. It is open for comments and suggestions.
Some sample wireframe designs will be found here. These are open for comments/suggestions.
The full information architecture and complete wireframe set is available in .pdf here: File:DMC Design.pdf.
Here is the proposed layout and content overview for the homepage, plus footer redesign:
After discussion with the maintainers of www.meego.com and the TSG it was felt that developer.meego.com diverged too much from the www.meego.com look&feel. The designers of developer.meego.com have generated an example of this:
... People working on the project part-time funded by Nokia ...
... People from the community involved in this project .....