Meego Wiki
Views

Application developer site

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
m (→Content Description)
(→Content Process: Added content management matrix and community roles)
Line 37: Line 37:
=== Content Process ===
=== Content Process ===
-
There is a need for a content process for control the information on the site.  This needs to allow all parties to contribute in a fair and equal manner, the primary criteria for content should be quality and relevance for application developers.
+
The proposed content management process is based upon several community roles. These roles must first be defined before introducing the proposed content management matrix.
 +
 
 +
'''Concept owner'''
 +
 
 +
Responsibilities include:
 +
* Manage the personas and user journeys across the ecosystem surrounding the site
 +
* Identify main content and capability gaps and needs for these journeys
 +
* Act as the primary advocate for the visitor
 +
 
 +
'''Design owner'''
 +
 
 +
Responsibilities include:
 +
* To ensure the structure and capabilities of the developer.meego.com match the needs of personas and the business/community
 +
* To ensure the site design fits the requirements and tonality of the MeeGo brand
 +
* To ensure business/community and visitor requirements are captured, analyzed and prioritized
 +
 
 +
'''Production'''
 +
 
 +
Responsibilities include:
 +
* Manage delivery of capabilities according to prioritized requirements
 +
* Packaging requirements into releases, planning release timetables and communicating releases details
 +
 
 +
'''Content editor'''
 +
 
 +
Responsibilities include:
 +
* Manage the actions resulting from the content plan for those personas and tasks that were prioritized for site launch (managed through Bugzilla)
 +
* Monitor and manage scenario and persona expectations (around KPIs) and further develop the content plan around these expectations
 +
* Validate user needs and remaining user tasks based on community/user needs (place content plan on wiki to get feedback, active use of Bugzilla to solicit needs)
 +
* Create and manage content, onsite and across the ecosystem (for example Wikipedia and Youtube) resulting from the actions identified above
 +
* Develop content needs from relationship with community, with people representing personas
 +
* Ensure quality of content (grammar, style, tone of voice, etc.) and relevance
 +
 
 +
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.
 +
 
 +
'''Business/community owner'''
 +
 
 +
Responsibilities include:
 +
* Accountable for the overall performance, results and visibility of developer.meego.com site
 +
* Prioritization of requirements according to business/community and visitor needs
 +
* Approval of major editorial decisions
 +
* Oversee and facilitate the developer community with a special focus on the primary community stakeholders
 +
* Budget and budget allocation
 +
 
 +
'''Analytics manager'''
 +
Responsibilities include:
 +
* Development of the measurement framework according to personas
 +
* Development of KPIs required for these personas
 +
* Regular production of KPI results, baseline and recommended targets
 +
 
 +
'''Operations'''
 +
 
 +
Responsibilities include:
 +
* Coordination and support for the team
 +
* Ensuring effective tools and processes are in place and in use
 +
* Managing meetings and ad-hoc workshops
 +
 
 +
==== Content management process matrix ====
 +
Draft version of the content management process is as follows. Note that steps 1-5 are for editor-driven content.
 +
 
 +
{| border="1"
 +
|Activity
 +
|Accountable
 +
|Responsible
 +
|Contributor
 +
|Informed
 +
|Tool(s)
 +
|----
 +
|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
 +
|----
 +
|}
 +
 
 +
Matrix legend:
 +
* Accountable = person/people responsible for decision-making (a.k.a. the buck stops here)
 +
* Responsible = person/people whose job is to see the activity happens
 +
* Contributor = person/people whose input is needed to make the activity happen
 +
* Informed = person/people who need to know what’s going on concerning the activity
 +
 
 +
'''About the tools used in the content management process'''
 +
 
 +
* Bugzilla is used to manage both content and capability needs, for example wishlists, future releases, current release maintenance fixes, incomplete areas, etc.
 +
* Wiki is used for content drafting and staging for community content. Content in the wiki could be drafted and reviewed in iterations between the content creators and editor and placed on site when the creators and editors feel it is in a complete, quality assured format. For content that is under continual development, Wiki entries may also be divided into constant and variable sections, and linked accordingly in the site.
 +
* Google Analytics may be used to track site use and conversion goals
 +
