(→Site design) |
|||
| Line 10: | Line 10: | ||
The current status can be found [[Application developer site/Status | here]]. | The current status can be found [[Application developer site/Status | here]]. | ||
| + | |||
| + | == Tasks == | ||
| + | |||
| + | Bugzilla tasks: [[http://bugs.meego.com/buglist.cgi?quicksearch=developer.meego.com][Developer.MeeGo.Com from bugzilla]] | ||
== Content Description == | == Content Description == | ||
Contents |
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.
Bugzilla tasks: [[1][Developer.MeeGo.Com from bugzilla]]
The content description can be found from here.
The process used to develop the site can be found here
The original schedule is to have an initial site ready for Nokia Developer Summit, and Intel Developer Forum in mid-September. This is to benefit from any publicity about MeeGo arising from these events.
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.
... People working on the project full-time funded by Nokia...
... People from the community involved in this project .....
The [[DeveloperEngagement | Developer Engagement Framework].