* Roadmap, actions, issues are used to track development plans
=== Content Draft ===
=== Content Draft ===

Revision as of 18:56, 9 January 2011

Contents

Overview

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.

Objectives

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).

Status

The current status can be found here.

A bugzilla version is available here.

IDPSeverityStatusSummary (50 tasks) ⇒
17896HighnormalASSIGNEDAPI References - Restructure API references page
18762HighnormalASSIGNEDConfiguration - Improve and simplify input formats and wysiwyg
19516HighnormalNEEDINFOGuides - create tree navigation block
20407HighnormalASSIGNEDAPI References - add active-trail state CSS to api menu
20412HighnormalASSIGNEDGeneral - upgrade to latest drupal version
16305LowmajorASSIGNEDGuides - Suggest new guide page or topic
20508LowmajorASSIGNEDBroken link on /guides/guidelines/meego-compliance-tools
16435LownormalASSIGNEDContent - packaging video
16439LownormalASSIGNEDOBS / packaging content for DMC
19528LownormalASSIGNEDSDK & Tools - allow for external app store SDK references
19530LownormalASSIGNEDSDK & Tools - define new content type fields
19531LownormalASSIGNEDSDK & Tools - views for tools lists (block and page)
19532LownormalASSIGNEDSDK & Tools - 2 categories for tools (commercial and open source)
19534LownormalASSIGNEDCommunity - design block for additional community forums promotions
19535LownormalASSIGNEDCommunity - commercial support
19537LownormalASSIGNEDPublish - app compliance checker
19538LownormalASSIGNEDPublish - - wireframe new section
19539LownormalASSIGNEDPublish - new content type for app store list
19540LownormalASSIGNEDPublish - app compliance checker; front end for app compliance checker
19541LownormalASSIGNEDPublish - app compliance checker; provide web service api for external submission of apps
19542LownormalASSIGNEDPublish - app compliance checker; provide logging of apps status for user
19543LownormalASSIGNEDPublish - app compliance checker; ensure privacy of app status
20199LownormalASSIGNEDContent - Details on setting up an internal OBS for meego
20318LownormalASSIGNEDBroken link on developer.meego.com/guides/deployment/packaging-guidelines
20535LownormalASSIGNEDBroken link on /guides/getting-started/application-development-lifecycle
20536LownormalASSIGNEDBroken links on /guides/samples/qt-quick-examples-forum-nokia
20537LownormalASSIGNEDBroken links on /guides/devices/installing-meego-nokia-n900-external-mmc-card
20538LownormalASSIGNEDBroken links on /guides/getting-started/developing-qt-simulator
20766LownormalNEEDINFOAdd additional filters to Guides page
6340MediumenhancementASSIGNEDDeveloper.MeeGo.Com content process
11439MediumenhancementREOPENEDExtra tools - copy deeper content from maemo.org
13222MediumenhancementNEWmeego docs search term should lead to our devel guide/corner when published.
14757MediumenhancementASSIGNEDContent - Motivational material/incentives needed
3680MediumnormalREOPENEDTypos and image problem in UI Design Guidelines - Handset
8703MediumnormalASSIGNED"Getting started" link is broken
11787MediumnormalASSIGNEDContent - Detailed architecture should be under guides and not references
12681MediumnormalASSIGNEDContent - Define the DMC website roles
17364MediumnormalASSIGNEDGuides - Restructure Guides area to provide both a tree view and list view
17366MediumnormalASSIGNEDAPI References - evaluate entire API references workflow and generation
19513MediumnormalASSIGNEDGuides - theme/style tabs like meego.com tabs
19518MediumnormalASSIGNEDGuides- improve guide node pages
19521MediumnormalASSIGNEDAPI References - refactor API menu navigation so reliance on menu items doesn't exist
19522MediumnormalASSIGNEDAPI References - autocomplete search for functions
19524MediumnormalASSIGNEDAPI References - look at other ways to pull in api docs
19525MediumnormalASSIGNEDAPI References - provide place for commercial tool APIs
19536MediumnormalASSIGNEDGeneral Items
20224MediumnormalASSIGNEDGeneral - look at different solution to the use of nice-menus for sub-site navigation
20227MediumnormalASSIGNEDGeneral - enable breadcrumbs for site navigation
20999MediumnormalNEWGuides - add "advanced toggle" to the filter block for all filters below the keyword filter
12877UndecidedmajorASSIGNEDFirst Stop at Becoming a Hero: A guide for first *non* hello world app on MeeGo.

Tasks

All bugzilla tasks/bugs for developer.meego.com.

Critical tasks

See bugzilla list above.

Content Description

The content description can be found from here.

The site should link to the related content listed here.


Content Process

The proposed content management process is based upon several community roles. These roles must first be defined before introducing the proposed content management matrix.

Concept owner

Responsibilities include:

  • Manage the personas and user journeys across the ecosystem surrounding the site
  • Identify main content and capability gaps and needs for these journeys
  • Act as the primary advocate for the visitor

Design owner

Responsibilities include:

  • To ensure the structure and capabilities of the developer.meego.com match the needs of personas and the business/community
  • To ensure the site design fits the requirements and tonality of the MeeGo brand
  • To ensure business/community and visitor requirements are captured, analyzed and prioritized

Production

Responsibilities include:

  • Manage delivery of capabilities according to prioritized requirements
  • Packaging requirements into releases, planning release timetables and communicating releases details

Content editor

Responsibilities include:

  • Manage the actions resulting from the content plan for those personas and tasks that were prioritized for site launch (managed through Bugzilla)
  • Monitor and manage scenario and persona expectations (around KPIs) and further develop the content plan around these expectations
  • Validate user needs and remaining user tasks based on community/user needs (place content plan on wiki to get feedback, active use of Bugzilla to solicit needs)
  • Create and manage content, onsite and across the ecosystem (for example Wikipedia and Youtube) resulting from the actions identified above
  • Develop content needs from relationship with community, with people representing personas
  • Ensure quality of content (grammar, style, tone of voice, etc.) and relevance

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.

Business/community owner

Responsibilities include:

  • Accountable for the overall performance, results and visibility of developer.meego.com site
  • Prioritization of requirements according to business/community and visitor needs
  • Approval of major editorial decisions
  • Oversee and facilitate the developer community with a special focus on the primary community stakeholders
  • Budget and budget allocation

Analytics manager Responsibilities include:

  • Development of the measurement framework according to personas
  • Development of KPIs required for these personas
  • Regular production of KPI results, baseline and recommended targets

Operations

Responsibilities include:

  • Coordination and support for the team
  • Ensuring effective tools and processes are in place and in use
  • Managing meetings and ad-hoc workshops

Content management process matrix

Draft version of the content management process is as follows. Note that steps 1-5 are for editor-driven content.

Activity Accountable Responsible Contributor Informed Tool(s)
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

Matrix legend:

  • Accountable = person/people responsible for decision-making (a.k.a. the buck stops here)
  • Responsible = person/people whose job is to see the activity happens
  • Contributor = person/people whose input is needed to make the activity happen
  • Informed = person/people who need to know what’s going on concerning the activity

About the tools used in the content management process

  • Bugzilla is used to manage both content and capability needs, for example wishlists, future releases, current release maintenance fixes, incomplete areas, etc.
  • Wiki is used for content drafting and staging for community content. Content in the wiki could be drafted and reviewed in iterations between the content creators and editor and placed on site when the creators and editors feel it is in a complete, quality assured format. For content that is under continual development, Wiki entries may also be divided into constant and variable sections, and linked accordingly in the site.
  • Google Analytics may be used to track site use and conversion goals
  • Roadmap, actions, issues are used to track development plans

Content Draft

A wiki version of the information architecture with draft content is available here.

Future Content

The current site could be enhanced with the following content.

  1. Active meego architecture diagram

Development Process

The process used to develop the site can be found here

Schedule

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.

Site design

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.

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:

Dev-meego.com-frontpage update 2010-12-20.png

Project Team

MeeGo Project Manager

Project Members

... People working on the project full-time funded by Nokia...

Community Members

... People from the community involved in this project .....

Contact People

Associated activities

The Developer Engagement Framework.

Retrieved from "http://wiki.meego.com/Application_developer_site"
Personal tools