MeeGo wiki - User contributions [en]

Application developer site

2011-04-03T15:09:15Z

Verbosemode: /* Tools used in site processes */

== 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 [[Application developer site/Status | here]].

A bugzilla version is available [http://bugs.meego.com/show_bug.cgi?id=7882 here].

{{#bugzilla:
|columns=id,priority,severity,status,summary
|product=developer.meego.com
|status=new,assigned,needinfo,reopened
|sort=priority,severity,id
}}

== Tasks ==

All [http://bugs.meego.com/buglist.cgi?quicksearch=developer.meego.com bugzilla tasks/bugs] for developer.meego.com.

=== Critical tasks ===

See bugzilla list above.

== Operating model ==
The operating model for DMC is proposed as follows:
[[File:DMC_roles_OM.png]]

'''DMC coordinator'''

Responsibilities include:
* Act as the primary advocate for the visitor
* Define tools and platforms
**Wiki
**Bugzilla
**Performance and security (backups, etc)
* Develop guidelines for community
* Set targets and action plans
* Build alliances across the ecosystem
* Communicate with the community
* Arrange funding
* Arbitrate requirements handling
* Steer MeeGo brand deployment
* KPI definitions and monitoring
* Create incentives for contributions:
** karma incentives
** financial incentives
** promotional materials
** dev device distribution
** event participation
* Manage the personas and user journeys across the ecosystem surrounding the site (w/content editors)
* Identify main content and capability gaps and needs for these journeys (w/content editors)

'''DMC Production Manager'''

Responsibilities include:
* Oversee minor and major platform releases
* Design aspects including:
** usability
** site IA (with content editors and coordinator)
** design assets
** CMS features
**ensure MeeGo brand deployment
* Steer site improvement requests
**'''Improvement requests process''':
*** 1. need requested
*** 2. need validated
*** 3. development prioritised
*** 4. source found (production manager finds concept developers)
*** 5. developed
*** 6. tested
*** 7. release planned
*** 8. release
* Agree on production workload. Flexible, can be delegated/divided based on:
** core skill
** application module
** and could also involve finding potential Linux foundation resources (which would influence role definitions etc.)

'''Drupal developers'''

Responsibilities include:
* Required participation in these steps of the improvement process:
** 1. need requested
** 4. source found
** 5. developed

'''Content editors'''

Responsibilities include:

* '''Oversee content process''':
** 1. need requested (generally through Bugzilla)
** 2. need validated: content editor validates against content plan
** 3. source found: content editor finds contributors
** 4. content created as draft (usually in wiki, but may be links in Bugzilla)
** 5. Content reviewed (by community/other contributors/content editor)
** 6. content released as approved (migrated to site by content editor or linked to wiki from DMC by content editor)
* Managing content plan:
** managing personas/scenarios
*** developers
*** designers
*** technology thought leaders
*** lead users
** prioritizing content requests
** managing home and hub page editorially
** managing content ecosystem
*** reach activities
*** social media monitoring
*** seo
* Manage content on site and across the ecosystem (for example Wikipedia and Youtube) resulting from the actions identified above
* Ensure quality of content (grammar, style, tone of voice, etc.) and relevance
* Agree on editorial workload
** assume minimum 2 or 3 editors needed
** workload by content type
** workload by core skill
** workload by language and localisation
** workload by persona
** workload by geography/timezone

'''FOR INSTRUCTIONS ON ADDING/EDITING CONTENT IN DMC, PLEASE SEE THIS PAGE:''' [http://wiki.meego.com/Application_developer_site/Drupal_guidelines http://wiki.meego.com/Application_developer_site/Drupal_guidelines]

'''Content contributors'''
Responsibilities include:

* Participation needed in these parts of the content process:
** 1. need requested (respond if skills suit request)
** 3. source found (content bug assigned to contributor)
** 4. content created as draft (usually in wiki, but may be links provided through Bugzilla)
** 5. Content reviewed (by other contributors/community members/content editor)

== Content Description ==

The content description can be found from [[Application developer site/Description | here]].

The site should link to the related content listed [[Application developer site/Related content | here]].

=== Content Draft ===

A wiki version of the information architecture with draft content is available [[Application developer site/Draft content | here]].

=== Future Content ===

The current site could be enhanced with the following content.

# [[Application developer site/Active architecture diagram| Active meego architecture diagram]]

== Content process ==

As defined above in the operating model:

* 1. need requested (generally through Bugzilla)
* 2. need validated: content editor validates against content plan
* 3. source found: content editor finds contributors
* 4. content created as draft (usually in wiki, but may be links in Bugzilla)
* 5. Content reviewed (by community/other contributors/content editor)
* 6. content released as approved (migrated to site by content editor or linked to wiki from DMC by content editor)

== Development Process ==

Improvements/requirements development process as defined in the operating model above:

* 1. need requested (Bugzilla)
* 2. need validated (Production manager/coordinator)
* 3. development prioritized (Production manager/coordinator/community input)
* 4. source found (production manager finds concept developers) (drupal developer, designer, etc)
* 5. developed
* 6. tested
* 7. release planned
* 8. release

More about site development can be found [[Application developer site/Process | here]]

== Release process ==

As defined above in the operating model:

Minor release:
* 1. Development
* 2. RC, security
* 3. Production

Major release:
* 1. Pre-alpha
* 2. Alpha
* 3. Beta
* 4. RC, security
* 5. Production

== Tools used in site processes ==

* Bugzilla is used to manage both content and capability needs, for example wishlists, enhancements [FEA], 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 (with source marked whenever possible)
* Google Analytics may be used to track site use and conversion goals
* Roadmap, actions, issues are used to track development plans
* MeeGo mailing lists, forum, personal email (last resort), and Bugzilla used as communication
* CMS for content management (see [http://wiki.meego.com/Application_developer_site/Drupal_guidelines instructions for content editors])

== 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, With the site planned to be available in October aligned with the MeeGo 1.1 release.

Critical bugs fixed as of March 15. Awaiting approval from community for passwords to be lifted.

== Site design ==

The draft information architecture can be found here [[Application developer site/Information architecture | here]]. It is open for comments and suggestions.

Some sample wireframe designs will be found [[Application developer site/WireFrames | 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:

'''MOCKUP ONLY'''
[[File:Homepage layout proposal.jpg]]

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:

'''MOCKUP ONLY'''
[[File:dev-meego.com-frontpage_update_2010-12-20.png|800px]]

== Project Team ==

=== MeeGo Project Manager ===

* [http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)] - Nokia's Maemo (Application) Developer Advocate

=== Project Members ===

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

* [http://meego.com/users/ttlukkar Teemu Lukkari/ttlukkar] / Activeark / Project management, Design manager
* [http://meego.com/users/harmaakinkku Graham Honeywill/harmaakinkku] / Activeark / Project Communications, Analytics manager, Concept owner
* [http://meego.com/users/verbosemode Tiffiny Rossi/verbosemode] / Activeark / Content editor
* [http://meego.com/users/mikaelkundert Mikael Kundert/mikaelkundert] / Activeark / Drupal developer
* [http://meego.com/users/quang Quang Pham/quang] / Activeark / Drupal developer

=== Community Members ===

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

* [http://meego.com/users/dneary Dave Neary/dneary] - maemo.org docmaster
* [http://meego.com/users/dawnfoster Dawn Foster/dawnfoster] - Community Manager
* [http://meego.com/users/mshaver Michael Shaver/mshaver] - Moblin.org webmaster & meego.com website developer
* [http://meego.com/users/townxelliot Elliot Smith/townxelliot] - MeeGo wiki maintainer & MeeGo SDK content editor
* bspencer - Bob Spencer

== Contact People ==

== Associated activities ==

The [[DeveloperEngagement | Developer Engagement Framework]].

== Documentation ==

[[Application developer site/Documentation | Technical documentation]]

Application developer site

2011-04-03T15:07:53Z

Verbosemode: /* Operating model */

== 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 [[Application developer site/Status | here]].

A bugzilla version is available [http://bugs.meego.com/show_bug.cgi?id=7882 here].

{{#bugzilla:
|columns=id,priority,severity,status,summary
|product=developer.meego.com
|status=new,assigned,needinfo,reopened
|sort=priority,severity,id
}}

== Tasks ==

All [http://bugs.meego.com/buglist.cgi?quicksearch=developer.meego.com bugzilla tasks/bugs] for developer.meego.com.

=== Critical tasks ===

See bugzilla list above.

== Operating model ==
The operating model for DMC is proposed as follows:
[[File:DMC_roles_OM.png]]

'''DMC coordinator'''

Responsibilities include:
* Act as the primary advocate for the visitor
* Define tools and platforms
**Wiki
**Bugzilla
**Performance and security (backups, etc)
* Develop guidelines for community
* Set targets and action plans
* Build alliances across the ecosystem
* Communicate with the community
* Arrange funding
* Arbitrate requirements handling
* Steer MeeGo brand deployment
* KPI definitions and monitoring
* Create incentives for contributions:
** karma incentives
** financial incentives
** promotional materials
** dev device distribution
** event participation
* Manage the personas and user journeys across the ecosystem surrounding the site (w/content editors)
* Identify main content and capability gaps and needs for these journeys (w/content editors)

'''DMC Production Manager'''

Responsibilities include:
* Oversee minor and major platform releases
* Design aspects including:
** usability
** site IA (with content editors and coordinator)
** design assets
** CMS features
**ensure MeeGo brand deployment
* Steer site improvement requests
**'''Improvement requests process''':
*** 1. need requested
*** 2. need validated
*** 3. development prioritised
*** 4. source found (production manager finds concept developers)
*** 5. developed
*** 6. tested
*** 7. release planned
*** 8. release
* Agree on production workload. Flexible, can be delegated/divided based on:
** core skill
** application module
** and could also involve finding potential Linux foundation resources (which would influence role definitions etc.)

'''Drupal developers'''

Responsibilities include:
* Required participation in these steps of the improvement process:
** 1. need requested
** 4. source found
** 5. developed

'''Content editors'''

Responsibilities include:

* '''Oversee content process''':
** 1. need requested (generally through Bugzilla)
** 2. need validated: content editor validates against content plan
** 3. source found: content editor finds contributors
** 4. content created as draft (usually in wiki, but may be links in Bugzilla)
** 5. Content reviewed (by community/other contributors/content editor)
** 6. content released as approved (migrated to site by content editor or linked to wiki from DMC by content editor)
* Managing content plan:
** managing personas/scenarios
*** developers
*** designers
*** technology thought leaders
*** lead users
** prioritizing content requests
** managing home and hub page editorially
** managing content ecosystem
*** reach activities
*** social media monitoring
*** seo
* Manage content on site and across the ecosystem (for example Wikipedia and Youtube) resulting from the actions identified above
* Ensure quality of content (grammar, style, tone of voice, etc.) and relevance
* Agree on editorial workload
** assume minimum 2 or 3 editors needed
** workload by content type
** workload by core skill
** workload by language and localisation
** workload by persona
** workload by geography/timezone

'''FOR INSTRUCTIONS ON ADDING/EDITING CONTENT IN DMC, PLEASE SEE THIS PAGE:''' [http://wiki.meego.com/Application_developer_site/Drupal_guidelines http://wiki.meego.com/Application_developer_site/Drupal_guidelines]

'''Content contributors'''
Responsibilities include:

* Participation needed in these parts of the content process:
** 1. need requested (respond if skills suit request)
** 3. source found (content bug assigned to contributor)
** 4. content created as draft (usually in wiki, but may be links provided through Bugzilla)
** 5. Content reviewed (by other contributors/community members/content editor)

== Content Description ==

The content description can be found from [[Application developer site/Description | here]].

The site should link to the related content listed [[Application developer site/Related content | here]].

=== Content Draft ===

A wiki version of the information architecture with draft content is available [[Application developer site/Draft content | here]].

=== Future Content ===

The current site could be enhanced with the following content.

# [[Application developer site/Active architecture diagram| Active meego architecture diagram]]

== Content process ==

As defined above in the operating model:

* 1. need requested (generally through Bugzilla)
* 2. need validated: content editor validates against content plan
* 3. source found: content editor finds contributors
* 4. content created as draft (usually in wiki, but may be links in Bugzilla)
* 5. Content reviewed (by community/other contributors/content editor)
* 6. content released as approved (migrated to site by content editor or linked to wiki from DMC by content editor)

== Development Process ==

Improvements/requirements development process as defined in the operating model above:

* 1. need requested (Bugzilla)
* 2. need validated (Production manager/coordinator)
* 3. development prioritized (Production manager/coordinator/community input)
* 4. source found (production manager finds concept developers) (drupal developer, designer, etc)
* 5. developed
* 6. tested
* 7. release planned
* 8. release

More about site development can be found [[Application developer site/Process | here]]

== Release process ==

As defined above in the operating model:

Minor release:
* 1. Development
* 2. RC, security
* 3. Production

Major release:
* 1. Pre-alpha
* 2. Alpha
* 3. Beta
* 4. RC, security
* 5. Production

== Tools used in site processes ==

* Bugzilla is used to manage both content and capability needs, for example wishlists, enhancements [FEA], 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 (with source marked whenever possible)
* Google Analytics may be used to track site use and conversion goals
* Roadmap, actions, issues are used to track development plans
* MeeGo mailing lists, forum, personal email (last resort), and Bugzilla used as communication

== 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, With the site planned to be available in October aligned with the MeeGo 1.1 release.

Critical bugs fixed as of March 15. Awaiting approval from community for passwords to be lifted.

== Site design ==

The draft information architecture can be found here [[Application developer site/Information architecture | here]]. It is open for comments and suggestions.

Some sample wireframe designs will be found [[Application developer site/WireFrames | 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:

'''MOCKUP ONLY'''
[[File:Homepage layout proposal.jpg]]

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:

'''MOCKUP ONLY'''
[[File:dev-meego.com-frontpage_update_2010-12-20.png|800px]]

== Project Team ==

=== MeeGo Project Manager ===

* [http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)] - Nokia's Maemo (Application) Developer Advocate

=== Project Members ===

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

* [http://meego.com/users/ttlukkar Teemu Lukkari/ttlukkar] / Activeark / Project management, Design manager
* [http://meego.com/users/harmaakinkku Graham Honeywill/harmaakinkku] / Activeark / Project Communications, Analytics manager, Concept owner
* [http://meego.com/users/verbosemode Tiffiny Rossi/verbosemode] / Activeark / Content editor
* [http://meego.com/users/mikaelkundert Mikael Kundert/mikaelkundert] / Activeark / Drupal developer
* [http://meego.com/users/quang Quang Pham/quang] / Activeark / Drupal developer

=== Community Members ===

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

* [http://meego.com/users/dneary Dave Neary/dneary] - maemo.org docmaster
* [http://meego.com/users/dawnfoster Dawn Foster/dawnfoster] - Community Manager
* [http://meego.com/users/mshaver Michael Shaver/mshaver] - Moblin.org webmaster & meego.com website developer
* [http://meego.com/users/townxelliot Elliot Smith/townxelliot] - MeeGo wiki maintainer & MeeGo SDK content editor
* bspencer - Bob Spencer

== Contact People ==

== Associated activities ==

The [[DeveloperEngagement | Developer Engagement Framework]].

== Documentation ==

[[Application developer site/Documentation | Technical documentation]]

Application developer site

2011-04-03T15:06:58Z

Verbosemode: /* Operating model */

== 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 [[Application developer site/Status | here]].

A bugzilla version is available [http://bugs.meego.com/show_bug.cgi?id=7882 here].

{{#bugzilla:
|columns=id,priority,severity,status,summary
|product=developer.meego.com
|status=new,assigned,needinfo,reopened
|sort=priority,severity,id
}}

== Tasks ==

All [http://bugs.meego.com/buglist.cgi?quicksearch=developer.meego.com bugzilla tasks/bugs] for developer.meego.com.

=== Critical tasks ===

See bugzilla list above.

== Operating model ==
The operating model for DMC is proposed as follows:
[[File:DMC_roles_OM.png]]

'''DMC coordinator'''

Responsibilities include:
* Act as the primary advocate for the visitor
* Define tools and platforms
**Wiki
**Bugzilla
**Performance and security (backups, etc)
* Develop guidelines for community
* Set targets and action plans
* Build alliances across the ecosystem
* Communicate with the community
* Arrange funding
* Arbitrate requirements handling
* Steer MeeGo brand deployment
* KPI definitions and monitoring
* Create incentives for contributions:
** karma incentives
** financial incentives
** promotional materials
** dev device distribution
** event participation
* Manage the personas and user journeys across the ecosystem surrounding the site (w/content editors)
* Identify main content and capability gaps and needs for these journeys (w/content editors)

'''DMC Production Manager'''

Responsibilities include:
* Oversee minor and major platform releases
* Design aspects including:
** usability
** site IA (with content editors and coordinator)
** design assets
** CMS features
**ensure MeeGo brand deployment
* Steer site improvement requests
**'''Improvement requests process''':
*** 1. need requested
*** 2. need validated
*** 3. development prioritised
*** 4. source found (production manager finds concept developers)
*** 5. developed
*** 6. tested
*** 7. release planned
*** 8. release
* Agree on production workload. Flexible, can be delegated/divided based on:
** core skill
** application module
** and could also involve finding potential Linux foundation resources (which would influence role definitions etc.)

'''Drupal developers'''

Responsibilities include:
* Required participation in these steps of the improvement process:
** 1. need requested
** 4. source found
** 5. developed

'''Content editors'''

Responsibilities include:

* '''Oversee content process''':
** 1. need requested (generally through Bugzilla)
** 2. need validated: content editor validates against content plan
** 3. source found: content editor finds contributors
** 4. content created as draft (usually in wiki, but may be links in Bugzilla)
** 5. Content reviewed (by community/other contributors/content editor)
** 6. content released as approved (migrated to site by content editor or linked to wiki from DMC by content editor)
* Managing content plan:
** managing personas/scenarios
*** developers
*** designers
*** technology thought leaders
*** lead users
** prioritizing content requests
** managing home and hub page editorially
** managing content ecosystem
*** reach activities
*** social media monitoring
*** seo
* Manage content on site and across the ecosystem (for example Wikipedia and Youtube) resulting from the actions identified above
* Ensure quality of content (grammar, style, tone of voice, etc.) and relevance
* Agree on editorial workload
** assume minimum 2 or 3 editors needed
** workload by content type
** workload by core skill
** workload by language and localisation
** workload by persona
** workload by geography/timezone

FOR INSTRUCTIONS ON ADDING/EDITING CONTENT IN DNC, PLEASE SEE THIS PAGE: [http://wiki.meego.com/Application_developer_site/Drupal_guidelines]

'''Content contributors'''
Responsibilities include:

* Participation needed in these parts of the content process:
** 1. need requested (respond if skills suit request)
** 3. source found (content bug assigned to contributor)
** 4. content created as draft (usually in wiki, but may be links provided through Bugzilla)
** 5. Content reviewed (by other contributors/community members/content editor)

== Content Description ==

The content description can be found from [[Application developer site/Description | here]].

The site should link to the related content listed [[Application developer site/Related content | here]].

=== Content Draft ===

A wiki version of the information architecture with draft content is available [[Application developer site/Draft content | here]].

=== Future Content ===

The current site could be enhanced with the following content.

# [[Application developer site/Active architecture diagram| Active meego architecture diagram]]

== Content process ==

As defined above in the operating model:

* 1. need requested (generally through Bugzilla)
* 2. need validated: content editor validates against content plan
* 3. source found: content editor finds contributors
* 4. content created as draft (usually in wiki, but may be links in Bugzilla)
* 5. Content reviewed (by community/other contributors/content editor)
* 6. content released as approved (migrated to site by content editor or linked to wiki from DMC by content editor)

== Development Process ==

Improvements/requirements development process as defined in the operating model above:

* 1. need requested (Bugzilla)
* 2. need validated (Production manager/coordinator)
* 3. development prioritized (Production manager/coordinator/community input)
* 4. source found (production manager finds concept developers) (drupal developer, designer, etc)
* 5. developed
* 6. tested
* 7. release planned
* 8. release

More about site development can be found [[Application developer site/Process | here]]

== Release process ==

As defined above in the operating model:

Minor release:
* 1. Development
* 2. RC, security
* 3. Production

Major release:
* 1. Pre-alpha
* 2. Alpha
* 3. Beta
* 4. RC, security
* 5. Production

== Tools used in site processes ==

* Bugzilla is used to manage both content and capability needs, for example wishlists, enhancements [FEA], 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 (with source marked whenever possible)
* Google Analytics may be used to track site use and conversion goals
* Roadmap, actions, issues are used to track development plans
* MeeGo mailing lists, forum, personal email (last resort), and Bugzilla used as communication

== 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, With the site planned to be available in October aligned with the MeeGo 1.1 release.

Critical bugs fixed as of March 15. Awaiting approval from community for passwords to be lifted.

== Site design ==

The draft information architecture can be found here [[Application developer site/Information architecture | here]]. It is open for comments and suggestions.

Some sample wireframe designs will be found [[Application developer site/WireFrames | 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:

'''MOCKUP ONLY'''
[[File:Homepage layout proposal.jpg]]

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:

'''MOCKUP ONLY'''
[[File:dev-meego.com-frontpage_update_2010-12-20.png|800px]]

== Project Team ==

=== MeeGo Project Manager ===

* [http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)] - Nokia's Maemo (Application) Developer Advocate

=== Project Members ===

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

* [http://meego.com/users/ttlukkar Teemu Lukkari/ttlukkar] / Activeark / Project management, Design manager
* [http://meego.com/users/harmaakinkku Graham Honeywill/harmaakinkku] / Activeark / Project Communications, Analytics manager, Concept owner
* [http://meego.com/users/verbosemode Tiffiny Rossi/verbosemode] / Activeark / Content editor
* [http://meego.com/users/mikaelkundert Mikael Kundert/mikaelkundert] / Activeark / Drupal developer
* [http://meego.com/users/quang Quang Pham/quang] / Activeark / Drupal developer

=== Community Members ===

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

* [http://meego.com/users/dneary Dave Neary/dneary] - maemo.org docmaster
* [http://meego.com/users/dawnfoster Dawn Foster/dawnfoster] - Community Manager
* [http://meego.com/users/mshaver Michael Shaver/mshaver] - Moblin.org webmaster & meego.com website developer
* [http://meego.com/users/townxelliot Elliot Smith/townxelliot] - MeeGo wiki maintainer & MeeGo SDK content editor
* bspencer - Bob Spencer

== Contact People ==

== Associated activities ==

The [[DeveloperEngagement | Developer Engagement Framework]].

== Documentation ==

[[Application developer site/Documentation | Technical documentation]]

Application developer site/Drupal guidelines

2011-04-03T15:04:50Z

Verbosemode: /* Changing navigation and sub-navigation */

= Application Developer Site - Drupal guidelines =

== Location ==

The development/staging site is [http://meego.dev.dh-te.com here]. To get access please contact Ronan Mac Laverty (macron/maclaver).

== Access rights ==

To create content on the developer.meego.com site you need to have editor privileges. These can be obtained from the following people:
* Teemu Lukkari (ActiveArk)
* Ronan Mac Laverty (Nokia)
* Gil Quim (Nokia)
* Michael Shaver (Intel)
* Bob Spencer (Intel)

== Logging in ==

Those who have been given access writes to the DMC CMS may log in at the following address:

http://developer.meego.com/user

Enter your username and password, which are the same you use for all other sites in the MeeGo ecosystem. Click on Log in to enter.

Once you log in, you will see this screen:

[[File: screen2.png]]

From this screen you can either edit existing content, browse/view the website content and structure, or create new content.

Click on the '''wrench (spanner)''' at the top left of your screen to enter the higher-level content management and administration menus.

== Content Types ==

The content types available on DMC at the time of launch are the following.

*Api page (api_page) – These are specially coded pages for the api docs. The drupal developer should be the one to make updates here.
*Book page (book) – A book page is a page of content, organized into a collection of related entries collectively known as a book. A book page automatically displays links to adjacent pages, providing a simple navigation system for organizing and reviewing structured content.
*Event (event) – All events retrieved from main site by RSS/XML feed.
*External guide (guide_external) – Places a teaser into guide sections, allowing to link to external guides.
*Feed (feed) – Subscribe to RSS or Atom feeds. Creates nodes of the content type "Feed item" from feed content.
*Feed item (feed_item) – This content type is being used for automatically aggregated content from feeds.
*Guide (guide) – Used for practically everything, but primarily guides and tutorials. Must be categorized by type of guide (corresponds with the sub navigation in the guide section).
*Note (note) – Notes are simple pages, used in such places as Developer notes and Release notes. They provide a left hand navigation structure on their list pages.
*Page (page) – A general free-form HTML page (DO NOT CURRENTLY USE, if you think its needed its important to try to abstract the need and make a general content type if possible)
*Promotional block (promo) – A Promotional block can be used to place a content teaser into a section head or on the home page with different text or images then are found in the content itself.
*Section head (section_head) – Top level pages (Home, Introduction, ....). The Section head type is used to show a selection of content in a block layout.
*Section head with lists (section_head_view) – Top level pages with embedded views (lists, like guides). The Section head type is used to show a selection of content in blocks around a dominant content list.

For the majority of people only use the Guide information format.

To see this list, click on the '''wrench''' at the top left hand of the screen, then '''Content management > Content types'''.

== Add new content types or edit existing content types ==
When you are viewing the list of content types (W'''rench > Content management > Content types''') look at the menu at the top right of the content list. From here you can “'''add content type'''” or edit the “f'''ields'''” of existing content types.

[[File:screen1.png]]

== Browse/view content ==
Go to '''Wrench > Content management > Content list'''.

You can browse content by whether it’s published or not, type, date posted, or date uploaded.

[[File:screen3.png]]

Click on a content item in the list to view it, or “'''Edit'''” to make changes.

== Create content ==
Go to '''Wrench > Create content'''. From the black navigation frame on the left, choose which type of content you would like to add.

[[File:screen4.png]]

When you click on each content type, you will get a template to fill in with all the required and optional fields. Entering this information is very straightforward and help is available by hovering over a field you wish to learn more about.

Required fields are marked with a red asterisk.

If the content you have entered contains HTML, you may wish to select either enhanced HTML or raw as your format type (consult this help for more information: [http://developer.meego.com/filter/tips http://developer.meego.com/filter/tips]).

== Tips for creating content ==

=== External guides and guides ===

If you would like to connect several guides together as a “book” the developers could progress through, click on “'''Book outline'''” at the bottom of the Create Guide/External Guide page.

In the book field, you can either create a new book or add the guide to an existing book.

[[File:screen5.png]]

To ensure your guide/external guide has a description in the guide lists, click on '''List information''' at the bottom of the Create Guide/External guide page and enter a brief description. You can also upload an image here so it will have an image in the guide list page as well.

[[File:screen6.png]]

=== For all content types (but most likely pages or guides) ===

==== Content in menus ====
If you would like a page or guide to show up in the sub-navigation, click on “'''Menu'''” at the bottom of the Create <content type> page. In the '''PARENT ITEM''' field, select the navigation element you would like the page to appear under, then name it in '''MENU LINK TITLE'''.

[[File:screen7.png]]

==== Meta tags ====
Here you can add the metadata description, which will help people searching determine whether that page is relevant or not. Make metadata descriptions approximately 150 chars (with spaces) or less.

=== Section heads and Section heads w/lists ===
These are the landing pages of the site, and here you will most likely want to add promotional blocks as the content used here. So therefore, it’s prudent to create your promotional blocks first, then start adding the promo block titles in the “'''Content to feature'''” fields on the Create Section head page.

[[File:screen8.png]]

You can also adjust the layout of the promo blocks on a section head page by clicking on “'''Row layout'''” at the bottom of the Create page, then selecting the desired amount of promo blocks in each row.

[[File:screen9.png]]

Top links can be used to add more teasers in the banner area of the landing pages (section heads), but as they are not very attractive, they should be used with caution, perhaps only to show major/critical announcements.

== Edit content ==
You can edit content either from the Content list, or by navigating to the page you would like to edit and selecting '''Edit''' from the menu on the left hand side. If you do not see this menu, click '''X''' to close the content management menu:

[[File:screen10.png]]

It will return to the wrench icon and you should see the option to “'''Edit'''” the page.

== Delete content ==
Go to the page you would like to delete, click on '''Edit''', then '''Delete'''.

== Remove promo blocks from section heads ==
If you wish to delete a promo block from a section head, but still keep the promo block, go to the section head and click '''Edit'''. Then in the “'''Content to feature”''' field, just delete the title of the promo block you want to remove.

== Changing navigation and sub-navigation ==
Go to '''Wrench > Administer > Site Building > Menus > Primary links'''.

[[File:screen11.png]]

Here you can enable, disable, edit and delete what is shown in the navigation. Click '''Save configuration''' when you are done.

Application developer site/Drupal guidelines

2011-04-03T15:04:14Z

Verbosemode: /* Edit content */

= Application Developer Site - Drupal guidelines =

== Location ==

The development/staging site is [http://meego.dev.dh-te.com here]. To get access please contact Ronan Mac Laverty (macron/maclaver).

== Access rights ==

To create content on the developer.meego.com site you need to have editor privileges. These can be obtained from the following people:
* Teemu Lukkari (ActiveArk)
* Ronan Mac Laverty (Nokia)
* Gil Quim (Nokia)
* Michael Shaver (Intel)
* Bob Spencer (Intel)

== Logging in ==

Those who have been given access writes to the DMC CMS may log in at the following address:

http://developer.meego.com/user

Enter your username and password, which are the same you use for all other sites in the MeeGo ecosystem. Click on Log in to enter.

Once you log in, you will see this screen:

[[File: screen2.png]]

From this screen you can either edit existing content, browse/view the website content and structure, or create new content.

Click on the '''wrench (spanner)''' at the top left of your screen to enter the higher-level content management and administration menus.

== Content Types ==

The content types available on DMC at the time of launch are the following.

*Api page (api_page) – These are specially coded pages for the api docs. The drupal developer should be the one to make updates here.
*Book page (book) – A book page is a page of content, organized into a collection of related entries collectively known as a book. A book page automatically displays links to adjacent pages, providing a simple navigation system for organizing and reviewing structured content.
*Event (event) – All events retrieved from main site by RSS/XML feed.
*External guide (guide_external) – Places a teaser into guide sections, allowing to link to external guides.
*Feed (feed) – Subscribe to RSS or Atom feeds. Creates nodes of the content type "Feed item" from feed content.
*Feed item (feed_item) – This content type is being used for automatically aggregated content from feeds.
*Guide (guide) – Used for practically everything, but primarily guides and tutorials. Must be categorized by type of guide (corresponds with the sub navigation in the guide section).
*Note (note) – Notes are simple pages, used in such places as Developer notes and Release notes. They provide a left hand navigation structure on their list pages.
*Page (page) – A general free-form HTML page (DO NOT CURRENTLY USE, if you think its needed its important to try to abstract the need and make a general content type if possible)
*Promotional block (promo) – A Promotional block can be used to place a content teaser into a section head or on the home page with different text or images then are found in the content itself.
*Section head (section_head) – Top level pages (Home, Introduction, ....). The Section head type is used to show a selection of content in a block layout.
*Section head with lists (section_head_view) – Top level pages with embedded views (lists, like guides). The Section head type is used to show a selection of content in blocks around a dominant content list.

For the majority of people only use the Guide information format.

To see this list, click on the '''wrench''' at the top left hand of the screen, then '''Content management > Content types'''.

== Add new content types or edit existing content types ==
When you are viewing the list of content types (W'''rench > Content management > Content types''') look at the menu at the top right of the content list. From here you can “'''add content type'''” or edit the “f'''ields'''” of existing content types.

[[File:screen1.png]]

== Browse/view content ==
Go to '''Wrench > Content management > Content list'''.

You can browse content by whether it’s published or not, type, date posted, or date uploaded.

[[File:screen3.png]]

Click on a content item in the list to view it, or “'''Edit'''” to make changes.

== Create content ==
Go to '''Wrench > Create content'''. From the black navigation frame on the left, choose which type of content you would like to add.

[[File:screen4.png]]

When you click on each content type, you will get a template to fill in with all the required and optional fields. Entering this information is very straightforward and help is available by hovering over a field you wish to learn more about.

Required fields are marked with a red asterisk.

If the content you have entered contains HTML, you may wish to select either enhanced HTML or raw as your format type (consult this help for more information: [http://developer.meego.com/filter/tips http://developer.meego.com/filter/tips]).

== Tips for creating content ==

=== External guides and guides ===

If you would like to connect several guides together as a “book” the developers could progress through, click on “'''Book outline'''” at the bottom of the Create Guide/External Guide page.

In the book field, you can either create a new book or add the guide to an existing book.

[[File:screen5.png]]

To ensure your guide/external guide has a description in the guide lists, click on '''List information''' at the bottom of the Create Guide/External guide page and enter a brief description. You can also upload an image here so it will have an image in the guide list page as well.

[[File:screen6.png]]

=== For all content types (but most likely pages or guides) ===

==== Content in menus ====
If you would like a page or guide to show up in the sub-navigation, click on “'''Menu'''” at the bottom of the Create <content type> page. In the '''PARENT ITEM''' field, select the navigation element you would like the page to appear under, then name it in '''MENU LINK TITLE'''.

[[File:screen7.png]]

==== Meta tags ====
Here you can add the metadata description, which will help people searching determine whether that page is relevant or not. Make metadata descriptions approximately 150 chars (with spaces) or less.

=== Section heads and Section heads w/lists ===
These are the landing pages of the site, and here you will most likely want to add promotional blocks as the content used here. So therefore, it’s prudent to create your promotional blocks first, then start adding the promo block titles in the “'''Content to feature'''” fields on the Create Section head page.

[[File:screen8.png]]

You can also adjust the layout of the promo blocks on a section head page by clicking on “'''Row layout'''” at the bottom of the Create page, then selecting the desired amount of promo blocks in each row.

[[File:screen9.png]]

Top links can be used to add more teasers in the banner area of the landing pages (section heads), but as they are not very attractive, they should be used with caution, perhaps only to show major/critical announcements.

== Edit content ==
You can edit content either from the Content list, or by navigating to the page you would like to edit and selecting '''Edit''' from the menu on the left hand side. If you do not see this menu, click '''X''' to close the content management menu:

[[File:screen10.png]]

It will return to the wrench icon and you should see the option to “'''Edit'''” the page.

== Delete content ==
Go to the page you would like to delete, click on '''Edit''', then '''Delete'''.

== Remove promo blocks from section heads ==
If you wish to delete a promo block from a section head, but still keep the promo block, go to the section head and click '''Edit'''. Then in the “'''Content to feature”''' field, just delete the title of the promo block you want to remove.

== Changing navigation and sub-navigation ==
Go to '''Wrench > Administer > Site Building > Menus > Primary links'''.

<IMG>

Here you can enable, disable, edit and delete what is shown in the navigation. Click '''Save configuration''' when you are done.

Application developer site/Drupal guidelines

2011-04-03T15:03:05Z

Verbosemode: /* Section heads and Section heads w/lists */

= Application Developer Site - Drupal guidelines =

== Location ==

The development/staging site is [http://meego.dev.dh-te.com here]. To get access please contact Ronan Mac Laverty (macron/maclaver).

== Access rights ==

To create content on the developer.meego.com site you need to have editor privileges. These can be obtained from the following people:
* Teemu Lukkari (ActiveArk)
* Ronan Mac Laverty (Nokia)
* Gil Quim (Nokia)
* Michael Shaver (Intel)
* Bob Spencer (Intel)

== Logging in ==

Those who have been given access writes to the DMC CMS may log in at the following address:

http://developer.meego.com/user

Enter your username and password, which are the same you use for all other sites in the MeeGo ecosystem. Click on Log in to enter.

Once you log in, you will see this screen:

[[File: screen2.png]]

From this screen you can either edit existing content, browse/view the website content and structure, or create new content.

Click on the '''wrench (spanner)''' at the top left of your screen to enter the higher-level content management and administration menus.

== Content Types ==

The content types available on DMC at the time of launch are the following.

*Api page (api_page) – These are specially coded pages for the api docs. The drupal developer should be the one to make updates here.
*Book page (book) – A book page is a page of content, organized into a collection of related entries collectively known as a book. A book page automatically displays links to adjacent pages, providing a simple navigation system for organizing and reviewing structured content.
*Event (event) – All events retrieved from main site by RSS/XML feed.
*External guide (guide_external) – Places a teaser into guide sections, allowing to link to external guides.
*Feed (feed) – Subscribe to RSS or Atom feeds. Creates nodes of the content type "Feed item" from feed content.
*Feed item (feed_item) – This content type is being used for automatically aggregated content from feeds.
*Guide (guide) – Used for practically everything, but primarily guides and tutorials. Must be categorized by type of guide (corresponds with the sub navigation in the guide section).
*Note (note) – Notes are simple pages, used in such places as Developer notes and Release notes. They provide a left hand navigation structure on their list pages.
*Page (page) – A general free-form HTML page (DO NOT CURRENTLY USE, if you think its needed its important to try to abstract the need and make a general content type if possible)
*Promotional block (promo) – A Promotional block can be used to place a content teaser into a section head or on the home page with different text or images then are found in the content itself.
*Section head (section_head) – Top level pages (Home, Introduction, ....). The Section head type is used to show a selection of content in a block layout.
*Section head with lists (section_head_view) – Top level pages with embedded views (lists, like guides). The Section head type is used to show a selection of content in blocks around a dominant content list.

For the majority of people only use the Guide information format.

To see this list, click on the '''wrench''' at the top left hand of the screen, then '''Content management > Content types'''.

== Add new content types or edit existing content types ==
When you are viewing the list of content types (W'''rench > Content management > Content types''') look at the menu at the top right of the content list. From here you can “'''add content type'''” or edit the “f'''ields'''” of existing content types.

[[File:screen1.png]]

== Browse/view content ==
Go to '''Wrench > Content management > Content list'''.

You can browse content by whether it’s published or not, type, date posted, or date uploaded.

[[File:screen3.png]]

Click on a content item in the list to view it, or “'''Edit'''” to make changes.

== Create content ==
Go to '''Wrench > Create content'''. From the black navigation frame on the left, choose which type of content you would like to add.

[[File:screen4.png]]

When you click on each content type, you will get a template to fill in with all the required and optional fields. Entering this information is very straightforward and help is available by hovering over a field you wish to learn more about.

Required fields are marked with a red asterisk.

If the content you have entered contains HTML, you may wish to select either enhanced HTML or raw as your format type (consult this help for more information: [http://developer.meego.com/filter/tips http://developer.meego.com/filter/tips]).

== Tips for creating content ==

=== External guides and guides ===

If you would like to connect several guides together as a “book” the developers could progress through, click on “'''Book outline'''” at the bottom of the Create Guide/External Guide page.

In the book field, you can either create a new book or add the guide to an existing book.

[[File:screen5.png]]

To ensure your guide/external guide has a description in the guide lists, click on '''List information''' at the bottom of the Create Guide/External guide page and enter a brief description. You can also upload an image here so it will have an image in the guide list page as well.

[[File:screen6.png]]

=== For all content types (but most likely pages or guides) ===

==== Content in menus ====
If you would like a page or guide to show up in the sub-navigation, click on “'''Menu'''” at the bottom of the Create <content type> page. In the '''PARENT ITEM''' field, select the navigation element you would like the page to appear under, then name it in '''MENU LINK TITLE'''.

[[File:screen7.png]]

==== Meta tags ====
Here you can add the metadata description, which will help people searching determine whether that page is relevant or not. Make metadata descriptions approximately 150 chars (with spaces) or less.

=== Section heads and Section heads w/lists ===
These are the landing pages of the site, and here you will most likely want to add promotional blocks as the content used here. So therefore, it’s prudent to create your promotional blocks first, then start adding the promo block titles in the “'''Content to feature'''” fields on the Create Section head page.

[[File:screen8.png]]

You can also adjust the layout of the promo blocks on a section head page by clicking on “'''Row layout'''” at the bottom of the Create page, then selecting the desired amount of promo blocks in each row.

[[File:screen9.png]]

Top links can be used to add more teasers in the banner area of the landing pages (section heads), but as they are not very attractive, they should be used with caution, perhaps only to show major/critical announcements.

== Edit content ==
You can edit content either from the Content list, or by navigating to the page you would like to edit and selecting '''Edit''' from the menu on the left hand side. If you do not see this menu, click '''X''' to close the content management menu:

<IMG>

It will return to the wrench icon and you should see the option to “'''Edit'''” the page.

== Delete content ==
Go to the page you would like to delete, click on '''Edit''', then '''Delete'''.

== Remove promo blocks from section heads ==
If you wish to delete a promo block from a section head, but still keep the promo block, go to the section head and click '''Edit'''. Then in the “'''Content to feature”''' field, just delete the title of the promo block you want to remove.

== Changing navigation and sub-navigation ==
Go to '''Wrench > Administer > Site Building > Menus > Primary links'''.

<IMG>

Here you can enable, disable, edit and delete what is shown in the navigation. Click '''Save configuration''' when you are done.

Application developer site/Drupal guidelines

2011-04-03T15:02:06Z

Verbosemode: /* Content in menus */

= Application Developer Site - Drupal guidelines =

== Location ==

The development/staging site is [http://meego.dev.dh-te.com here]. To get access please contact Ronan Mac Laverty (macron/maclaver).

== Access rights ==

To create content on the developer.meego.com site you need to have editor privileges. These can be obtained from the following people:
* Teemu Lukkari (ActiveArk)
* Ronan Mac Laverty (Nokia)
* Gil Quim (Nokia)
* Michael Shaver (Intel)
* Bob Spencer (Intel)

== Logging in ==

Those who have been given access writes to the DMC CMS may log in at the following address:

http://developer.meego.com/user

Enter your username and password, which are the same you use for all other sites in the MeeGo ecosystem. Click on Log in to enter.

Once you log in, you will see this screen:

[[File: screen2.png]]

From this screen you can either edit existing content, browse/view the website content and structure, or create new content.

Click on the '''wrench (spanner)''' at the top left of your screen to enter the higher-level content management and administration menus.

== Content Types ==

The content types available on DMC at the time of launch are the following.

*Api page (api_page) – These are specially coded pages for the api docs. The drupal developer should be the one to make updates here.
*Book page (book) – A book page is a page of content, organized into a collection of related entries collectively known as a book. A book page automatically displays links to adjacent pages, providing a simple navigation system for organizing and reviewing structured content.
*Event (event) – All events retrieved from main site by RSS/XML feed.
*External guide (guide_external) – Places a teaser into guide sections, allowing to link to external guides.
*Feed (feed) – Subscribe to RSS or Atom feeds. Creates nodes of the content type "Feed item" from feed content.
*Feed item (feed_item) – This content type is being used for automatically aggregated content from feeds.
*Guide (guide) – Used for practically everything, but primarily guides and tutorials. Must be categorized by type of guide (corresponds with the sub navigation in the guide section).
*Note (note) – Notes are simple pages, used in such places as Developer notes and Release notes. They provide a left hand navigation structure on their list pages.
*Page (page) – A general free-form HTML page (DO NOT CURRENTLY USE, if you think its needed its important to try to abstract the need and make a general content type if possible)
*Promotional block (promo) – A Promotional block can be used to place a content teaser into a section head or on the home page with different text or images then are found in the content itself.
*Section head (section_head) – Top level pages (Home, Introduction, ....). The Section head type is used to show a selection of content in a block layout.
*Section head with lists (section_head_view) – Top level pages with embedded views (lists, like guides). The Section head type is used to show a selection of content in blocks around a dominant content list.

For the majority of people only use the Guide information format.

To see this list, click on the '''wrench''' at the top left hand of the screen, then '''Content management > Content types'''.

== Add new content types or edit existing content types ==
When you are viewing the list of content types (W'''rench > Content management > Content types''') look at the menu at the top right of the content list. From here you can “'''add content type'''” or edit the “f'''ields'''” of existing content types.

[[File:screen1.png]]

== Browse/view content ==
Go to '''Wrench > Content management > Content list'''.

You can browse content by whether it’s published or not, type, date posted, or date uploaded.

[[File:screen3.png]]

Click on a content item in the list to view it, or “'''Edit'''” to make changes.

== Create content ==
Go to '''Wrench > Create content'''. From the black navigation frame on the left, choose which type of content you would like to add.

[[File:screen4.png]]

When you click on each content type, you will get a template to fill in with all the required and optional fields. Entering this information is very straightforward and help is available by hovering over a field you wish to learn more about.

Required fields are marked with a red asterisk.

If the content you have entered contains HTML, you may wish to select either enhanced HTML or raw as your format type (consult this help for more information: [http://developer.meego.com/filter/tips http://developer.meego.com/filter/tips]).

== Tips for creating content ==

=== External guides and guides ===

If you would like to connect several guides together as a “book” the developers could progress through, click on “'''Book outline'''” at the bottom of the Create Guide/External Guide page.

In the book field, you can either create a new book or add the guide to an existing book.

[[File:screen5.png]]

To ensure your guide/external guide has a description in the guide lists, click on '''List information''' at the bottom of the Create Guide/External guide page and enter a brief description. You can also upload an image here so it will have an image in the guide list page as well.

[[File:screen6.png]]

=== For all content types (but most likely pages or guides) ===

==== Content in menus ====
If you would like a page or guide to show up in the sub-navigation, click on “'''Menu'''” at the bottom of the Create <content type> page. In the '''PARENT ITEM''' field, select the navigation element you would like the page to appear under, then name it in '''MENU LINK TITLE'''.

[[File:screen7.png]]

==== Meta tags ====
Here you can add the metadata description, which will help people searching determine whether that page is relevant or not. Make metadata descriptions approximately 150 chars (with spaces) or less.

=== Section heads and Section heads w/lists ===
These are the landing pages of the site, and here you will most likely want to add promotional blocks as the content used here. So therefore, it’s prudent to create your promotional blocks first, then start adding the promo block titles in the “'''Content to feature'''” fields on the Create Section head page.

<IMG>

You can also adjust the layout of the promo blocks on a section head page by clicking on “'''Row layout'''” at the bottom of the Create page, then selecting the desired amount of promo blocks in each row.

<IMG>

Top links can be used to add more teasers in the banner area of the landing pages (section heads), but as they are not very attractive, they should be used with caution, perhaps only to show major/critical announcements.

== Edit content ==
You can edit content either from the Content list, or by navigating to the page you would like to edit and selecting '''Edit''' from the menu on the left hand side. If you do not see this menu, click '''X''' to close the content management menu:

<IMG>

It will return to the wrench icon and you should see the option to “'''Edit'''” the page.

== Delete content ==
Go to the page you would like to delete, click on '''Edit''', then '''Delete'''.

== Remove promo blocks from section heads ==
If you wish to delete a promo block from a section head, but still keep the promo block, go to the section head and click '''Edit'''. Then in the “'''Content to feature”''' field, just delete the title of the promo block you want to remove.

== Changing navigation and sub-navigation ==
Go to '''Wrench > Administer > Site Building > Menus > Primary links'''.

<IMG>

Here you can enable, disable, edit and delete what is shown in the navigation. Click '''Save configuration''' when you are done.

Application developer site/Drupal guidelines

2011-04-03T15:01:16Z

Verbosemode: /* External guides and guides */

= Application Developer Site - Drupal guidelines =

== Location ==

The development/staging site is [http://meego.dev.dh-te.com here]. To get access please contact Ronan Mac Laverty (macron/maclaver).

== Access rights ==

To create content on the developer.meego.com site you need to have editor privileges. These can be obtained from the following people:
* Teemu Lukkari (ActiveArk)
* Ronan Mac Laverty (Nokia)
* Gil Quim (Nokia)
* Michael Shaver (Intel)
* Bob Spencer (Intel)

== Logging in ==

Those who have been given access writes to the DMC CMS may log in at the following address:

http://developer.meego.com/user

Enter your username and password, which are the same you use for all other sites in the MeeGo ecosystem. Click on Log in to enter.

Once you log in, you will see this screen:

[[File: screen2.png]]

From this screen you can either edit existing content, browse/view the website content and structure, or create new content.

Click on the '''wrench (spanner)''' at the top left of your screen to enter the higher-level content management and administration menus.

== Content Types ==

The content types available on DMC at the time of launch are the following.

*Api page (api_page) – These are specially coded pages for the api docs. The drupal developer should be the one to make updates here.
*Book page (book) – A book page is a page of content, organized into a collection of related entries collectively known as a book. A book page automatically displays links to adjacent pages, providing a simple navigation system for organizing and reviewing structured content.
*Event (event) – All events retrieved from main site by RSS/XML feed.
*External guide (guide_external) – Places a teaser into guide sections, allowing to link to external guides.
*Feed (feed) – Subscribe to RSS or Atom feeds. Creates nodes of the content type "Feed item" from feed content.
*Feed item (feed_item) – This content type is being used for automatically aggregated content from feeds.
*Guide (guide) – Used for practically everything, but primarily guides and tutorials. Must be categorized by type of guide (corresponds with the sub navigation in the guide section).
*Note (note) – Notes are simple pages, used in such places as Developer notes and Release notes. They provide a left hand navigation structure on their list pages.
*Page (page) – A general free-form HTML page (DO NOT CURRENTLY USE, if you think its needed its important to try to abstract the need and make a general content type if possible)
*Promotional block (promo) – A Promotional block can be used to place a content teaser into a section head or on the home page with different text or images then are found in the content itself.
*Section head (section_head) – Top level pages (Home, Introduction, ....). The Section head type is used to show a selection of content in a block layout.
*Section head with lists (section_head_view) – Top level pages with embedded views (lists, like guides). The Section head type is used to show a selection of content in blocks around a dominant content list.

For the majority of people only use the Guide information format.

To see this list, click on the '''wrench''' at the top left hand of the screen, then '''Content management > Content types'''.

== Add new content types or edit existing content types ==
When you are viewing the list of content types (W'''rench > Content management > Content types''') look at the menu at the top right of the content list. From here you can “'''add content type'''” or edit the “f'''ields'''” of existing content types.

[[File:screen1.png]]

== Browse/view content ==
Go to '''Wrench > Content management > Content list'''.

You can browse content by whether it’s published or not, type, date posted, or date uploaded.

[[File:screen3.png]]

Click on a content item in the list to view it, or “'''Edit'''” to make changes.

== Create content ==
Go to '''Wrench > Create content'''. From the black navigation frame on the left, choose which type of content you would like to add.

[[File:screen4.png]]

When you click on each content type, you will get a template to fill in with all the required and optional fields. Entering this information is very straightforward and help is available by hovering over a field you wish to learn more about.

Required fields are marked with a red asterisk.

If the content you have entered contains HTML, you may wish to select either enhanced HTML or raw as your format type (consult this help for more information: [http://developer.meego.com/filter/tips http://developer.meego.com/filter/tips]).

== Tips for creating content ==

=== External guides and guides ===

If you would like to connect several guides together as a “book” the developers could progress through, click on “'''Book outline'''” at the bottom of the Create Guide/External Guide page.

In the book field, you can either create a new book or add the guide to an existing book.

[[File:screen5.png]]

To ensure your guide/external guide has a description in the guide lists, click on '''List information''' at the bottom of the Create Guide/External guide page and enter a brief description. You can also upload an image here so it will have an image in the guide list page as well.

[[File:screen6.png]]

=== For all content types (but most likely pages or guides) ===

==== Content in menus ====
If you would like a page or guide to show up in the sub-navigation, click on “'''Menu'''” at the bottom of the Create <content type> page. In the '''PARENT ITEM''' field, select the navigation element you would like the page to appear under, then name it in '''MENU LINK TITLE'''.

<IMG>

==== Meta tags ====
Here you can add the metadata description, which will help people searching determine whether that page is relevant or not. Make metadata descriptions approximately 150 chars (with spaces) or less.

=== Section heads and Section heads w/lists ===
These are the landing pages of the site, and here you will most likely want to add promotional blocks as the content used here. So therefore, it’s prudent to create your promotional blocks first, then start adding the promo block titles in the “'''Content to feature'''” fields on the Create Section head page.

<IMG>

You can also adjust the layout of the promo blocks on a section head page by clicking on “'''Row layout'''” at the bottom of the Create page, then selecting the desired amount of promo blocks in each row.

<IMG>

Top links can be used to add more teasers in the banner area of the landing pages (section heads), but as they are not very attractive, they should be used with caution, perhaps only to show major/critical announcements.

== Edit content ==
You can edit content either from the Content list, or by navigating to the page you would like to edit and selecting '''Edit''' from the menu on the left hand side. If you do not see this menu, click '''X''' to close the content management menu:

<IMG>

It will return to the wrench icon and you should see the option to “'''Edit'''” the page.

== Delete content ==
Go to the page you would like to delete, click on '''Edit''', then '''Delete'''.

== Remove promo blocks from section heads ==
If you wish to delete a promo block from a section head, but still keep the promo block, go to the section head and click '''Edit'''. Then in the “'''Content to feature”''' field, just delete the title of the promo block you want to remove.

== Changing navigation and sub-navigation ==
Go to '''Wrench > Administer > Site Building > Menus > Primary links'''.

<IMG>

Here you can enable, disable, edit and delete what is shown in the navigation. Click '''Save configuration''' when you are done.

Application developer site/Drupal guidelines

2011-04-03T14:59:45Z

Verbosemode: /* Create content */

= Application Developer Site - Drupal guidelines =

== Location ==

The development/staging site is [http://meego.dev.dh-te.com here]. To get access please contact Ronan Mac Laverty (macron/maclaver).

== Access rights ==

To create content on the developer.meego.com site you need to have editor privileges. These can be obtained from the following people:
* Teemu Lukkari (ActiveArk)
* Ronan Mac Laverty (Nokia)
* Gil Quim (Nokia)
* Michael Shaver (Intel)
* Bob Spencer (Intel)

== Logging in ==

Those who have been given access writes to the DMC CMS may log in at the following address:

http://developer.meego.com/user

Enter your username and password, which are the same you use for all other sites in the MeeGo ecosystem. Click on Log in to enter.

Once you log in, you will see this screen:

[[File: screen2.png]]

From this screen you can either edit existing content, browse/view the website content and structure, or create new content.

Click on the '''wrench (spanner)''' at the top left of your screen to enter the higher-level content management and administration menus.

== Content Types ==

The content types available on DMC at the time of launch are the following.

*Api page (api_page) – These are specially coded pages for the api docs. The drupal developer should be the one to make updates here.
*Book page (book) – A book page is a page of content, organized into a collection of related entries collectively known as a book. A book page automatically displays links to adjacent pages, providing a simple navigation system for organizing and reviewing structured content.
*Event (event) – All events retrieved from main site by RSS/XML feed.
*External guide (guide_external) – Places a teaser into guide sections, allowing to link to external guides.
*Feed (feed) – Subscribe to RSS or Atom feeds. Creates nodes of the content type "Feed item" from feed content.
*Feed item (feed_item) – This content type is being used for automatically aggregated content from feeds.
*Guide (guide) – Used for practically everything, but primarily guides and tutorials. Must be categorized by type of guide (corresponds with the sub navigation in the guide section).
*Note (note) – Notes are simple pages, used in such places as Developer notes and Release notes. They provide a left hand navigation structure on their list pages.
*Page (page) – A general free-form HTML page (DO NOT CURRENTLY USE, if you think its needed its important to try to abstract the need and make a general content type if possible)
*Promotional block (promo) – A Promotional block can be used to place a content teaser into a section head or on the home page with different text or images then are found in the content itself.
*Section head (section_head) – Top level pages (Home, Introduction, ....). The Section head type is used to show a selection of content in a block layout.
*Section head with lists (section_head_view) – Top level pages with embedded views (lists, like guides). The Section head type is used to show a selection of content in blocks around a dominant content list.

For the majority of people only use the Guide information format.

To see this list, click on the '''wrench''' at the top left hand of the screen, then '''Content management > Content types'''.

== Add new content types or edit existing content types ==
When you are viewing the list of content types (W'''rench > Content management > Content types''') look at the menu at the top right of the content list. From here you can “'''add content type'''” or edit the “f'''ields'''” of existing content types.

[[File:screen1.png]]

== Browse/view content ==
Go to '''Wrench > Content management > Content list'''.

You can browse content by whether it’s published or not, type, date posted, or date uploaded.

[[File:screen3.png]]

Click on a content item in the list to view it, or “'''Edit'''” to make changes.

== Create content ==
Go to '''Wrench > Create content'''. From the black navigation frame on the left, choose which type of content you would like to add.

[[File:screen4.png]]

When you click on each content type, you will get a template to fill in with all the required and optional fields. Entering this information is very straightforward and help is available by hovering over a field you wish to learn more about.

Required fields are marked with a red asterisk.

If the content you have entered contains HTML, you may wish to select either enhanced HTML or raw as your format type (consult this help for more information: [http://developer.meego.com/filter/tips http://developer.meego.com/filter/tips]).

== Tips for creating content ==

=== External guides and guides ===

If you would like to connect several guides together as a “book” the developers could progress through, click on “'''Book outline'''” at the bottom of the Create Guide/External Guide page.

In the book field, you can either create a new book or add the guide to an existing book.

<IMG>

To ensure your guide/external guide has a description in the guide lists, click on '''List information''' at the bottom of the Create Guide/External guide page and enter a brief description. You can also upload an image here so it will have an image in the guide list page as well.

<IMG>

=== For all content types (but most likely pages or guides) ===

==== Content in menus ====
If you would like a page or guide to show up in the sub-navigation, click on “'''Menu'''” at the bottom of the Create <content type> page. In the '''PARENT ITEM''' field, select the navigation element you would like the page to appear under, then name it in '''MENU LINK TITLE'''.

<IMG>

==== Meta tags ====
Here you can add the metadata description, which will help people searching determine whether that page is relevant or not. Make metadata descriptions approximately 150 chars (with spaces) or less.

=== Section heads and Section heads w/lists ===
These are the landing pages of the site, and here you will most likely want to add promotional blocks as the content used here. So therefore, it’s prudent to create your promotional blocks first, then start adding the promo block titles in the “'''Content to feature'''” fields on the Create Section head page.

<IMG>

You can also adjust the layout of the promo blocks on a section head page by clicking on “'''Row layout'''” at the bottom of the Create page, then selecting the desired amount of promo blocks in each row.

<IMG>

Top links can be used to add more teasers in the banner area of the landing pages (section heads), but as they are not very attractive, they should be used with caution, perhaps only to show major/critical announcements.

== Edit content ==
You can edit content either from the Content list, or by navigating to the page you would like to edit and selecting '''Edit''' from the menu on the left hand side. If you do not see this menu, click '''X''' to close the content management menu:

<IMG>

It will return to the wrench icon and you should see the option to “'''Edit'''” the page.

== Delete content ==
Go to the page you would like to delete, click on '''Edit''', then '''Delete'''.

== Remove promo blocks from section heads ==
If you wish to delete a promo block from a section head, but still keep the promo block, go to the section head and click '''Edit'''. Then in the “'''Content to feature”''' field, just delete the title of the promo block you want to remove.

== Changing navigation and sub-navigation ==
Go to '''Wrench > Administer > Site Building > Menus > Primary links'''.

<IMG>

Here you can enable, disable, edit and delete what is shown in the navigation. Click '''Save configuration''' when you are done.

Application developer site/Drupal guidelines

2011-04-03T14:59:04Z

Verbosemode: /* Browse/view content */

= Application Developer Site - Drupal guidelines =

== Location ==

The development/staging site is [http://meego.dev.dh-te.com here]. To get access please contact Ronan Mac Laverty (macron/maclaver).

== Access rights ==

To create content on the developer.meego.com site you need to have editor privileges. These can be obtained from the following people:
* Teemu Lukkari (ActiveArk)
* Ronan Mac Laverty (Nokia)
* Gil Quim (Nokia)
* Michael Shaver (Intel)
* Bob Spencer (Intel)

== Logging in ==

Those who have been given access writes to the DMC CMS may log in at the following address:

http://developer.meego.com/user

Enter your username and password, which are the same you use for all other sites in the MeeGo ecosystem. Click on Log in to enter.

Once you log in, you will see this screen:

[[File: screen2.png]]

From this screen you can either edit existing content, browse/view the website content and structure, or create new content.

Click on the '''wrench (spanner)''' at the top left of your screen to enter the higher-level content management and administration menus.

== Content Types ==

The content types available on DMC at the time of launch are the following.

*Api page (api_page) – These are specially coded pages for the api docs. The drupal developer should be the one to make updates here.
*Book page (book) – A book page is a page of content, organized into a collection of related entries collectively known as a book. A book page automatically displays links to adjacent pages, providing a simple navigation system for organizing and reviewing structured content.
*Event (event) – All events retrieved from main site by RSS/XML feed.
*External guide (guide_external) – Places a teaser into guide sections, allowing to link to external guides.
*Feed (feed) – Subscribe to RSS or Atom feeds. Creates nodes of the content type "Feed item" from feed content.
*Feed item (feed_item) – This content type is being used for automatically aggregated content from feeds.
*Guide (guide) – Used for practically everything, but primarily guides and tutorials. Must be categorized by type of guide (corresponds with the sub navigation in the guide section).
*Note (note) – Notes are simple pages, used in such places as Developer notes and Release notes. They provide a left hand navigation structure on their list pages.
*Page (page) – A general free-form HTML page (DO NOT CURRENTLY USE, if you think its needed its important to try to abstract the need and make a general content type if possible)
*Promotional block (promo) – A Promotional block can be used to place a content teaser into a section head or on the home page with different text or images then are found in the content itself.
*Section head (section_head) – Top level pages (Home, Introduction, ....). The Section head type is used to show a selection of content in a block layout.
*Section head with lists (section_head_view) – Top level pages with embedded views (lists, like guides). The Section head type is used to show a selection of content in blocks around a dominant content list.

For the majority of people only use the Guide information format.

To see this list, click on the '''wrench''' at the top left hand of the screen, then '''Content management > Content types'''.

== Add new content types or edit existing content types ==
When you are viewing the list of content types (W'''rench > Content management > Content types''') look at the menu at the top right of the content list. From here you can “'''add content type'''” or edit the “f'''ields'''” of existing content types.

[[File:screen1.png]]

== Browse/view content ==
Go to '''Wrench > Content management > Content list'''.

You can browse content by whether it’s published or not, type, date posted, or date uploaded.

[[File:screen3.png]]

Click on a content item in the list to view it, or “'''Edit'''” to make changes.

== Create content ==
Go to '''Wrench > Create content'''. From the black navigation frame on the left, choose which type of content you would like to add.

<IMG>

When you click on each content type, you will get a template to fill in with all the required and optional fields. Entering this information is very straightforward and help is available by hovering over a field you wish to learn more about.

Required fields are marked with a red asterisk.

If the content you have entered contains HTML, you may wish to select either enhanced HTML or raw as your format type (consult this help for more information: [http://developer.meego.com/filter/tips http://developer.meego.com/filter/tips]).

== Tips for creating content ==

=== External guides and guides ===

If you would like to connect several guides together as a “book” the developers could progress through, click on “'''Book outline'''” at the bottom of the Create Guide/External Guide page.

In the book field, you can either create a new book or add the guide to an existing book.

<IMG>

To ensure your guide/external guide has a description in the guide lists, click on '''List information''' at the bottom of the Create Guide/External guide page and enter a brief description. You can also upload an image here so it will have an image in the guide list page as well.

<IMG>

=== For all content types (but most likely pages or guides) ===

==== Content in menus ====
If you would like a page or guide to show up in the sub-navigation, click on “'''Menu'''” at the bottom of the Create <content type> page. In the '''PARENT ITEM''' field, select the navigation element you would like the page to appear under, then name it in '''MENU LINK TITLE'''.

<IMG>

==== Meta tags ====
Here you can add the metadata description, which will help people searching determine whether that page is relevant or not. Make metadata descriptions approximately 150 chars (with spaces) or less.

=== Section heads and Section heads w/lists ===
These are the landing pages of the site, and here you will most likely want to add promotional blocks as the content used here. So therefore, it’s prudent to create your promotional blocks first, then start adding the promo block titles in the “'''Content to feature'''” fields on the Create Section head page.

<IMG>

You can also adjust the layout of the promo blocks on a section head page by clicking on “'''Row layout'''” at the bottom of the Create page, then selecting the desired amount of promo blocks in each row.

<IMG>

Top links can be used to add more teasers in the banner area of the landing pages (section heads), but as they are not very attractive, they should be used with caution, perhaps only to show major/critical announcements.

== Edit content ==
You can edit content either from the Content list, or by navigating to the page you would like to edit and selecting '''Edit''' from the menu on the left hand side. If you do not see this menu, click '''X''' to close the content management menu:

<IMG>

It will return to the wrench icon and you should see the option to “'''Edit'''” the page.

== Delete content ==
Go to the page you would like to delete, click on '''Edit''', then '''Delete'''.

== Remove promo blocks from section heads ==
If you wish to delete a promo block from a section head, but still keep the promo block, go to the section head and click '''Edit'''. Then in the “'''Content to feature”''' field, just delete the title of the promo block you want to remove.

== Changing navigation and sub-navigation ==
Go to '''Wrench > Administer > Site Building > Menus > Primary links'''.

<IMG>

Here you can enable, disable, edit and delete what is shown in the navigation. Click '''Save configuration''' when you are done.

Application developer site/Drupal guidelines

2011-04-03T14:58:18Z

Verbosemode: /* Add new content types or edit existing content types */

= Application Developer Site - Drupal guidelines =

== Location ==

The development/staging site is [http://meego.dev.dh-te.com here]. To get access please contact Ronan Mac Laverty (macron/maclaver).

== Access rights ==

To create content on the developer.meego.com site you need to have editor privileges. These can be obtained from the following people:
* Teemu Lukkari (ActiveArk)
* Ronan Mac Laverty (Nokia)
* Gil Quim (Nokia)
* Michael Shaver (Intel)
* Bob Spencer (Intel)

== Logging in ==

Those who have been given access writes to the DMC CMS may log in at the following address:

http://developer.meego.com/user

Enter your username and password, which are the same you use for all other sites in the MeeGo ecosystem. Click on Log in to enter.

Once you log in, you will see this screen:

[[File: screen2.png]]

From this screen you can either edit existing content, browse/view the website content and structure, or create new content.

Click on the '''wrench (spanner)''' at the top left of your screen to enter the higher-level content management and administration menus.

== Content Types ==

The content types available on DMC at the time of launch are the following.

*Api page (api_page) – These are specially coded pages for the api docs. The drupal developer should be the one to make updates here.
*Book page (book) – A book page is a page of content, organized into a collection of related entries collectively known as a book. A book page automatically displays links to adjacent pages, providing a simple navigation system for organizing and reviewing structured content.
*Event (event) – All events retrieved from main site by RSS/XML feed.
*External guide (guide_external) – Places a teaser into guide sections, allowing to link to external guides.
*Feed (feed) – Subscribe to RSS or Atom feeds. Creates nodes of the content type "Feed item" from feed content.
*Feed item (feed_item) – This content type is being used for automatically aggregated content from feeds.
*Guide (guide) – Used for practically everything, but primarily guides and tutorials. Must be categorized by type of guide (corresponds with the sub navigation in the guide section).
*Note (note) – Notes are simple pages, used in such places as Developer notes and Release notes. They provide a left hand navigation structure on their list pages.
*Page (page) – A general free-form HTML page (DO NOT CURRENTLY USE, if you think its needed its important to try to abstract the need and make a general content type if possible)
*Promotional block (promo) – A Promotional block can be used to place a content teaser into a section head or on the home page with different text or images then are found in the content itself.
*Section head (section_head) – Top level pages (Home, Introduction, ....). The Section head type is used to show a selection of content in a block layout.
*Section head with lists (section_head_view) – Top level pages with embedded views (lists, like guides). The Section head type is used to show a selection of content in blocks around a dominant content list.

For the majority of people only use the Guide information format.

To see this list, click on the '''wrench''' at the top left hand of the screen, then '''Content management > Content types'''.

== Add new content types or edit existing content types ==
When you are viewing the list of content types (W'''rench > Content management > Content types''') look at the menu at the top right of the content list. From here you can “'''add content type'''” or edit the “f'''ields'''” of existing content types.

[[File:screen1.png]]

== Browse/view content ==
Go to '''Wrench > Content management > Content list'''.

You can browse content by whether it’s published or not, type, date posted, or date uploaded.

<IMG PLACEHOLDER>

Click on a content item in the list to view it, or “'''Edit'''” to make changes.

== Create content ==
Go to '''Wrench > Create content'''. From the black navigation frame on the left, choose which type of content you would like to add.

<IMG>

When you click on each content type, you will get a template to fill in with all the required and optional fields. Entering this information is very straightforward and help is available by hovering over a field you wish to learn more about.

Required fields are marked with a red asterisk.

If the content you have entered contains HTML, you may wish to select either enhanced HTML or raw as your format type (consult this help for more information: [http://developer.meego.com/filter/tips http://developer.meego.com/filter/tips]).

== Tips for creating content ==

=== External guides and guides ===

If you would like to connect several guides together as a “book” the developers could progress through, click on “'''Book outline'''” at the bottom of the Create Guide/External Guide page.

In the book field, you can either create a new book or add the guide to an existing book.

<IMG>

To ensure your guide/external guide has a description in the guide lists, click on '''List information''' at the bottom of the Create Guide/External guide page and enter a brief description. You can also upload an image here so it will have an image in the guide list page as well.

<IMG>

=== For all content types (but most likely pages or guides) ===

==== Content in menus ====
If you would like a page or guide to show up in the sub-navigation, click on “'''Menu'''” at the bottom of the Create <content type> page. In the '''PARENT ITEM''' field, select the navigation element you would like the page to appear under, then name it in '''MENU LINK TITLE'''.

<IMG>

==== Meta tags ====
Here you can add the metadata description, which will help people searching determine whether that page is relevant or not. Make metadata descriptions approximately 150 chars (with spaces) or less.

=== Section heads and Section heads w/lists ===
These are the landing pages of the site, and here you will most likely want to add promotional blocks as the content used here. So therefore, it’s prudent to create your promotional blocks first, then start adding the promo block titles in the “'''Content to feature'''” fields on the Create Section head page.

<IMG>

You can also adjust the layout of the promo blocks on a section head page by clicking on “'''Row layout'''” at the bottom of the Create page, then selecting the desired amount of promo blocks in each row.

<IMG>

Top links can be used to add more teasers in the banner area of the landing pages (section heads), but as they are not very attractive, they should be used with caution, perhaps only to show major/critical announcements.

== Edit content ==
You can edit content either from the Content list, or by navigating to the page you would like to edit and selecting '''Edit''' from the menu on the left hand side. If you do not see this menu, click '''X''' to close the content management menu:

<IMG>

It will return to the wrench icon and you should see the option to “'''Edit'''” the page.

== Delete content ==
Go to the page you would like to delete, click on '''Edit''', then '''Delete'''.

== Remove promo blocks from section heads ==
If you wish to delete a promo block from a section head, but still keep the promo block, go to the section head and click '''Edit'''. Then in the “'''Content to feature”''' field, just delete the title of the promo block you want to remove.

== Changing navigation and sub-navigation ==
Go to '''Wrench > Administer > Site Building > Menus > Primary links'''.

<IMG>

Here you can enable, disable, edit and delete what is shown in the navigation. Click '''Save configuration''' when you are done.

Application developer site/Drupal guidelines

2011-04-03T14:57:52Z

Verbosemode: /* Content Types */

= Application Developer Site - Drupal guidelines =

== Location ==

The development/staging site is [http://meego.dev.dh-te.com here]. To get access please contact Ronan Mac Laverty (macron/maclaver).

== Access rights ==

To create content on the developer.meego.com site you need to have editor privileges. These can be obtained from the following people:
* Teemu Lukkari (ActiveArk)
* Ronan Mac Laverty (Nokia)
* Gil Quim (Nokia)
* Michael Shaver (Intel)
* Bob Spencer (Intel)

== Logging in ==

Those who have been given access writes to the DMC CMS may log in at the following address:

http://developer.meego.com/user

Enter your username and password, which are the same you use for all other sites in the MeeGo ecosystem. Click on Log in to enter.

Once you log in, you will see this screen:

[[File: screen2.png]]

From this screen you can either edit existing content, browse/view the website content and structure, or create new content.

Click on the '''wrench (spanner)''' at the top left of your screen to enter the higher-level content management and administration menus.

== Content Types ==

The content types available on DMC at the time of launch are the following.

*Api page (api_page) – These are specially coded pages for the api docs. The drupal developer should be the one to make updates here.
*Book page (book) – A book page is a page of content, organized into a collection of related entries collectively known as a book. A book page automatically displays links to adjacent pages, providing a simple navigation system for organizing and reviewing structured content.
*Event (event) – All events retrieved from main site by RSS/XML feed.
*External guide (guide_external) – Places a teaser into guide sections, allowing to link to external guides.
*Feed (feed) – Subscribe to RSS or Atom feeds. Creates nodes of the content type "Feed item" from feed content.
*Feed item (feed_item) – This content type is being used for automatically aggregated content from feeds.
*Guide (guide) – Used for practically everything, but primarily guides and tutorials. Must be categorized by type of guide (corresponds with the sub navigation in the guide section).
*Note (note) – Notes are simple pages, used in such places as Developer notes and Release notes. They provide a left hand navigation structure on their list pages.
*Page (page) – A general free-form HTML page (DO NOT CURRENTLY USE, if you think its needed its important to try to abstract the need and make a general content type if possible)
*Promotional block (promo) – A Promotional block can be used to place a content teaser into a section head or on the home page with different text or images then are found in the content itself.
*Section head (section_head) – Top level pages (Home, Introduction, ....). The Section head type is used to show a selection of content in a block layout.
*Section head with lists (section_head_view) – Top level pages with embedded views (lists, like guides). The Section head type is used to show a selection of content in blocks around a dominant content list.

For the majority of people only use the Guide information format.

To see this list, click on the '''wrench''' at the top left hand of the screen, then '''Content management > Content types'''.

== Add new content types or edit existing content types ==
When you are viewing the list of content types (W'''rench > Content management > Content types''') look at the menu at the top right of the content list. From here you can “'''add content type'''” or edit the “f'''ields'''” of existing content types.

<IMG PLACEHOLDER>

== Browse/view content ==
Go to '''Wrench > Content management > Content list'''.

You can browse content by whether it’s published or not, type, date posted, or date uploaded.

<IMG PLACEHOLDER>

Click on a content item in the list to view it, or “'''Edit'''” to make changes.

== Create content ==
Go to '''Wrench > Create content'''. From the black navigation frame on the left, choose which type of content you would like to add.

<IMG>

When you click on each content type, you will get a template to fill in with all the required and optional fields. Entering this information is very straightforward and help is available by hovering over a field you wish to learn more about.

Required fields are marked with a red asterisk.

If the content you have entered contains HTML, you may wish to select either enhanced HTML or raw as your format type (consult this help for more information: [http://developer.meego.com/filter/tips http://developer.meego.com/filter/tips]).

== Tips for creating content ==

=== External guides and guides ===

If you would like to connect several guides together as a “book” the developers could progress through, click on “'''Book outline'''” at the bottom of the Create Guide/External Guide page.

In the book field, you can either create a new book or add the guide to an existing book.

<IMG>

To ensure your guide/external guide has a description in the guide lists, click on '''List information''' at the bottom of the Create Guide/External guide page and enter a brief description. You can also upload an image here so it will have an image in the guide list page as well.

<IMG>

=== For all content types (but most likely pages or guides) ===

==== Content in menus ====
If you would like a page or guide to show up in the sub-navigation, click on “'''Menu'''” at the bottom of the Create <content type> page. In the '''PARENT ITEM''' field, select the navigation element you would like the page to appear under, then name it in '''MENU LINK TITLE'''.

<IMG>

==== Meta tags ====
Here you can add the metadata description, which will help people searching determine whether that page is relevant or not. Make metadata descriptions approximately 150 chars (with spaces) or less.

=== Section heads and Section heads w/lists ===
These are the landing pages of the site, and here you will most likely want to add promotional blocks as the content used here. So therefore, it’s prudent to create your promotional blocks first, then start adding the promo block titles in the “'''Content to feature'''” fields on the Create Section head page.

<IMG>

You can also adjust the layout of the promo blocks on a section head page by clicking on “'''Row layout'''” at the bottom of the Create page, then selecting the desired amount of promo blocks in each row.

<IMG>

Top links can be used to add more teasers in the banner area of the landing pages (section heads), but as they are not very attractive, they should be used with caution, perhaps only to show major/critical announcements.

== Edit content ==
You can edit content either from the Content list, or by navigating to the page you would like to edit and selecting '''Edit''' from the menu on the left hand side. If you do not see this menu, click '''X''' to close the content management menu:

<IMG>

It will return to the wrench icon and you should see the option to “'''Edit'''” the page.

== Delete content ==
Go to the page you would like to delete, click on '''Edit''', then '''Delete'''.

== Remove promo blocks from section heads ==
If you wish to delete a promo block from a section head, but still keep the promo block, go to the section head and click '''Edit'''. Then in the “'''Content to feature”''' field, just delete the title of the promo block you want to remove.

== Changing navigation and sub-navigation ==
Go to '''Wrench > Administer > Site Building > Menus > Primary links'''.

<IMG>

Here you can enable, disable, edit and delete what is shown in the navigation. Click '''Save configuration''' when you are done.

Application developer site/Drupal guidelines

2011-04-03T14:57:15Z

Verbosemode: /* Content Types */

= Application Developer Site - Drupal guidelines =

== Location ==

The development/staging site is [http://meego.dev.dh-te.com here]. To get access please contact Ronan Mac Laverty (macron/maclaver).

== Access rights ==

To create content on the developer.meego.com site you need to have editor privileges. These can be obtained from the following people:
* Teemu Lukkari (ActiveArk)
* Ronan Mac Laverty (Nokia)
* Gil Quim (Nokia)
* Michael Shaver (Intel)
* Bob Spencer (Intel)

== Logging in ==

Those who have been given access writes to the DMC CMS may log in at the following address:

http://developer.meego.com/user

Enter your username and password, which are the same you use for all other sites in the MeeGo ecosystem. Click on Log in to enter.

Once you log in, you will see this screen:

[[File: screen2.png]]

From this screen you can either edit existing content, browse/view the website content and structure, or create new content.

Click on the '''wrench (spanner)''' at the top left of your screen to enter the higher-level content management and administration menus.

== Content Types ==

The content types available on DMC at the time of launch are the following.

*Api page (api_page) – These are specially coded pages for the api docs. The drupal developer should be the one to make updates here.
*Book page (book) – A book page is a page of content, organized into a collection of related entries collectively known as a book. A book page automatically displays links to adjacent pages, providing a simple navigation system for organizing and reviewing structured content.
*Event (event) – All events retrieved from main site by RSS/XML feed.
*External guide (guide_external) – Places a teaser into guide sections, allowing to link to external guides.
*Feed (feed) – Subscribe to RSS or Atom feeds. Creates nodes of the content type "Feed item" from feed content.
*Feed item (feed_item) – This content type is being used for automatically aggregated content from feeds.
*Guide (guide) – Used for practically everything, but primarily guides and tutorials. Must be categorized by type of guide (corresponds with the sub navigation in the guide section).
*Note (note) – Notes are simple pages, used in such places as Developer notes and Release notes. They provide a left hand navigation structure on their list pages.
*Page (page) – A general free-form HTML page (DO NOT CURRENTLY USE, if you think its needed its important to try to abstract the need and make a general content type if possible)
*Promotional block (promo) – A Promotional block can be used to place a content teaser into a section head or on the home page with different text or images then are found in the content itself.
*Section head (section_head) – Top level pages (Home, Introduction, ....). The Section head type is used to show a selection of content in a block layout.
*Section head with lists (section_head_view) – Top level pages with embedded views (lists, like guides). The Section head type is used to show a selection of content in blocks around a dominant content list.

For the majority of people only use the Guide information format.

To see this list, click on the '''wrench''' at the top left hand of the screen, then '''Content management > Content types'''.

[[File:screen1.png]]

== Add new content types or edit existing content types ==
When you are viewing the list of content types (W'''rench > Content management > Content types''') look at the menu at the top right of the content list. From here you can “'''add content type'''” or edit the “f'''ields'''” of existing content types.

<IMG PLACEHOLDER>

== Browse/view content ==
Go to '''Wrench > Content management > Content list'''.

You can browse content by whether it’s published or not, type, date posted, or date uploaded.

<IMG PLACEHOLDER>

Click on a content item in the list to view it, or “'''Edit'''” to make changes.

== Create content ==
Go to '''Wrench > Create content'''. From the black navigation frame on the left, choose which type of content you would like to add.

<IMG>

When you click on each content type, you will get a template to fill in with all the required and optional fields. Entering this information is very straightforward and help is available by hovering over a field you wish to learn more about.

Required fields are marked with a red asterisk.

If the content you have entered contains HTML, you may wish to select either enhanced HTML or raw as your format type (consult this help for more information: [http://developer.meego.com/filter/tips http://developer.meego.com/filter/tips]).

== Tips for creating content ==

=== External guides and guides ===

If you would like to connect several guides together as a “book” the developers could progress through, click on “'''Book outline'''” at the bottom of the Create Guide/External Guide page.

In the book field, you can either create a new book or add the guide to an existing book.

<IMG>

To ensure your guide/external guide has a description in the guide lists, click on '''List information''' at the bottom of the Create Guide/External guide page and enter a brief description. You can also upload an image here so it will have an image in the guide list page as well.

<IMG>

=== For all content types (but most likely pages or guides) ===

==== Content in menus ====
If you would like a page or guide to show up in the sub-navigation, click on “'''Menu'''” at the bottom of the Create <content type> page. In the '''PARENT ITEM''' field, select the navigation element you would like the page to appear under, then name it in '''MENU LINK TITLE'''.

<IMG>

==== Meta tags ====
Here you can add the metadata description, which will help people searching determine whether that page is relevant or not. Make metadata descriptions approximately 150 chars (with spaces) or less.

=== Section heads and Section heads w/lists ===
These are the landing pages of the site, and here you will most likely want to add promotional blocks as the content used here. So therefore, it’s prudent to create your promotional blocks first, then start adding the promo block titles in the “'''Content to feature'''” fields on the Create Section head page.

<IMG>

You can also adjust the layout of the promo blocks on a section head page by clicking on “'''Row layout'''” at the bottom of the Create page, then selecting the desired amount of promo blocks in each row.

<IMG>

Top links can be used to add more teasers in the banner area of the landing pages (section heads), but as they are not very attractive, they should be used with caution, perhaps only to show major/critical announcements.

== Edit content ==
You can edit content either from the Content list, or by navigating to the page you would like to edit and selecting '''Edit''' from the menu on the left hand side. If you do not see this menu, click '''X''' to close the content management menu:

<IMG>

It will return to the wrench icon and you should see the option to “'''Edit'''” the page.

== Delete content ==
Go to the page you would like to delete, click on '''Edit''', then '''Delete'''.

== Remove promo blocks from section heads ==
If you wish to delete a promo block from a section head, but still keep the promo block, go to the section head and click '''Edit'''. Then in the “'''Content to feature”''' field, just delete the title of the promo block you want to remove.

== Changing navigation and sub-navigation ==
Go to '''Wrench > Administer > Site Building > Menus > Primary links'''.

<IMG>

Here you can enable, disable, edit and delete what is shown in the navigation. Click '''Save configuration''' when you are done.

Application developer site/Drupal guidelines

2011-04-03T14:56:29Z

Verbosemode: /* Logging in */

= Application Developer Site - Drupal guidelines =

== Location ==

The development/staging site is [http://meego.dev.dh-te.com here]. To get access please contact Ronan Mac Laverty (macron/maclaver).

== Access rights ==

To create content on the developer.meego.com site you need to have editor privileges. These can be obtained from the following people:
* Teemu Lukkari (ActiveArk)
* Ronan Mac Laverty (Nokia)
* Gil Quim (Nokia)
* Michael Shaver (Intel)
* Bob Spencer (Intel)

== Logging in ==

Those who have been given access writes to the DMC CMS may log in at the following address:

http://developer.meego.com/user

Enter your username and password, which are the same you use for all other sites in the MeeGo ecosystem. Click on Log in to enter.

Once you log in, you will see this screen:

[[File: screen2.png]]

From this screen you can either edit existing content, browse/view the website content and structure, or create new content.

Click on the '''wrench (spanner)''' at the top left of your screen to enter the higher-level content management and administration menus.

== Content Types ==

The content types available on DMC at the time of launch are the following.

*Api page (api_page) – These are specially coded pages for the api docs. The drupal developer should be the one to make updates here.
*Book page (book) – A book page is a page of content, organized into a collection of related entries collectively known as a book. A book page automatically displays links to adjacent pages, providing a simple navigation system for organizing and reviewing structured content.
*Event (event) – All events retrieved from main site by RSS/XML feed.
*External guide (guide_external) – Places a teaser into guide sections, allowing to link to external guides.
*Feed (feed) – Subscribe to RSS or Atom feeds. Creates nodes of the content type "Feed item" from feed content.
*Feed item (feed_item) – This content type is being used for automatically aggregated content from feeds.
*Guide (guide) – Used for practically everything, but primarily guides and tutorials. Must be categorized by type of guide (corresponds with the sub navigation in the guide section).
*Note (note) – Notes are simple pages, used in such places as Developer notes and Release notes. They provide a left hand navigation structure on their list pages.
*Page (page) – A general free-form HTML page (DO NOT CURRENTLY USE, if you think its needed its important to try to abstract the need and make a general content type if possible)
*Promotional block (promo) – A Promotional block can be used to place a content teaser into a section head or on the home page with different text or images then are found in the content itself.
*Section head (section_head) – Top level pages (Home, Introduction, ....). The Section head type is used to show a selection of content in a block layout.
*Section head with lists (section_head_view) – Top level pages with embedded views (lists, like guides). The Section head type is used to show a selection of content in blocks around a dominant content list.

For the majority of people only use the Guide information format.

To see this list, click on the '''wrench''' at the top left hand of the screen, then '''Content management > Content types'''.

== Add new content types or edit existing content types ==
When you are viewing the list of content types (W'''rench > Content management > Content types''') look at the menu at the top right of the content list. From here you can “'''add content type'''” or edit the “f'''ields'''” of existing content types.

<IMG PLACEHOLDER>

== Browse/view content ==
Go to '''Wrench > Content management > Content list'''.

You can browse content by whether it’s published or not, type, date posted, or date uploaded.

<IMG PLACEHOLDER>

Click on a content item in the list to view it, or “'''Edit'''” to make changes.

== Create content ==
Go to '''Wrench > Create content'''. From the black navigation frame on the left, choose which type of content you would like to add.

<IMG>

When you click on each content type, you will get a template to fill in with all the required and optional fields. Entering this information is very straightforward and help is available by hovering over a field you wish to learn more about.

Required fields are marked with a red asterisk.

If the content you have entered contains HTML, you may wish to select either enhanced HTML or raw as your format type (consult this help for more information: [http://developer.meego.com/filter/tips http://developer.meego.com/filter/tips]).

== Tips for creating content ==

=== External guides and guides ===

If you would like to connect several guides together as a “book” the developers could progress through, click on “'''Book outline'''” at the bottom of the Create Guide/External Guide page.

In the book field, you can either create a new book or add the guide to an existing book.

<IMG>

To ensure your guide/external guide has a description in the guide lists, click on '''List information''' at the bottom of the Create Guide/External guide page and enter a brief description. You can also upload an image here so it will have an image in the guide list page as well.

<IMG>

=== For all content types (but most likely pages or guides) ===

==== Content in menus ====
If you would like a page or guide to show up in the sub-navigation, click on “'''Menu'''” at the bottom of the Create <content type> page. In the '''PARENT ITEM''' field, select the navigation element you would like the page to appear under, then name it in '''MENU LINK TITLE'''.

<IMG>

==== Meta tags ====
Here you can add the metadata description, which will help people searching determine whether that page is relevant or not. Make metadata descriptions approximately 150 chars (with spaces) or less.

=== Section heads and Section heads w/lists ===
These are the landing pages of the site, and here you will most likely want to add promotional blocks as the content used here. So therefore, it’s prudent to create your promotional blocks first, then start adding the promo block titles in the “'''Content to feature'''” fields on the Create Section head page.

<IMG>

You can also adjust the layout of the promo blocks on a section head page by clicking on “'''Row layout'''” at the bottom of the Create page, then selecting the desired amount of promo blocks in each row.

<IMG>

Top links can be used to add more teasers in the banner area of the landing pages (section heads), but as they are not very attractive, they should be used with caution, perhaps only to show major/critical announcements.

== Edit content ==
You can edit content either from the Content list, or by navigating to the page you would like to edit and selecting '''Edit''' from the menu on the left hand side. If you do not see this menu, click '''X''' to close the content management menu:

<IMG>

It will return to the wrench icon and you should see the option to “'''Edit'''” the page.

== Delete content ==
Go to the page you would like to delete, click on '''Edit''', then '''Delete'''.

== Remove promo blocks from section heads ==
If you wish to delete a promo block from a section head, but still keep the promo block, go to the section head and click '''Edit'''. Then in the “'''Content to feature”''' field, just delete the title of the promo block you want to remove.

== Changing navigation and sub-navigation ==
Go to '''Wrench > Administer > Site Building > Menus > Primary links'''.

<IMG>

Here you can enable, disable, edit and delete what is shown in the navigation. Click '''Save configuration''' when you are done.

Application developer site/Drupal guidelines

2011-04-03T14:55:51Z

Verbosemode: /* Logging in */

= Application Developer Site - Drupal guidelines =

== Location ==

The development/staging site is [http://meego.dev.dh-te.com here]. To get access please contact Ronan Mac Laverty (macron/maclaver).

== Access rights ==

To create content on the developer.meego.com site you need to have editor privileges. These can be obtained from the following people:
* Teemu Lukkari (ActiveArk)
* Ronan Mac Laverty (Nokia)
* Gil Quim (Nokia)
* Michael Shaver (Intel)
* Bob Spencer (Intel)

== Logging in ==

Those who have been given access writes to the DMC CMS may log in at the following address:

http://developer.meego.com/user

Enter your username and password, which are the same you use for all other sites in the MeeGo ecosystem. Click on Log in to enter.

Once you log in, you will see this screen:

[[File: screen1.png]]

From this screen you can either edit existing content, browse/view the website content and structure, or create new content.

Click on the '''wrench (spanner)''' at the top left of your screen to enter the higher-level content management and administration menus.

== Content Types ==

The content types available on DMC at the time of launch are the following.

*Api page (api_page) – These are specially coded pages for the api docs. The drupal developer should be the one to make updates here.
*Book page (book) – A book page is a page of content, organized into a collection of related entries collectively known as a book. A book page automatically displays links to adjacent pages, providing a simple navigation system for organizing and reviewing structured content.
*Event (event) – All events retrieved from main site by RSS/XML feed.
*External guide (guide_external) – Places a teaser into guide sections, allowing to link to external guides.
*Feed (feed) – Subscribe to RSS or Atom feeds. Creates nodes of the content type "Feed item" from feed content.
*Feed item (feed_item) – This content type is being used for automatically aggregated content from feeds.
*Guide (guide) – Used for practically everything, but primarily guides and tutorials. Must be categorized by type of guide (corresponds with the sub navigation in the guide section).
*Note (note) – Notes are simple pages, used in such places as Developer notes and Release notes. They provide a left hand navigation structure on their list pages.
*Page (page) – A general free-form HTML page (DO NOT CURRENTLY USE, if you think its needed its important to try to abstract the need and make a general content type if possible)
*Promotional block (promo) – A Promotional block can be used to place a content teaser into a section head or on the home page with different text or images then are found in the content itself.
*Section head (section_head) – Top level pages (Home, Introduction, ....). The Section head type is used to show a selection of content in a block layout.
*Section head with lists (section_head_view) – Top level pages with embedded views (lists, like guides). The Section head type is used to show a selection of content in blocks around a dominant content list.

For the majority of people only use the Guide information format.

To see this list, click on the '''wrench''' at the top left hand of the screen, then '''Content management > Content types'''.

== Add new content types or edit existing content types ==
When you are viewing the list of content types (W'''rench > Content management > Content types''') look at the menu at the top right of the content list. From here you can “'''add content type'''” or edit the “f'''ields'''” of existing content types.

<IMG PLACEHOLDER>

== Browse/view content ==
Go to '''Wrench > Content management > Content list'''.

You can browse content by whether it’s published or not, type, date posted, or date uploaded.

<IMG PLACEHOLDER>

Click on a content item in the list to view it, or “'''Edit'''” to make changes.

== Create content ==
Go to '''Wrench > Create content'''. From the black navigation frame on the left, choose which type of content you would like to add.

<IMG>

When you click on each content type, you will get a template to fill in with all the required and optional fields. Entering this information is very straightforward and help is available by hovering over a field you wish to learn more about.

Required fields are marked with a red asterisk.

If the content you have entered contains HTML, you may wish to select either enhanced HTML or raw as your format type (consult this help for more information: [http://developer.meego.com/filter/tips http://developer.meego.com/filter/tips]).

== Tips for creating content ==

=== External guides and guides ===

If you would like to connect several guides together as a “book” the developers could progress through, click on “'''Book outline'''” at the bottom of the Create Guide/External Guide page.

In the book field, you can either create a new book or add the guide to an existing book.

<IMG>

To ensure your guide/external guide has a description in the guide lists, click on '''List information''' at the bottom of the Create Guide/External guide page and enter a brief description. You can also upload an image here so it will have an image in the guide list page as well.

<IMG>

=== For all content types (but most likely pages or guides) ===

==== Content in menus ====
If you would like a page or guide to show up in the sub-navigation, click on “'''Menu'''” at the bottom of the Create <content type> page. In the '''PARENT ITEM''' field, select the navigation element you would like the page to appear under, then name it in '''MENU LINK TITLE'''.

<IMG>

==== Meta tags ====
Here you can add the metadata description, which will help people searching determine whether that page is relevant or not. Make metadata descriptions approximately 150 chars (with spaces) or less.

=== Section heads and Section heads w/lists ===
These are the landing pages of the site, and here you will most likely want to add promotional blocks as the content used here. So therefore, it’s prudent to create your promotional blocks first, then start adding the promo block titles in the “'''Content to feature'''” fields on the Create Section head page.

<IMG>

You can also adjust the layout of the promo blocks on a section head page by clicking on “'''Row layout'''” at the bottom of the Create page, then selecting the desired amount of promo blocks in each row.

<IMG>

Top links can be used to add more teasers in the banner area of the landing pages (section heads), but as they are not very attractive, they should be used with caution, perhaps only to show major/critical announcements.

== Edit content ==
You can edit content either from the Content list, or by navigating to the page you would like to edit and selecting '''Edit''' from the menu on the left hand side. If you do not see this menu, click '''X''' to close the content management menu:

<IMG>

It will return to the wrench icon and you should see the option to “'''Edit'''” the page.

== Delete content ==
Go to the page you would like to delete, click on '''Edit''', then '''Delete'''.

== Remove promo blocks from section heads ==
If you wish to delete a promo block from a section head, but still keep the promo block, go to the section head and click '''Edit'''. Then in the “'''Content to feature”''' field, just delete the title of the promo block you want to remove.

== Changing navigation and sub-navigation ==
Go to '''Wrench > Administer > Site Building > Menus > Primary links'''.

<IMG>

Here you can enable, disable, edit and delete what is shown in the navigation. Click '''Save configuration''' when you are done.

File:Screen11.png

2011-04-03T14:53:23Z

Verbosemode:

File:Screen10.png

2011-04-03T14:53:04Z

Verbosemode:

File:Screen9.png

2011-04-03T14:52:23Z

Verbosemode:

File:Screen8.png

2011-04-03T14:51:53Z

Verbosemode:

File:Screen7.png

2011-04-03T14:51:31Z

Verbosemode:

File:Screen6.png

2011-04-03T14:50:07Z

Verbosemode:

File:Screen5.png

2011-04-03T14:49:27Z

Verbosemode:

File:Screen4.png

2011-04-03T14:46:54Z

Verbosemode:

File:Screen3.png

2011-04-03T14:46:35Z

Verbosemode:

File:Screen2.png

2011-04-03T14:42:59Z

Verbosemode:

File:Screen1.png

2011-04-03T14:41:20Z

Verbosemode:

Application developer site/Drupal guidelines

2011-04-03T14:37:04Z

Verbosemode: /* Logging in */

= Application Developer Site - Drupal guidelines =

== Location ==

The development/staging site is [http://meego.dev.dh-te.com here]. To get access please contact Ronan Mac Laverty (macron/maclaver).

== Access rights ==

To create content on the developer.meego.com site you need to have editor privileges. These can be obtained from the following people:
* Teemu Lukkari (ActiveArk)
* Ronan Mac Laverty (Nokia)
* Gil Quim (Nokia)
* Michael Shaver (Intel)
* Bob Spencer (Intel)

== Logging in ==

Those who have been given access writes to the DMC CMS may log in at the following address:

http://developer.meego.com/user

Enter your username and password, which are the same you use for all other sites in the MeeGo ecosystem. Click on Log in to enter.

Once you log in, you will see this screen:

<IMG placeholder>

From this screen you can either edit existing content, browse/view the website content and structure, or create new content.

Click on the '''wrench (spanner)''' at the top left of your screen to enter the higher-level content management and administration menus.

== Content Types ==

The content types available on DMC at the time of launch are the following.

*Api page (api_page) – These are specially coded pages for the api docs. The drupal developer should be the one to make updates here.
*Book page (book) – A book page is a page of content, organized into a collection of related entries collectively known as a book. A book page automatically displays links to adjacent pages, providing a simple navigation system for organizing and reviewing structured content.
*Event (event) – All events retrieved from main site by RSS/XML feed.
*External guide (guide_external) – Places a teaser into guide sections, allowing to link to external guides.
*Feed (feed) – Subscribe to RSS or Atom feeds. Creates nodes of the content type "Feed item" from feed content.
*Feed item (feed_item) – This content type is being used for automatically aggregated content from feeds.
*Guide (guide) – Used for practically everything, but primarily guides and tutorials. Must be categorized by type of guide (corresponds with the sub navigation in the guide section).
*Note (note) – Notes are simple pages, used in such places as Developer notes and Release notes. They provide a left hand navigation structure on their list pages.
*Page (page) – A general free-form HTML page (DO NOT CURRENTLY USE, if you think its needed its important to try to abstract the need and make a general content type if possible)
*Promotional block (promo) – A Promotional block can be used to place a content teaser into a section head or on the home page with different text or images then are found in the content itself.
*Section head (section_head) – Top level pages (Home, Introduction, ....). The Section head type is used to show a selection of content in a block layout.
*Section head with lists (section_head_view) – Top level pages with embedded views (lists, like guides). The Section head type is used to show a selection of content in blocks around a dominant content list.

For the majority of people only use the Guide information format.

To see this list, click on the '''wrench''' at the top left hand of the screen, then '''Content management > Content types'''.

== Add new content types or edit existing content types ==
When you are viewing the list of content types (W'''rench > Content management > Content types''') look at the menu at the top right of the content list. From here you can “'''add content type'''” or edit the “f'''ields'''” of existing content types.

<IMG PLACEHOLDER>

== Browse/view content ==
Go to '''Wrench > Content management > Content list'''.

You can browse content by whether it’s published or not, type, date posted, or date uploaded.

<IMG PLACEHOLDER>

Click on a content item in the list to view it, or “'''Edit'''” to make changes.

== Create content ==
Go to '''Wrench > Create content'''. From the black navigation frame on the left, choose which type of content you would like to add.

<IMG>

When you click on each content type, you will get a template to fill in with all the required and optional fields. Entering this information is very straightforward and help is available by hovering over a field you wish to learn more about.

Required fields are marked with a red asterisk.

If the content you have entered contains HTML, you may wish to select either enhanced HTML or raw as your format type (consult this help for more information: [http://developer.meego.com/filter/tips http://developer.meego.com/filter/tips]).

== Tips for creating content ==

=== External guides and guides ===

If you would like to connect several guides together as a “book” the developers could progress through, click on “'''Book outline'''” at the bottom of the Create Guide/External Guide page.

In the book field, you can either create a new book or add the guide to an existing book.

<IMG>

To ensure your guide/external guide has a description in the guide lists, click on '''List information''' at the bottom of the Create Guide/External guide page and enter a brief description. You can also upload an image here so it will have an image in the guide list page as well.

<IMG>

=== For all content types (but most likely pages or guides) ===

==== Content in menus ====
If you would like a page or guide to show up in the sub-navigation, click on “'''Menu'''” at the bottom of the Create <content type> page. In the '''PARENT ITEM''' field, select the navigation element you would like the page to appear under, then name it in '''MENU LINK TITLE'''.

<IMG>

==== Meta tags ====
Here you can add the metadata description, which will help people searching determine whether that page is relevant or not. Make metadata descriptions approximately 150 chars (with spaces) or less.

=== Section heads and Section heads w/lists ===
These are the landing pages of the site, and here you will most likely want to add promotional blocks as the content used here. So therefore, it’s prudent to create your promotional blocks first, then start adding the promo block titles in the “'''Content to feature'''” fields on the Create Section head page.

<IMG>

You can also adjust the layout of the promo blocks on a section head page by clicking on “'''Row layout'''” at the bottom of the Create page, then selecting the desired amount of promo blocks in each row.

<IMG>

Top links can be used to add more teasers in the banner area of the landing pages (section heads), but as they are not very attractive, they should be used with caution, perhaps only to show major/critical announcements.

== Edit content ==
You can edit content either from the Content list, or by navigating to the page you would like to edit and selecting '''Edit''' from the menu on the left hand side. If you do not see this menu, click '''X''' to close the content management menu:

<IMG>

It will return to the wrench icon and you should see the option to “'''Edit'''” the page.

== Delete content ==
Go to the page you would like to delete, click on '''Edit''', then '''Delete'''.

== Remove promo blocks from section heads ==
If you wish to delete a promo block from a section head, but still keep the promo block, go to the section head and click '''Edit'''. Then in the “'''Content to feature”''' field, just delete the title of the promo block you want to remove.

== Changing navigation and sub-navigation ==
Go to '''Wrench > Administer > Site Building > Menus > Primary links'''.

<IMG>

Here you can enable, disable, edit and delete what is shown in the navigation. Click '''Save configuration''' when you are done.

Application developer site/Drupal guidelines

2011-04-03T14:36:21Z

Verbosemode: More detailed guide for content editors

= Application Developer Site - Drupal guidelines =

== Location ==

The development/staging site is [http://meego.dev.dh-te.com here]. To get access please contact Ronan Mac Laverty (macron/maclaver).

== Access rights ==

To create content on the developer.meego.com site you need to have editor privileges. These can be obtained from the following people:
* Teemu Lukkari (ActiveArk)
* Ronan Mac Laverty (Nokia)
* Gil Quim (Nokia)
* Michael Shaver (Intel)
* Bob Spencer (Intel)

== Logging in ==

Those who have been given access writes to the DMC CMS may log in at the following address:

http://developer.meego.com/user

Enter your username and password, which are the same you use for all other sites in the MeeGo ecosystem. Click on Log in to enter.

Once you log in, you will see this screen:

<IMG placeholder>

From this screen you can either edit existing content, browse/view the website content and structure, or create new content.

1) Click on the wrench (spanner) at the top left of your screen to enter the higher-level content management and administration menus.

== Content Types ==

The content types available on DMC at the time of launch are the following.

*Api page (api_page) – These are specially coded pages for the api docs. The drupal developer should be the one to make updates here.
*Book page (book) – A book page is a page of content, organized into a collection of related entries collectively known as a book. A book page automatically displays links to adjacent pages, providing a simple navigation system for organizing and reviewing structured content.
*Event (event) – All events retrieved from main site by RSS/XML feed.
*External guide (guide_external) – Places a teaser into guide sections, allowing to link to external guides.
*Feed (feed) – Subscribe to RSS or Atom feeds. Creates nodes of the content type "Feed item" from feed content.
*Feed item (feed_item) – This content type is being used for automatically aggregated content from feeds.
*Guide (guide) – Used for practically everything, but primarily guides and tutorials. Must be categorized by type of guide (corresponds with the sub navigation in the guide section).
*Note (note) – Notes are simple pages, used in such places as Developer notes and Release notes. They provide a left hand navigation structure on their list pages.
*Page (page) – A general free-form HTML page (DO NOT CURRENTLY USE, if you think its needed its important to try to abstract the need and make a general content type if possible)
*Promotional block (promo) – A Promotional block can be used to place a content teaser into a section head or on the home page with different text or images then are found in the content itself.
*Section head (section_head) – Top level pages (Home, Introduction, ....). The Section head type is used to show a selection of content in a block layout.
*Section head with lists (section_head_view) – Top level pages with embedded views (lists, like guides). The Section head type is used to show a selection of content in blocks around a dominant content list.

For the majority of people only use the Guide information format.

To see this list, click on the '''wrench''' at the top left hand of the screen, then '''Content management > Content types'''.

== Add new content types or edit existing content types ==
When you are viewing the list of content types (W'''rench > Content management > Content types''') look at the menu at the top right of the content list. From here you can “'''add content type'''” or edit the “f'''ields'''” of existing content types.

<IMG PLACEHOLDER>

== Browse/view content ==
Go to '''Wrench > Content management > Content list'''.

You can browse content by whether it’s published or not, type, date posted, or date uploaded.

<IMG PLACEHOLDER>

Click on a content item in the list to view it, or “'''Edit'''” to make changes.

== Create content ==
Go to '''Wrench > Create content'''. From the black navigation frame on the left, choose which type of content you would like to add.

<IMG>

When you click on each content type, you will get a template to fill in with all the required and optional fields. Entering this information is very straightforward and help is available by hovering over a field you wish to learn more about.

Required fields are marked with a red asterisk.

If the content you have entered contains HTML, you may wish to select either enhanced HTML or raw as your format type (consult this help for more information: [http://developer.meego.com/filter/tips http://developer.meego.com/filter/tips]).

== Tips for creating content ==

=== External guides and guides ===

If you would like to connect several guides together as a “book” the developers could progress through, click on “'''Book outline'''” at the bottom of the Create Guide/External Guide page.

In the book field, you can either create a new book or add the guide to an existing book.

<IMG>

To ensure your guide/external guide has a description in the guide lists, click on '''List information''' at the bottom of the Create Guide/External guide page and enter a brief description. You can also upload an image here so it will have an image in the guide list page as well.

<IMG>

=== For all content types (but most likely pages or guides) ===

==== Content in menus ====
If you would like a page or guide to show up in the sub-navigation, click on “'''Menu'''” at the bottom of the Create <content type> page. In the '''PARENT ITEM''' field, select the navigation element you would like the page to appear under, then name it in '''MENU LINK TITLE'''.

<IMG>

==== Meta tags ====
Here you can add the metadata description, which will help people searching determine whether that page is relevant or not. Make metadata descriptions approximately 150 chars (with spaces) or less.

=== Section heads and Section heads w/lists ===
These are the landing pages of the site, and here you will most likely want to add promotional blocks as the content used here. So therefore, it’s prudent to create your promotional blocks first, then start adding the promo block titles in the “'''Content to feature'''” fields on the Create Section head page.

<IMG>

You can also adjust the layout of the promo blocks on a section head page by clicking on “'''Row layout'''” at the bottom of the Create page, then selecting the desired amount of promo blocks in each row.

<IMG>

Top links can be used to add more teasers in the banner area of the landing pages (section heads), but as they are not very attractive, they should be used with caution, perhaps only to show major/critical announcements.

== Edit content ==
You can edit content either from the Content list, or by navigating to the page you would like to edit and selecting '''Edit''' from the menu on the left hand side. If you do not see this menu, click '''X''' to close the content management menu:

<IMG>

It will return to the wrench icon and you should see the option to “'''Edit'''” the page.

== Delete content ==
Go to the page you would like to delete, click on '''Edit''', then '''Delete'''.

== Remove promo blocks from section heads ==
If you wish to delete a promo block from a section head, but still keep the promo block, go to the section head and click '''Edit'''. Then in the “'''Content to feature”''' field, just delete the title of the promo block you want to remove.

== Changing navigation and sub-navigation ==
Go to '''Wrench > Administer > Site Building > Menus > Primary links'''.

<IMG>

Here you can enable, disable, edit and delete what is shown in the navigation. Click '''Save configuration''' when you are done.

Application developer site

2011-03-23T08:05:51Z

Verbosemode:

== 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 [[Application developer site/Status | here]].

A bugzilla version is available [http://bugs.meego.com/show_bug.cgi?id=7882 here].

{{#bugzilla:
|columns=id,priority,severity,status,summary
|product=developer.meego.com
|status=new,assigned,needinfo,reopened
|sort=priority,severity,id
}}

== Tasks ==

All [http://bugs.meego.com/buglist.cgi?quicksearch=developer.meego.com bugzilla tasks/bugs] for developer.meego.com.

=== Critical tasks ===

See bugzilla list above.

== Operating model ==
The operating model for DMC is proposed as follows:
[[File:DMC_roles_OM.png]]

'''DMC coordinator'''

Responsibilities include:
* Act as the primary advocate for the visitor
* Define tools and platforms
**Wiki
**Bugzilla
**Performance and security (backups, etc)
* Develop guidelines for community
* Set targets and action plans
* Build alliances across the ecosystem
* Communicate with the community
* Arrange funding
* Arbitrate requirements handling
* Steer MeeGo brand deployment
* KPI definitions and monitoring
* Create incentives for contributions:
** karma incentives
** financial incentives
** promotional materials
** dev device distribution
** event participation
* Manage the personas and user journeys across the ecosystem surrounding the site (w/content editors)
* Identify main content and capability gaps and needs for these journeys (w/content editors)

'''DMC Production Manager'''

Responsibilities include:
* Oversee minor and major platform releases
* Design aspects including:
** usability
** site IA (with content editors and coordinator)
** design assets
** CMS features
**ensure MeeGo brand deployment
* Steer site improvement requests
**'''Improvement requests process''':
*** 1. need requested
*** 2. need validated
*** 3. development prioritised
*** 4. source found (production manager finds concept developers)
*** 5. developed
*** 6. tested
*** 7. release planned
*** 8. release
* Agree on production workload. Flexible, can be delegated/divided based on:
** core skill
** application module
** and could also involve finding potential Linux foundation resources (which would influence role definitions etc.)

'''Drupal developers'''

Responsibilities include:
* Required participation in these steps of the improvement process:
** 1. need requested
** 4. source found
** 5. developed

'''Content editors'''

Responsibilities include:

* '''Oversee content process''':
** 1. need requested (generally through Bugzilla)
** 2. need validated: content editor validates against content plan
** 3. source found: content editor finds contributors
** 4. content created as draft (usually in wiki, but may be links in Bugzilla)
** 5. Content reviewed (by community/other contributors/content editor)
** 6. content released as approved (migrated to site by content editor or linked to wiki from DMC by content editor)
* Managing content plan:
** managing personas/scenarios
*** developers
*** designers
*** technology thought leaders
*** lead users
** prioritizing content requests
** managing home and hub page editorially
** managing content ecosystem
*** reach activities
*** social media monitoring
*** seo
* Manage content on site and across the ecosystem (for example Wikipedia and Youtube) resulting from the actions identified above
* Ensure quality of content (grammar, style, tone of voice, etc.) and relevance
* Agree on editorial workload
** assume minimum 2 or 3 editors needed
** workload by content type
** workload by core skill
** workload by language and localisation
** workload by persona
** workload by geography/timezone

'''Content contributors'''
Responsibilities include:

* Participation needed in these parts of the content process:
** 1. need requested (respond if skills suit request)
** 3. source found (content bug assigned to contributor)
** 4. content created as draft (usually in wiki, but may be links provided through Bugzilla)
** 5. Content reviewed (by other contributors/community members/content editor)

== Content Description ==

The content description can be found from [[Application developer site/Description | here]].

The site should link to the related content listed [[Application developer site/Related content | here]].

=== Content Draft ===

A wiki version of the information architecture with draft content is available [[Application developer site/Draft content | here]].

=== Future Content ===

The current site could be enhanced with the following content.

# [[Application developer site/Active architecture diagram| Active meego architecture diagram]]

== Content process ==

As defined above in the operating model:

* 1. need requested (generally through Bugzilla)
* 2. need validated: content editor validates against content plan
* 3. source found: content editor finds contributors
* 4. content created as draft (usually in wiki, but may be links in Bugzilla)
* 5. Content reviewed (by community/other contributors/content editor)
* 6. content released as approved (migrated to site by content editor or linked to wiki from DMC by content editor)

== Development Process ==

Improvements/requirements development process as defined in the operating model above:

* 1. need requested (Bugzilla)
* 2. need validated (Production manager/coordinator)
* 3. development prioritized (Production manager/coordinator/community input)
* 4. source found (production manager finds concept developers) (drupal developer, designer, etc)
* 5. developed
* 6. tested
* 7. release planned
* 8. release

More about site development can be found [[Application developer site/Process | here]]

== Release process ==

As defined above in the operating model:

Minor release:
* 1. Development
* 2. RC, security
* 3. Production

Major release:
* 1. Pre-alpha
* 2. Alpha
* 3. Beta
* 4. RC, security
* 5. Production

== Tools used in site processes ==

* Bugzilla is used to manage both content and capability needs, for example wishlists, enhancements [FEA], 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 (with source marked whenever possible)
* Google Analytics may be used to track site use and conversion goals
* Roadmap, actions, issues are used to track development plans
* MeeGo mailing lists, forum, personal email (last resort), and Bugzilla used as communication

== 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, With the site planned to be available in October aligned with the MeeGo 1.1 release.

Critical bugs fixed as of March 15. Awaiting approval from community for passwords to be lifted.

== Site design ==

The draft information architecture can be found here [[Application developer site/Information architecture | here]]. It is open for comments and suggestions.

Some sample wireframe designs will be found [[Application developer site/WireFrames | 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:

'''MOCKUP ONLY'''
[[File:Homepage layout proposal.jpg]]

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:

'''MOCKUP ONLY'''
[[File:dev-meego.com-frontpage_update_2010-12-20.png|800px]]

== Project Team ==

=== MeeGo Project Manager ===

* [http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)] - Nokia's Maemo (Application) Developer Advocate

=== Project Members ===

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

* [http://meego.com/users/ttlukkar Teemu Lukkari/ttlukkar] / Activeark / Project management, Design manager
* [http://meego.com/users/harmaakinkku Graham Honeywill/harmaakinkku] / Activeark / Project Communications, Analytics manager, Concept owner
* [http://meego.com/users/verbosemode Tiffiny Rossi/verbosemode] / Activeark / Content editor
* [http://meego.com/users/mikaelkundert Mikael Kundert/mikaelkundert] / Activeark / Drupal developer

=== Community Members ===

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

* [http://meego.com/users/dneary Dave Neary/dneary] - maemo.org docmaster
* [http://meego.com/users/dawnfoster Dawn Foster/dawnfoster] - Community Manager
* [http://meego.com/users/mshaver Michael Shaver/mshaver] - Moblin.org webmaster & meego.com website developer
* [http://meego.com/users/townxelliot Elliot Smith/townxelliot] - MeeGo wiki maintainer & MeeGo SDK content editor
* bspencer - Bob Spencer

== Contact People ==

== Associated activities ==

The [[DeveloperEngagement | Developer Engagement Framework]].

Application developer site

2011-03-15T20:17:13Z

Verbosemode: Restructured page

== 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 [[Application developer site/Status | here]].

A bugzilla version is available [http://bugs.meego.com/show_bug.cgi?id=7882 here].

{{#bugzilla:
|columns=id,priority,severity,status,summary
|product=developer.meego.com
|status=new,assigned,needinfo,reopened
|sort=priority,severity,id
}}

== Tasks ==

All [http://bugs.meego.com/buglist.cgi?quicksearch=developer.meego.com bugzilla tasks/bugs] for developer.meego.com.

=== Critical tasks ===

See bugzilla list above.

== Operating model ==
The operating model for DMC is proposed as follows:
[[File:DMC_roles_OM.png]]

'''DMC coordinator'''

Responsibilities include:
* Act as the primary advocate for the visitor
* Define tools and platforms
**Wiki
**Bugzilla
**Performance and security (backups, etc)
* Develop guidelines for community
* Set targets and action plans
* Build alliances across the ecosystem
* Communicate with the community
* Arrange funding
* Arbitrate requirements handling
* Steer MeeGo brand deployment
* KPI definitions and monitoring
* Create incentives for contributions:
** karma incentives
** financial incentives
** promotional materials
** dev device distribution
** event participation
* Manage the personas and user journeys across the ecosystem surrounding the site (w/content editors)
* Identify main content and capability gaps and needs for these journeys (w/content editors)

'''DMC Production Manager'''

Responsibilities include:
* Oversee minor and major platform releases
* Design aspects including:
** usability
** site IA (with content editors and coordinator)
** design assets
** CMS features
**ensure MeeGo brand deployment
* Steer site improvement requests
**'''Improvement requests process''':
*** 1. need requested
*** 2. need validated
*** 3. development prioritised
*** 4. source found (production manager finds concept developers)
*** 5. developed
*** 6. tested
*** 7. release planned
*** 8. release
* Agree on production workload. Flexible, can be delegated/divided based on:
** core skill
** application module
** and could also involve finding potential Linux foundation resources (which would influence role definitions etc.)

'''Drupal developers'''

Responsibilities include:
* Required participation in these steps of the improvement process:
** 1. need requested
** 4. source found
** 5. developed

'''Content editors'''

Responsibilities include:

* '''Oversee content process''':
** 1. need requested (generally through Bugzilla)
** 2. need validated: content editor validates against content plan
** 3. source found: content editor finds contributors
** 4. content created as draft (usually in wiki, but may be links in Bugzilla)
** 5. Content reviewed (by community/other contributors/content editor)
** 6. content released as approved (migrated to site by content editor or linked to wiki from DMC by content editor)
* Managing content plan:
** managing personas/scenarios
*** developers
*** designers
*** technology thought leaders
*** lead users
** prioritizing content requests
** managing home and hub page editorially
** managing content ecosystem
*** reach activities
*** social media monitoring
*** seo
* Manage content on site and across the ecosystem (for example Wikipedia and Youtube) resulting from the actions identified above
* Ensure quality of content (grammar, style, tone of voice, etc.) and relevance
* Agree on editorial workload
** assume minimum 2 or 3 editors needed
** workload by content type
** workload by core skill
** workload by language and localisation
** workload by persona
** workload by geography/timezone

'''Content contributors'''
Responsibilities include:

* Participation needed in these parts of the content process:
** 1. need requested (respond if skills suit request)
** 3. source found (content bug assigned to contributor)
** 4. content created as draft (usually in wiki, but may be links provided through Bugzilla)
** 5. Content reviewed (by other contributors/community members/content editor)

'''About the tools used in the content/improvements management processes'''

* Bugzilla is used to manage both content and capability needs, for example wishlists, enhancements [FEA], 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 (with source marked whenever possible)
* Google Analytics may be used to track site use and conversion goals
* Roadmap, actions, issues are used to track development plans
* MeeGo mailing lists, forum, personal email (last resort), and Bugzilla used as communication

== Content Description ==

The content description can be found from [[Application developer site/Description | here]].

The site should link to the related content listed [[Application developer site/Related content | here]].

=== Content Draft ===

A wiki version of the information architecture with draft content is available [[Application developer site/Draft content | here]].

=== Future Content ===

The current site could be enhanced with the following content.

# [[Application developer site/Active architecture diagram| Active meego architecture diagram]]

== Content process ==

As defined above in the operating model:

* 1. need requested (generally through Bugzilla)
* 2. need validated: content editor validates against content plan
* 3. source found: content editor finds contributors
* 4. content created as draft (usually in wiki, but may be links in Bugzilla)
* 5. Content reviewed (by community/other contributors/content editor)
* 6. content released as approved (migrated to site by content editor or linked to wiki from DMC by content editor)

== Development Process ==

Improvements/requirements development process as defined in the operating model above:

* 1. need requested (Bugzilla)
* 2. need validated (Production manager/coordinator)
* 3. development prioritized (Production manager/coordinator/community input)
* 4. source found (production manager finds concept developers) (drupal developer, designer, etc)
* 5. developed
* 6. tested
* 7. release planned
* 8. release

More about site development can be found [[Application developer site/Process | 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, With the site planned to be available in October aligned with the MeeGo 1.1 release.

Critical bugs fixed as of MArch 15. Awaiting approval from community for passwords to be lifted.

== Site design ==

The draft information architecture can be found here [[Application developer site/Information architecture | here]]. It is open for comments and suggestions.

Some sample wireframe designs will be found [[Application developer site/WireFrames | 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:

'''MOCKUP ONLY'''
[[File:Homepage layout proposal.jpg]]

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:

'''MOCKUP ONLY'''
[[File:dev-meego.com-frontpage_update_2010-12-20.png|800px]]

== Project Team ==

=== MeeGo Project Manager ===

* [http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)] - Nokia's Maemo (Application) Developer Advocate

=== Project Members ===

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

* [http://meego.com/users/ttlukkar Teemu Lukkari/ttlukkar] / Activeark / Project management, Design manager
* [http://meego.com/users/harmaakinkku Graham Honeywill/harmaakinkku] / Activeark / Project Communications, Analytics manager, Concept owner
* [http://meego.com/users/verbosemode Tiffiny Rossi/verbosemode] / Activeark / Content editor
* [http://meego.com/users/mikaelkundert Mikael Kundert/mikaelkundert] / Activeark / Drupal developer

=== Community Members ===

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

* [http://meego.com/users/dneary Dave Neary/dneary] - maemo.org docmaster
* [http://meego.com/users/dawnfoster Dawn Foster/dawnfoster] - Community Manager
* [http://meego.com/users/mshaver Michael Shaver/mshaver] - Moblin.org webmaster & meego.com website developer
* [http://meego.com/users/townxelliot Elliot Smith/townxelliot] - MeeGo wiki maintainer & MeeGo SDK content editor
* bspencer - Bob Spencer

== Contact People ==

== Associated activities ==

The [[DeveloperEngagement | Developer Engagement Framework]].

Application developer site

2011-03-15T04:32:25Z

Verbosemode: Restructuring page

== 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 [[Application developer site/Status | here]].

A bugzilla version is available [http://bugs.meego.com/show_bug.cgi?id=7882 here].

{{#bugzilla:
|columns=id,priority,severity,status,summary
|product=developer.meego.com
|status=new,assigned,needinfo,reopened
|sort=priority,severity,id
}}

== Tasks ==

All [http://bugs.meego.com/buglist.cgi?quicksearch=developer.meego.com bugzilla tasks/bugs] for developer.meego.com.

=== Critical tasks ===

See bugzilla list above.

== Operating model ==
The operating model for DMC is proposed as follows:
[[File:DMC_roles_OM.png]]

'''DMC coordinator'''

Responsibilities include:
* Act as the primary advocate for the visitor
* Define tools and platforms
**Wiki
**Bugzilla
**Performance and security (backups, etc)
* Develop guidelines for community
* Set targets and action plans
* Build alliances across the ecosystem
* Communicate with the community
* Arrange funding
* Arbitrate requirements handling
* Steer MeeGo brand deployment
* KPI definitions and monitoring
* Create incentives for contributions:
** karma incentives
** financial incentives
** promotional materials
** dev device distribution
** event participation
* Manage the personas and user journeys across the ecosystem surrounding the site (w/content editors)
* Identify main content and capability gaps and needs for these journeys (w/content editors)

'''DMC Production Manager'''

Responsibilities include:
* Oversee minor and major platform releases
* Design aspects including:
** usability
** site IA (with content editors and coordinator)
** design assets
** CMS features
**ensure MeeGo brand deployment
* Steer site improvement requests
**'''Improvement requests process''':
*** 1. need requested
*** 2. need validated
*** 3. development prioritised
*** 4. source found (production manager finds concept developers)
*** 5. developed
*** 6. tested
*** 7. release planned
*** 8. release
* Agree on production workload. Flexible, can be delegated/divided based on:
** core skill
** application module
** and could also involve finding potential Linux foundation resources (which would influence role definitions etc.)

'''Drupal developers'''

Responsibilities include:
* Required participation in these steps of the improvement process:
** 1. need requested
** 4. source found
** 5. developed

'''Content editors'''

Responsibilities include:

* '''Oversee content process''':
** 1. need requested (generally through Bugzilla)
** 2. need validated: content editor validates against content plan
** 3. source found: content editor finds contributors
** 4. content created as draft (usually in wiki, but may be links in Bugzilla)
** 5. Content reviewed (by community/other contributors/content editor)
** 6. content released as approved (migrated to site by content editor or linked to wiki from DMC by content editor)
* Managing content plan:
** managing personas/scenarios
*** developers
*** designers
*** technology thought leaders
*** lead users
** prioritizing content requests
** managing home and hub page editorially
** managing content ecosystem
*** reach activities
*** social media monitoring
*** seo
* Manage content on site and across the ecosystem (for example Wikipedia and Youtube) resulting from the actions identified above
* Ensure quality of content (grammar, style, tone of voice, etc.) and relevance
* Agree on editorial workload
** assume minimum 2 or 3 editors needed
** workload by content type
** workload by core skill
** workload by language and localisation
** workload by persona
** workload by geography/timezone

'''Content contributors'''
Responsibilities include:

* Participation needed in these parts of the content process:
** 1. need requested (respond if skills suit request)
** 3. source found (content bug assigned to contributor)
** 4. content created as draft (usually in wiki, but may be links provided through Bugzilla)
** 5. Content reviewed (by other contributors/community members/content editor)

'''About the tools used in the content/improvements management processes'''

* Bugzilla is used to manage both content and capability needs, for example wishlists, enhancements [FEA], 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 (with source marked whenever possible)
* Google Analytics may be used to track site use and conversion goals
* Roadmap, actions, issues are used to track development plans
* MeeGo mailing lists, forum, personal email (last resort), and Bugzilla used as communication

== Content Description ==

The content description can be found from [[Application developer site/Description | here]].

The site should link to the related content listed [[Application developer site/Related content | here]].

=== Content processes ===

As defined above in the operating model:

* 1. need requested (generally through Bugzilla)
* 2. need validated: content editor validates against content plan
* 3. source found: content editor finds contributors
* 4. content created as draft (usually in wiki, but may be links in Bugzilla)
* 5. Content reviewed (by community/other contributors/content editor)
* 6. content released as approved (migrated to site by content editor or linked to wiki from DMC by content editor)

=== Content Draft ===

A wiki version of the information architecture with draft content is available [[Application developer site/Draft content | here]].

=== Future Content ===

The current site could be enhanced with the following content.

# [[Application developer site/Active architecture diagram| Active meego architecture diagram]]

== Development Process ==

Improvements/requirements development process as defined in the operating model above:

* 1. need requested (Bugzilla)
* 2. need validated (Production manager/coordinator)
* 3. development prioritized (Production manager/coordinator/community input)
* 4. source found (production manager finds concept developers) (drupal developer, designer, etc)
* 5. developed
* 6. tested
* 7. release planned
* 8. release

More about site development can be found [[Application developer site/Process | 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, With the site planned to be available in October aligned with the MeeGo 1.1 release.

Critical bugs fixed as of MArch 15. Awaiting approval from community for passwords to be lifted.

== Site design ==

The draft information architecture can be found here [[Application developer site/Information architecture | here]]. It is open for comments and suggestions.

Some sample wireframe designs will be found [[Application developer site/WireFrames | 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:

'''MOCKUP ONLY'''
[[File:Homepage layout proposal.jpg]]

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:

'''MOCKUP ONLY'''
[[File:dev-meego.com-frontpage_update_2010-12-20.png|800px]]

== Project Team ==

=== MeeGo Project Manager ===

* [http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)] - Nokia's Maemo (Application) Developer Advocate

=== Project Members ===

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

* [http://meego.com/users/ttlukkar Teemu Lukkari/ttlukkar] / Activeark / Project management, Design manager
* [http://meego.com/users/harmaakinkku Graham Honeywill/harmaakinkku] / Activeark / Project Communications, Analytics manager, Concept owner
* [http://meego.com/users/verbosemode Tiffiny Rossi/verbosemode] / Activeark / Content editor
* [http://meego.com/users/mikaelkundert Mikael Kundert/mikaelkundert] / Activeark / Drupal developer

=== Community Members ===

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

* [http://meego.com/users/dneary Dave Neary/dneary] - maemo.org docmaster
* [http://meego.com/users/dawnfoster Dawn Foster/dawnfoster] - Community Manager
* [http://meego.com/users/mshaver Michael Shaver/mshaver] - Moblin.org webmaster & meego.com website developer
* [http://meego.com/users/townxelliot Elliot Smith/townxelliot] - MeeGo wiki maintainer & MeeGo SDK content editor
* bspencer - Bob Spencer

== Contact People ==

== Associated activities ==

The [[DeveloperEngagement | Developer Engagement Framework]].

Application developer site

2011-03-15T04:22:28Z

Verbosemode: /* Content and improvements processes */

== 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 [[Application developer site/Status | here]].

A bugzilla version is available [http://bugs.meego.com/show_bug.cgi?id=7882 here].

{{#bugzilla:
|columns=id,priority,severity,status,summary
|product=developer.meego.com
|status=new,assigned,needinfo,reopened
|sort=priority,severity,id
}}

== Tasks ==

All [http://bugs.meego.com/buglist.cgi?quicksearch=developer.meego.com bugzilla tasks/bugs] for developer.meego.com.

=== Critical tasks ===

See bugzilla list above.

== Content Description ==

The content description can be found from [[Application developer site/Description | here]].

The site should link to the related content listed [[Application developer site/Related content | here]].

=== Content and improvements processes ===

The operating model for DMC is proposed as follows:
[[File:DMC_roles_OM.png]]

'''DMC coordinator'''

Responsibilities include:
* Act as the primary advocate for the visitor
* Define tools and platforms
**Wiki
**Bugzilla
**Performance and security (backups, etc)
* Develop guidelines for community
* Set targets and action plans
* Build alliances across the ecosystem
* Communicate with the community
* Arrange funding
* Arbitrate requirements handling
* Steer MeeGo brand deployment
* KPI definitions and monitoring
* Create incentives for contributions:
** karma incentives
** financial incentives
** promotional materials
** dev device distribution
** event participation
* Manage the personas and user journeys across the ecosystem surrounding the site (w/content editors)
* Identify main content and capability gaps and needs for these journeys (w/content editors)

'''DMC Production Manager'''

Responsibilities include:
* Oversee minor and major platform releases
* Design aspects including:
** usability
** site IA (with content editors and coordinator)
** design assets
** CMS features
**ensure MeeGo brand deployment
* Steer site improvement requests
**'''Improvement requests process''':
*** 1. need requested
*** 2. need validated
*** 3. development prioritised
*** 4. source found (production manager finds concept developers)
*** 5. developed
*** 6. tested
*** 7. release planned
*** 8. release
* Agree on production workload. Flexible, can be delegated/divided based on:
** core skill
** application module
** and could also involve finding potential Linux foundation resources (which would influence role definitions etc.)

'''Drupal developers'''

Responsibilities include:
* Required participation in these steps of the improvement process:
** 1. need requested
** 4. source found
** 5. developed

'''Content editors'''

Responsibilities include:

* '''Oversee content process''':
** 1. need requested (generally through Bugzilla)
** 2. need validated: content editor validates against content plan
** 3. source found: content editor finds contributors
** 4. content created as draft (usually in wiki, but may be links in Bugzilla)
** 5. Content reviewed (by community/other contributors/content editor)
** 6. content released as approved (migrated to site by content editor or linked to wiki from DMC by content editor)
* Managing content plan:
** managing personas/scenarios
*** developers
*** designers
*** technology thought leaders
*** lead users
** prioritizing content requests
** managing home and hub page editorially
** managing content ecosystem
*** reach activities
*** social media monitoring
*** seo
* Manage content on site and across the ecosystem (for example Wikipedia and Youtube) resulting from the actions identified above
* Ensure quality of content (grammar, style, tone of voice, etc.) and relevance
* Agree on editorial workload
** assume minimum 2 or 3 editors needed
** workload by content type
** workload by core skill
** workload by language and localisation
** workload by persona
** workload by geography/timezone

'''Content contributors'''
Responsibilities include:

* Participation needed in these parts of the content process:
** 1. need requested (respond if skills suit request)
** 3. source found (content bug assigned to contributor)
** 4. content created as draft (usually in wiki, but may be links provided through Bugzilla)
** 5. Content reviewed (by other contributors/community members/content editor)

'''About the tools used in the content/improvements management processes'''

* Bugzilla is used to manage both content and capability needs, for example wishlists, enhancements [FEA], 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 (with source marked whenever possible)
* Google Analytics may be used to track site use and conversion goals
* Roadmap, actions, issues are used to track development plans
* MeeGo mailing lists, forum, personal email (last resort), and Bugzilla used as communication

=== Content Draft ===

A wiki version of the information architecture with draft content is available [[Application developer site/Draft content | here]].

=== Future Content ===

The current site could be enhanced with the following content.

# [[Application developer site/Active architecture diagram| Active meego architecture diagram]]

== Development Process ==

The process used to develop the site can be found [[Application developer site/Process | 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 [[Application developer site/Information architecture | here]]. It is open for comments and suggestions.

Some sample wireframe designs will be found [[Application developer site/WireFrames | 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:

'''MOCKUP ONLY'''
[[File:Homepage layout proposal.jpg]]

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:

'''MOCKUP ONLY'''
[[File:dev-meego.com-frontpage_update_2010-12-20.png|800px]]

== Project Team ==

=== MeeGo Project Manager ===

* [http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)] - Nokia's Maemo (Application) Developer Advocate

=== Project Members ===

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

* [http://meego.com/users/ttlukkar Teemu Lukkari/ttlukkar] / Activeark / Project management, Design manager
* [http://meego.com/users/harmaakinkku Graham Honeywill/harmaakinkku] / Activeark / Project Communications, Analytics manager, Concept owner
* [http://meego.com/users/verbosemode Tiffiny Rossi/verbosemode] / Activeark / Content editor
* [http://meego.com/users/mikaelkundert Mikael Kundert/mikaelkundert] / Activeark / Drupal developer

=== Community Members ===

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

* [http://meego.com/users/dneary Dave Neary/dneary] - maemo.org docmaster
* [http://meego.com/users/dawnfoster Dawn Foster/dawnfoster] - Community Manager
* [http://meego.com/users/mshaver Michael Shaver/mshaver] - Moblin.org webmaster & meego.com website developer
* [http://meego.com/users/townxelliot Elliot Smith/townxelliot] - MeeGo wiki maintainer & MeeGo SDK content editor
* bspencer - Bob Spencer

== Contact People ==

== Associated activities ==

The [[DeveloperEngagement | Developer Engagement Framework]].

Application developer site

2011-03-15T04:21:57Z

Verbosemode: /* Content and improvements processes */

== 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 [[Application developer site/Status | here]].

A bugzilla version is available [http://bugs.meego.com/show_bug.cgi?id=7882 here].

{{#bugzilla:
|columns=id,priority,severity,status,summary
|product=developer.meego.com
|status=new,assigned,needinfo,reopened
|sort=priority,severity,id
}}

== Tasks ==

All [http://bugs.meego.com/buglist.cgi?quicksearch=developer.meego.com bugzilla tasks/bugs] for developer.meego.com.

=== Critical tasks ===

See bugzilla list above.

== Content Description ==

The content description can be found from [[Application developer site/Description | here]].

The site should link to the related content listed [[Application developer site/Related content | here]].

=== Content and improvements processes ===

The operating model for DMC is proposed as follows:
[[File:EDMC_roles_OM.png]]

'''DMC coordinator'''

Responsibilities include:
* Act as the primary advocate for the visitor
* Define tools and platforms
**Wiki
**Bugzilla
**Performance and security (backups, etc)
* Develop guidelines for community
* Set targets and action plans
* Build alliances across the ecosystem
* Communicate with the community
* Arrange funding
* Arbitrate requirements handling
* Steer MeeGo brand deployment
* KPI definitions and monitoring
* Create incentives for contributions:
** karma incentives
** financial incentives
** promotional materials
** dev device distribution
** event participation
* Manage the personas and user journeys across the ecosystem surrounding the site (w/content editors)
* Identify main content and capability gaps and needs for these journeys (w/content editors)

'''DMC Production Manager'''

Responsibilities include:
* Oversee minor and major platform releases
* Design aspects including:
** usability
** site IA (with content editors and coordinator)
** design assets
** CMS features
**ensure MeeGo brand deployment
* Steer site improvement requests
**'''Improvement requests process''':
*** 1. need requested
*** 2. need validated
*** 3. development prioritised
*** 4. source found (production manager finds concept developers)
*** 5. developed
*** 6. tested
*** 7. release planned
*** 8. release
* Agree on production workload. Flexible, can be delegated/divided based on:
** core skill
** application module
** and could also involve finding potential Linux foundation resources (which would influence role definitions etc.)

'''Drupal developers'''

Responsibilities include:
* Required participation in these steps of the improvement process:
** 1. need requested
** 4. source found
** 5. developed

'''Content editors'''

Responsibilities include:

* '''Oversee content process''':
** 1. need requested (generally through Bugzilla)
** 2. need validated: content editor validates against content plan
** 3. source found: content editor finds contributors
** 4. content created as draft (usually in wiki, but may be links in Bugzilla)
** 5. Content reviewed (by community/other contributors/content editor)
** 6. content released as approved (migrated to site by content editor or linked to wiki from DMC by content editor)
* Managing content plan:
** managing personas/scenarios
*** developers
*** designers
*** technology thought leaders
*** lead users
** prioritizing content requests
** managing home and hub page editorially
** managing content ecosystem
*** reach activities
*** social media monitoring
*** seo
* Manage content on site and across the ecosystem (for example Wikipedia and Youtube) resulting from the actions identified above
* Ensure quality of content (grammar, style, tone of voice, etc.) and relevance
* Agree on editorial workload
** assume minimum 2 or 3 editors needed
** workload by content type
** workload by core skill
** workload by language and localisation
** workload by persona
** workload by geography/timezone

'''Content contributors'''
Responsibilities include:

* Participation needed in these parts of the content process:
** 1. need requested (respond if skills suit request)
** 3. source found (content bug assigned to contributor)
** 4. content created as draft (usually in wiki, but may be links provided through Bugzilla)
** 5. Content reviewed (by other contributors/community members/content editor)

'''About the tools used in the content/improvements management processes'''

* Bugzilla is used to manage both content and capability needs, for example wishlists, enhancements [FEA], 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 (with source marked whenever possible)
* Google Analytics may be used to track site use and conversion goals
* Roadmap, actions, issues are used to track development plans
* MeeGo mailing lists, forum, personal email (last resort), and Bugzilla used as communication

=== Content Draft ===

A wiki version of the information architecture with draft content is available [[Application developer site/Draft content | here]].

=== Future Content ===

The current site could be enhanced with the following content.

# [[Application developer site/Active architecture diagram| Active meego architecture diagram]]

== Development Process ==

The process used to develop the site can be found [[Application developer site/Process | 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 [[Application developer site/Information architecture | here]]. It is open for comments and suggestions.

Some sample wireframe designs will be found [[Application developer site/WireFrames | 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:

'''MOCKUP ONLY'''
[[File:Homepage layout proposal.jpg]]

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:

'''MOCKUP ONLY'''
[[File:dev-meego.com-frontpage_update_2010-12-20.png|800px]]

== Project Team ==

=== MeeGo Project Manager ===

* [http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)] - Nokia's Maemo (Application) Developer Advocate

=== Project Members ===

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

* [http://meego.com/users/ttlukkar Teemu Lukkari/ttlukkar] / Activeark / Project management, Design manager
* [http://meego.com/users/harmaakinkku Graham Honeywill/harmaakinkku] / Activeark / Project Communications, Analytics manager, Concept owner
* [http://meego.com/users/verbosemode Tiffiny Rossi/verbosemode] / Activeark / Content editor
* [http://meego.com/users/mikaelkundert Mikael Kundert/mikaelkundert] / Activeark / Drupal developer

=== Community Members ===

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

* [http://meego.com/users/dneary Dave Neary/dneary] - maemo.org docmaster
* [http://meego.com/users/dawnfoster Dawn Foster/dawnfoster] - Community Manager
* [http://meego.com/users/mshaver Michael Shaver/mshaver] - Moblin.org webmaster & meego.com website developer
* [http://meego.com/users/townxelliot Elliot Smith/townxelliot] - MeeGo wiki maintainer & MeeGo SDK content editor
* bspencer - Bob Spencer

== Contact People ==

== Associated activities ==

The [[DeveloperEngagement | Developer Engagement Framework]].

File:DMC roles OM.png

2011-03-15T04:19:37Z

Verbosemode: Mind map showing DMC roles and the proposed operating models (plus content and improvements processes imbedded into role definitions).

Mind map showing DMC roles and the proposed operating models (plus content and improvements processes imbedded into role definitions).

Application developer site

2011-03-15T04:16:35Z

Verbosemode: /* Content and improvements processes */

== 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 [[Application developer site/Status | here]].

A bugzilla version is available [http://bugs.meego.com/show_bug.cgi?id=7882 here].

{{#bugzilla:
|columns=id,priority,severity,status,summary
|product=developer.meego.com
|status=new,assigned,needinfo,reopened
|sort=priority,severity,id
}}

== Tasks ==

All [http://bugs.meego.com/buglist.cgi?quicksearch=developer.meego.com bugzilla tasks/bugs] for developer.meego.com.

=== Critical tasks ===

See bugzilla list above.

== Content Description ==

The content description can be found from [[Application developer site/Description | here]].

The site should link to the related content listed [[Application developer site/Related content | here]].

=== Content and improvements processes ===

The proposed content management process is based upon several community roles.

'''DMC coordinator'''

Responsibilities include:
* Act as the primary advocate for the visitor
* Define tools and platforms
**Wiki
**Bugzilla
**Performance and security (backups, etc)
* Develop guidelines for community
* Set targets and action plans
* Build alliances across the ecosystem
* Communicate with the community
* Arrange funding
* Arbitrate requirements handling
* Steer MeeGo brand deployment
* KPI definitions and monitoring
* Create incentives for contributions:
** karma incentives
** financial incentives
** promotional materials
** dev device distribution
** event participation
* Manage the personas and user journeys across the ecosystem surrounding the site (w/content editors)
* Identify main content and capability gaps and needs for these journeys (w/content editors)

'''DMC Production Manager'''

Responsibilities include:
* Oversee minor and major platform releases
* Design aspects including:
** usability
** site IA (with content editors and coordinator)
** design assets
** CMS features
**ensure MeeGo brand deployment
* Steer site improvement requests
**'''Improvement requests process''':
*** 1. need requested
*** 2. need validated
*** 3. development prioritised
*** 4. source found (production manager finds concept developers)
*** 5. developed
*** 6. tested
*** 7. release planned
*** 8. release
* Agree on production workload. Flexible, can be delegated/divided based on:
** core skill
** application module
** and could also involve finding potential Linux foundation resources (which would influence role definitions etc.)

'''Drupal developers'''

Responsibilities include:
* Required participation in these steps of the improvement process:
** 1. need requested
** 4. source found
** 5. developed

'''Content editors'''

Responsibilities include:

* '''Oversee content process''':
** 1. need requested (generally through Bugzilla)
** 2. need validated: content editor validates against content plan
** 3. source found: content editor finds contributors
** 4. content created as draft (usually in wiki, but may be links in Bugzilla)
** 5. Content reviewed (by community/other contributors/content editor)
** 6. content released as approved (migrated to site by content editor or linked to wiki from DMC by content editor)
* Managing content plan:
** managing personas/scenarios
*** developers
*** designers
*** technology thought leaders
*** lead users
** prioritizing content requests
** managing home and hub page editorially
** managing content ecosystem
*** reach activities
*** social media monitoring
*** seo
* Manage content on site and across the ecosystem (for example Wikipedia and Youtube) resulting from the actions identified above
* Ensure quality of content (grammar, style, tone of voice, etc.) and relevance
* Agree on editorial workload
** assume minimum 2 or 3 editors needed
** workload by content type
** workload by core skill
** workload by language and localisation
** workload by persona
** workload by geography/timezone

'''Content contributors'''
Responsibilities include:

* Participation needed in these parts of the content process:
** 1. need requested (respond if skills suit request)
** 3. source found (content bug assigned to contributor)
** 4. content created as draft (usually in wiki, but may be links provided through Bugzilla)
** 5. Content reviewed (by other contributors/community members/content editor)

'''About the tools used in the content/improvements management processes'''

* Bugzilla is used to manage both content and capability needs, for example wishlists, enhancements [FEA], 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 (with source marked whenever possible)
* Google Analytics may be used to track site use and conversion goals
* Roadmap, actions, issues are used to track development plans
* MeeGo mailing lists, forum, personal email (last resort), and Bugzilla used as communication

=== Content Draft ===

A wiki version of the information architecture with draft content is available [[Application developer site/Draft content | here]].

=== Future Content ===

The current site could be enhanced with the following content.

# [[Application developer site/Active architecture diagram| Active meego architecture diagram]]

== Development Process ==

The process used to develop the site can be found [[Application developer site/Process | 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 [[Application developer site/Information architecture | here]]. It is open for comments and suggestions.

Some sample wireframe designs will be found [[Application developer site/WireFrames | 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:

'''MOCKUP ONLY'''
[[File:Homepage layout proposal.jpg]]

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:

'''MOCKUP ONLY'''
[[File:dev-meego.com-frontpage_update_2010-12-20.png|800px]]

== Project Team ==

=== MeeGo Project Manager ===

* [http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)] - Nokia's Maemo (Application) Developer Advocate

=== Project Members ===

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

* [http://meego.com/users/ttlukkar Teemu Lukkari/ttlukkar] / Activeark / Project management, Design manager
* [http://meego.com/users/harmaakinkku Graham Honeywill/harmaakinkku] / Activeark / Project Communications, Analytics manager, Concept owner
* [http://meego.com/users/verbosemode Tiffiny Rossi/verbosemode] / Activeark / Content editor
* [http://meego.com/users/mikaelkundert Mikael Kundert/mikaelkundert] / Activeark / Drupal developer

=== Community Members ===

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

* [http://meego.com/users/dneary Dave Neary/dneary] - maemo.org docmaster
* [http://meego.com/users/dawnfoster Dawn Foster/dawnfoster] - Community Manager
* [http://meego.com/users/mshaver Michael Shaver/mshaver] - Moblin.org webmaster & meego.com website developer
* [http://meego.com/users/townxelliot Elliot Smith/townxelliot] - MeeGo wiki maintainer & MeeGo SDK content editor
* bspencer - Bob Spencer

== Contact People ==

== Associated activities ==

The [[DeveloperEngagement | Developer Engagement Framework]].

Application developer site

2011-03-15T04:15:43Z

Verbosemode: /* Content Process */

== 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 [[Application developer site/Status | here]].

A bugzilla version is available [http://bugs.meego.com/show_bug.cgi?id=7882 here].

{{#bugzilla:
|columns=id,priority,severity,status,summary
|product=developer.meego.com
|status=new,assigned,needinfo,reopened
|sort=priority,severity,id
}}

== Tasks ==

All [http://bugs.meego.com/buglist.cgi?quicksearch=developer.meego.com bugzilla tasks/bugs] for developer.meego.com.

=== Critical tasks ===

See bugzilla list above.

== Content Description ==

The content description can be found from [[Application developer site/Description | here]].

The site should link to the related content listed [[Application developer site/Related content | here]].

=== Content and improvements processes ===

The proposed content management process is based upon several community roles.

'''DMC coordinator'''

Responsibilities include:
* Act as the primary advocate for the visitor
* Define tools and platforms
**Wiki
**Bugzilla
**Performance and security (backups, etc)
* Develop guidelines for community
* Set targets and action plans
* Build alliances across the ecosystem
* Communicate with the community
* Arrange funding
* Arbitrate requirements handling
* Steer MeeGo brand deployment
* KPI definitions and monitoring
* Create incentives for contributions:
** karma incentives
** financial incentives
** promotional materials
** dev device distribution
** event participation
* Manage the personas and user journeys across the ecosystem surrounding the site (w/content editors)
* Identify main content and capability gaps and needs for these journeys (w/content editors)

'''DMC Production Manager'''

Responsibilities include:
* Oversee minor and major platform releases
* Design aspects including:
** usability
** site IA (with content editors and coordinator)
** design assets
** CMS features
**ensure MeeGo brand deployment
* Steer site improvement requests
**Improvement requests process:
*** 1. need requested
*** 2. need validated
*** 3. development prioritised
*** 4. source found (production manager finds concept developers)
*** 5. developed
*** 6. tested
*** 7. release planned
*** 8. release
* Agree on production workload. Flexible, can be delegated/divided based on:
** core skill
** application module
** and could also involve finding potential Linux foundation resources (which would influence role definitions etc.)

'''Drupal developers'''

Responsibilities include:
* Required participation in these steps of the improvement process:
** 1. need requested
** 4. source found
** 5. developed

'''Content editors'''
Responsibilities include:

* Oversee content process:
** 1. need requested (generally through Bugzilla)
** 2. need validated: content editor validates against content plan
** 3. source found: content editor finds contributors
** 4. content created as draft (usually in wiki, but may be links in Bugzilla)
** 5. Content reviewed (by community/other contributors/content editor)
** 6. content released as approved (migrated to site by content editor or linked to wiki from DMC by content editor)
* Managing content plan:
** managing personas/scenarios
*** developers
*** designers
*** technology thought leaders
*** lead users
** prioritizing content requests
** managing home and hub page editorially
** managing content ecosystem
*** reach activities
*** social media monitoring
*** seo
* Manage content on site and across the ecosystem (for example Wikipedia and Youtube) resulting from the actions identified above
* Ensure quality of content (grammar, style, tone of voice, etc.) and relevance
* Agree on editorial workload
** assume minimum 2 or 3 editors needed
** workload by content type
** workload by core skill
** workload by language and localisation
** workload by persona
** workload by geography/timezone

'''Content contributors'''
Responsibilities include:

* Participation needed in these parts of the content process:
** 1. need requested (respond if skills suit request)
** 3. source found (content bug assigned to contributor)
** 4. content created as draft (usually in wiki, but may be links provided through Bugzilla)
** 5. Content reviewed (by other contributors/community members/content editor)

'''About the tools used in the content/improvements management processes'''

* Bugzilla is used to manage both content and capability needs, for example wishlists, enhancements [FEA], 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 (with source marked whenever possible)
* Google Analytics may be used to track site use and conversion goals
* Roadmap, actions, issues are used to track development plans
* MeeGo mailing lists, forum, personal email (last resort), and Bugzilla used as communication

=== Content Draft ===

A wiki version of the information architecture with draft content is available [[Application developer site/Draft content | here]].

=== Future Content ===

The current site could be enhanced with the following content.

# [[Application developer site/Active architecture diagram| Active meego architecture diagram]]

== Development Process ==

The process used to develop the site can be found [[Application developer site/Process | 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 [[Application developer site/Information architecture | here]]. It is open for comments and suggestions.

Some sample wireframe designs will be found [[Application developer site/WireFrames | 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:

'''MOCKUP ONLY'''
[[File:Homepage layout proposal.jpg]]

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:

'''MOCKUP ONLY'''
[[File:dev-meego.com-frontpage_update_2010-12-20.png|800px]]

== Project Team ==

=== MeeGo Project Manager ===

* [http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)] - Nokia's Maemo (Application) Developer Advocate

=== Project Members ===

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

* [http://meego.com/users/ttlukkar Teemu Lukkari/ttlukkar] / Activeark / Project management, Design manager
* [http://meego.com/users/harmaakinkku Graham Honeywill/harmaakinkku] / Activeark / Project Communications, Analytics manager, Concept owner
* [http://meego.com/users/verbosemode Tiffiny Rossi/verbosemode] / Activeark / Content editor
* [http://meego.com/users/mikaelkundert Mikael Kundert/mikaelkundert] / Activeark / Drupal developer

=== Community Members ===

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

* [http://meego.com/users/dneary Dave Neary/dneary] - maemo.org docmaster
* [http://meego.com/users/dawnfoster Dawn Foster/dawnfoster] - Community Manager
* [http://meego.com/users/mshaver Michael Shaver/mshaver] - Moblin.org webmaster & meego.com website developer
* [http://meego.com/users/townxelliot Elliot Smith/townxelliot] - MeeGo wiki maintainer & MeeGo SDK content editor
* bspencer - Bob Spencer

== Contact People ==

== Associated activities ==

The [[DeveloperEngagement | Developer Engagement Framework]].

Application developer site

2011-03-15T04:14:45Z

Verbosemode: /* Content Process */ Reworked

== 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 [[Application developer site/Status | here]].

A bugzilla version is available [http://bugs.meego.com/show_bug.cgi?id=7882 here].

{{#bugzilla:
|columns=id,priority,severity,status,summary
|product=developer.meego.com
|status=new,assigned,needinfo,reopened
|sort=priority,severity,id
}}

== Tasks ==

All [http://bugs.meego.com/buglist.cgi?quicksearch=developer.meego.com bugzilla tasks/bugs] for developer.meego.com.

=== Critical tasks ===

See bugzilla list above.

== Content Description ==

The content description can be found from [[Application developer site/Description | here]].

The site should link to the related content listed [[Application developer site/Related content | here]].

=== Content Process ===

The proposed content management process is based upon several community roles.

'''DMC coordinator'''

Responsibilities include:
* Act as the primary advocate for the visitor
* Define tools and platforms
**Wiki
**Bugzilla
**Performance and security (backups, etc)
* Develop guidelines for community
* Set targets and action plans
* Build alliances across the ecosystem
* Communicate with the community
* Arrange funding
* Arbitrate requirements handling
* Steer MeeGo brand deployment
* KPI definitions and monitoring
* Create incentives for contributions:
** karma incentives
** financial incentives
** promotional materials
** dev device distribution
** event participation
* Manage the personas and user journeys across the ecosystem surrounding the site (w/content editors)
* Identify main content and capability gaps and needs for these journeys (w/content editors)

'''DMC Production Manager'''

Responsibilities include:
* Oversee minor and major platform releases
* Design aspects including:
** usability
** site IA (with content editors and coordinator)
** design assets
** CMS features
**ensure MeeGo brand deployment
* Steer site improvement requests
**Improvement requests process:
*** 1. need requested
*** 2. need validated
*** 3. development prioritised
*** 4. source found (production manager finds concept developers)
*** 5. developed
*** 6. tested
*** 7. release planned
*** 8. release
* Agree on production workload. Flexible, can be delegated/divided based on:
** core skill
** application module
** and could also involve finding potential Linux foundation resources (which would influence role definitions etc.)

'''Drupal developers'''

Responsibilities include:
* Required participation in these steps of the improvement process:
** 1. need requested
** 4. source found
** 5. developed

'''Content editors'''
Responsibilities include:

* Oversee content process:
** 1. need requested (generally through Bugzilla)
** 2. need validated: content editor validates against content plan
** 3. source found: content editor finds contributors
** 4. content created as draft (usually in wiki, but may be links in Bugzilla)
** 5. Content reviewed (by community/other contributors/content editor)
** 6. content released as approved (migrated to site by content editor or linked to wiki from DMC by content editor)
* Managing content plan:
** managing personas/scenarios
*** developers
*** designers
*** technology thought leaders
*** lead users
** prioritizing content requests
** managing home and hub page editorially
** managing content ecosystem
*** reach activities
*** social media monitoring
*** seo
* Manage content on site and across the ecosystem (for example Wikipedia and Youtube) resulting from the actions identified above
* Ensure quality of content (grammar, style, tone of voice, etc.) and relevance
* Agree on editorial workload
** assume minimum 2 or 3 editors needed
** workload by content type
** workload by core skill
** workload by language and localisation
** workload by persona
** workload by geography/timezone

'''Content contributors'''
Responsibilities include:

* Participation needed in these parts of the content process:
** 1. need requested (respond if skills suit request)
** 3. source found (content bug assigned to contributor)
** 4. content created as draft (usually in wiki, but may be links provided through Bugzilla)
** 5. Content reviewed (by other contributors/community members/content editor)

'''About the tools used in the content/improvements management processes'''

* Bugzilla is used to manage both content and capability needs, for example wishlists, enhancements [FEA], 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 (with source marked whenever possible)
* Google Analytics may be used to track site use and conversion goals
* Roadmap, actions, issues are used to track development plans
* MeeGo mailing lists, forum, personal email (last resort), and Bugzilla used as communication

=== Content Draft ===

A wiki version of the information architecture with draft content is available [[Application developer site/Draft content | here]].

=== Future Content ===

The current site could be enhanced with the following content.

# [[Application developer site/Active architecture diagram| Active meego architecture diagram]]

== Development Process ==

The process used to develop the site can be found [[Application developer site/Process | 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 [[Application developer site/Information architecture | here]]. It is open for comments and suggestions.

Some sample wireframe designs will be found [[Application developer site/WireFrames | 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:

'''MOCKUP ONLY'''
[[File:Homepage layout proposal.jpg]]

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:

'''MOCKUP ONLY'''
[[File:dev-meego.com-frontpage_update_2010-12-20.png|800px]]

== Project Team ==

=== MeeGo Project Manager ===

* [http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)] - Nokia's Maemo (Application) Developer Advocate

=== Project Members ===

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

* [http://meego.com/users/ttlukkar Teemu Lukkari/ttlukkar] / Activeark / Project management, Design manager
* [http://meego.com/users/harmaakinkku Graham Honeywill/harmaakinkku] / Activeark / Project Communications, Analytics manager, Concept owner
* [http://meego.com/users/verbosemode Tiffiny Rossi/verbosemode] / Activeark / Content editor
* [http://meego.com/users/mikaelkundert Mikael Kundert/mikaelkundert] / Activeark / Drupal developer

=== Community Members ===

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

* [http://meego.com/users/dneary Dave Neary/dneary] - maemo.org docmaster
* [http://meego.com/users/dawnfoster Dawn Foster/dawnfoster] - Community Manager
* [http://meego.com/users/mshaver Michael Shaver/mshaver] - Moblin.org webmaster & meego.com website developer
* [http://meego.com/users/townxelliot Elliot Smith/townxelliot] - MeeGo wiki maintainer & MeeGo SDK content editor
* bspencer - Bob Spencer

== Contact People ==

== Associated activities ==

The [[DeveloperEngagement | Developer Engagement Framework]].

Documentation Backlog for MeeGo 1.2

2011-02-22T07:33:32Z

Verbosemode: /* Getting started with MeeGo application development */

[[Category:meego-1.2]]

= Contents of this page =

This site is used for mapping documentation content areas for the MeeGo 1.2 SDK developer documentation release. Eventually, the page will contain links to all relevant MeeGo 1.2 developer documentation content in wiki and to the developer documentation related features in Bugzilla.

'''Please be patient while the content on this page is being updated.'''

Note that this page will not link to any other documentation, such as
* instructions about writing documentation
* platform development instructions
* process descriptions describing how MeeGo OS work is carried out

If you are currently working on draft material for MeeGo 1.2, add links to all the pages you are updating here. Mark the status as: Not started, ongoing, to be reviewed, ready.

= Developer documentation =

'''Area owners:''' Taru Laine

'''Changes since MeeGo 1.1 SDK''':
Updates according to SDK implementation.

'''Status''': Ongoing.

'''Link to MeeGo Wiki:'''
[[SDK/Docs/1.2 | Table of Contents for MeeGo 1.2 SDK developer documentation]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9479 Feature 9479 ]

==Getting started ==
===Release notes for MeeGo 1.2 SDK===
'''Area owners:''' Veli Kaksonen, Bob Spencer

'''Suggested location''': developer.meego.com (DMC), References

'''Changes since MeeGo 1.1 SDK''': New content area.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* will probably be published in meego.com, in [http://meego.com/downloads/releases MeeGo release notes]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=12461 Feature 12461]

===Download site for MeeGo 1.2 SDK===
'''Area owners:''' Veli Kaksonen, Bob Spencer

'''Suggested location''': developer.meego.com (DMC), SDK

'''Changes since MeeGo 1.1 SDK''': New content area.

'''Status''': Not started

'''Link to MeeGo Wiki:'''
* probably provided through meego.com

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=12788 Feature 12788 ]

===Getting started with MeeGo application development===
'''Area owners:''' Ronan MacLaverty

'''Suggested location''': developer.meego.com (DMC), Guides/Getting started

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started

'''Links to MeeGo Wiki:'''
* [[SDK/Docs/1.2/MeeGo_overview| MeeGo application development overview]]
* [[SDK/Docs/1.2/MeeGo_developer_story| MeeGo developer story]]

//Having both of these seems redundant, so perhaps they can be merged, like here at developer.meego.com: http://developer.meego.com/guides/getting-started/meego-application-development-process //

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9480 Feature 9480 ]

===Installation instructions (OBS)===
'''Area owners:''' Elliot Smith

'''Suggested location''': developer.meego.com (DMC), Guides

'''Changes since MeeGo 1.1 SDK''': New content area.

'''Status''': Not started

'''Link to MeeGo Wiki:'''
//to be added//

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9481 Feature 9481]

===Installation instructions (application SDK)===
'''Area owners:''' Taru Laine for Linux, Max Yu for Windows

'''Suggested location''': developer.meego.com (DMC), Guides or SDK tools

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started

'''Link to MeeGo Wiki:'''
* [[SDK/Docs/1.2/Supported_operating_systems |Supported guest operating systems]]
* [[SDK/Docs/1.2/Installing_and_configuring_MeeGo_SDK_for_Linux|Installing and configuring MeeGo SDK for Linux]]
* [[SDK/Docs/1.2/Checking_virtualization_support|Checking your system's graphics capabilities]]
* [[SDK/Docs/1.2/Getting_started_with_the_MeeGo_SDK_for_Windows|Installing and configuring MeeGo SDK for Windows]]
* [[SDK/Docs/1.2/Configuring_QEMU |Setting up the emulator]]
* //Are these still needed?//
** [[SDK/Docs/1.2/MeeGo_SDK_with_Xephyr|Developing with Xephyr]]
** [[SDK/Docs/1.2/Building_a_MeeGo_chroot_on_Linux|Creating a MeeGo chroot]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9482 Feature 9482]

===Device provisioning instructions===
'''Area owners:''' Taru Laine for Handset, Elliot Smith for Netbook

'''Suggested location''': developer.meego.com (DMC), Guides

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started

'''Link to MeeGo Wiki:'''
* [[SDK/Docs/1.2/Setting_up_handset|Setting up your handset ]]
* [[SDK/Docs/1.2/Setting_up_netbook|Setting up your netbook]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9483 Feature 9483]

==Developing with MeeGo SDK ==

===Best practices documentation for MeeGo 1.2 SDK===
'''Area owners:''' Taru Laine

'''Suggested location''': developer.meego.com (DMC), Guides/Guidelines

'''Changes since MeeGo 1.1 SDK''': New content area.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=12464 Feature 12464 ]

===Other documentations===
'''Note''': This feature will be divided in Bugzilla into the following new features:
* Debugging instructions for MeeGo 1.2 SDK
** Area owner: Taru Laine?
* Creating a Hello world application
** Area owner: Taru Laine (note that Netbook-related content is also needed, e.g. from Elliot)
* Instructions for building MeeGo image/QEMU image
** Area owner: Fathi Boudra? (Is this needed in MeeGo 1.2 SDK developer documentation set?)

'''Area owners:''' Taru Laine (and Elliot Smith?)

'''Suggested location''':
* Debugging: developer.meego.com (DMC), Guides
* Creating a Hello World application: developer.meego.com (DMC), Guides
* Instructions for building MeeGo image/QEMU image: wiki.meego.com

'''Changes since MeeGo 1.1 SDK''':
Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* [[SDK/Docs/1.2/Developing_for_MeeGo |Developing for MeeGo]]
* [[SDK/Docs/1.2/Creating Hello World |Creating and running your first application]]
* [[SDK/Docs/1.2/Debugging with Qt Creator |Debugging with Qt Creator]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9493 Feature 9493]

===Packaging instructions (OBS)===
'''Area owners:''' Elliot Smith

'''Suggested location''': developer.meego.com (DMC), Guides

'''Changes since MeeGo 1.1 SDK''': New content area.

'''Status''': Not started

'''Link to MeeGo Wiki:'''
//to be added//

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9484 Feature 9484]

===Packaging instructions (Application SDK)===
'''Area owners:''' Taru Laine

'''Suggested location''': developer.meego.com (DMC), Guides

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started

'''Link to MeeGo Wiki:'''
* Can this be included in:
** [[SDK/Docs/1.2/Creating Hello World |Creating and running your first application]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9485 Feature 9485]

===Troubleshooting information for MeeGo 1.2 SDK===
'''Area owners:''' Taru Laine and Elliot Smith

'''Suggested location''': developer.meego.com (DMC), Guides/FAQ or wiki.meego.com

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* [[SDK/Docs/1.2/Troubleshooting|Troubleshooting]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=12462 Feature 12462]

=== Publishing instructions ===

'''Area owners:''' Taru Laine

'''Suggested location''': developer.meego.com (DMC), Guides

'''Changes since MeeGo 1.1 SDK''':
New content area.

'''Status''': Initial content with summary and links to currently open or planned vendor developer areas (where more instructions can be found). Also link to open-source repository apps.meego.com (work in progress).

'''Link to MeeGo Wiki:'''
http://wiki.meego.com/SDK/Docs/1.2/Publishing

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9486 Feature 9486]

==UI guidelines==

=== Handset UX guidelines ===

'''Area owners:''' Ronan MacLaverty

'''Suggested location''': developer.meego.com (DMC), Guidelines

'''Changes since MeeGo 1.1 SDK''':
Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* will probably be published in meego.com, in the following sections:
** [http://meego.com/developers/meego-ux-design-principles UI design principles]
** [http://meego.com/developers/ui-design-guidelines UI design guidelines]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9487 Feature 9487]

=== Netbook UX guidelines ===

'''Area owners:''' Elliot Smith

'''Suggested location''': developer.meego.com (DMC), Guides

'''Changes since MeeGo 1.1 SDK''':
New content area.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
//to be added//

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9488 Feature 9488]

==Reference material==
=== Architectural overview===
'''Area owners:''' Taru Laine

'''Suggested location''': meego.com, Architecture (?)

'''Changes since MeeGo 1.1 SDK''':
Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* to be published in meego.com, see the following figures: [http://meego.com/developers/meego-architecture MeeGo architecture overview], [http://meego.com/developers/meego-architecture/meego-architecture-layer-view MeeGo architecture layer view],
[http://meego.com/developers/meego-architecture/meego-architecture-domain-view MeeGo architecture domain view], and
[http://meego.com/developers/meego-architecture/meego-architecture-api-view MeeGo architecture API view]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9489 Feature 9489]

===API reference (MeeGo API)===
'''Area owners:''' Murali-Krishna Punaganti

'''Suggested location''': developer.meego.com (DMC), References

'''Changes since MeeGo 1.1 SDK''':
Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* will probably be published in meego.com

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9490 Feature 9490]

===API reference (Platform API)===
'''Area owners:''' Murali-Krishna Punaganti

'''Suggested location''': wiki.meego.com

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* will probably be published in meego.com

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9491 Feature 9491]

=== Links to relevant Qt documentation===
'''Area owners:''' Taru Laine

'''Suggested location''': various (depending on the page)

'''Changes since MeeGo 1.1 SDK''':
New content area.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* This feature covers various pages in the SDK developer documentation.

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=12463 Feature 12463]

===Glossary for MeeGo 1.2 SDK===
'''Area owners:''' Taru Laine

'''Suggested location''': developer.meego.com (DMC), Glossary

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* [[SDK/Docs/1.2/Terminology | Glossary]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=12241 Feature 12241]

==Sample Applications==
'''Area owners:''' Ville Lavonius.

'''Suggested location''': developer.meego.com (DMC), Guides/Samples

'''Changes since MeeGo 1.1 SDK''': New content area.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* [[SDK/Docs/1.2/Example_applications | Example applications]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9492 Feature 9492]

Documentation Backlog for MeeGo 1.2

2011-02-22T07:33:14Z

Verbosemode: /* Getting started with MeeGo application development */

[[Category:meego-1.2]]

= Contents of this page =

This site is used for mapping documentation content areas for the MeeGo 1.2 SDK developer documentation release. Eventually, the page will contain links to all relevant MeeGo 1.2 developer documentation content in wiki and to the developer documentation related features in Bugzilla.

'''Please be patient while the content on this page is being updated.'''

Note that this page will not link to any other documentation, such as
* instructions about writing documentation
* platform development instructions
* process descriptions describing how MeeGo OS work is carried out

If you are currently working on draft material for MeeGo 1.2, add links to all the pages you are updating here. Mark the status as: Not started, ongoing, to be reviewed, ready.

= Developer documentation =

'''Area owners:''' Taru Laine

'''Changes since MeeGo 1.1 SDK''':
Updates according to SDK implementation.

'''Status''': Ongoing.

'''Link to MeeGo Wiki:'''
[[SDK/Docs/1.2 | Table of Contents for MeeGo 1.2 SDK developer documentation]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9479 Feature 9479 ]

==Getting started ==
===Release notes for MeeGo 1.2 SDK===
'''Area owners:''' Veli Kaksonen, Bob Spencer

'''Suggested location''': developer.meego.com (DMC), References

'''Changes since MeeGo 1.1 SDK''': New content area.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* will probably be published in meego.com, in [http://meego.com/downloads/releases MeeGo release notes]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=12461 Feature 12461]

===Download site for MeeGo 1.2 SDK===
'''Area owners:''' Veli Kaksonen, Bob Spencer

'''Suggested location''': developer.meego.com (DMC), SDK

'''Changes since MeeGo 1.1 SDK''': New content area.

'''Status''': Not started

'''Link to MeeGo Wiki:'''
* probably provided through meego.com

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=12788 Feature 12788 ]

===Getting started with MeeGo application development===
'''Area owners:''' Ronan MacLaverty

'''Suggested location''': developer.meego.com (DMC), Guides/Getting started

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started

'''Links to MeeGo Wiki:'''
* [[SDK/Docs/1.2/MeeGo_overview| MeeGo application development overview]]
* [[SDK/Docs/1.2/MeeGo_developer_story| MeeGo developer story]]

//Having both of these seems redundant, so perhaps they can be merged, like here at developer.meego.com: http://developer.meego.com/guides/getting-started/meego-application-development-process

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9480 Feature 9480 ]

===Installation instructions (OBS)===
'''Area owners:''' Elliot Smith

'''Suggested location''': developer.meego.com (DMC), Guides

'''Changes since MeeGo 1.1 SDK''': New content area.

'''Status''': Not started

'''Link to MeeGo Wiki:'''
//to be added//

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9481 Feature 9481]

===Installation instructions (application SDK)===
'''Area owners:''' Taru Laine for Linux, Max Yu for Windows

'''Suggested location''': developer.meego.com (DMC), Guides or SDK tools

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started

'''Link to MeeGo Wiki:'''
* [[SDK/Docs/1.2/Supported_operating_systems |Supported guest operating systems]]
* [[SDK/Docs/1.2/Installing_and_configuring_MeeGo_SDK_for_Linux|Installing and configuring MeeGo SDK for Linux]]
* [[SDK/Docs/1.2/Checking_virtualization_support|Checking your system's graphics capabilities]]
* [[SDK/Docs/1.2/Getting_started_with_the_MeeGo_SDK_for_Windows|Installing and configuring MeeGo SDK for Windows]]
* [[SDK/Docs/1.2/Configuring_QEMU |Setting up the emulator]]
* //Are these still needed?//
** [[SDK/Docs/1.2/MeeGo_SDK_with_Xephyr|Developing with Xephyr]]
** [[SDK/Docs/1.2/Building_a_MeeGo_chroot_on_Linux|Creating a MeeGo chroot]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9482 Feature 9482]

===Device provisioning instructions===
'''Area owners:''' Taru Laine for Handset, Elliot Smith for Netbook

'''Suggested location''': developer.meego.com (DMC), Guides

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started

'''Link to MeeGo Wiki:'''
* [[SDK/Docs/1.2/Setting_up_handset|Setting up your handset ]]
* [[SDK/Docs/1.2/Setting_up_netbook|Setting up your netbook]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9483 Feature 9483]

==Developing with MeeGo SDK ==

===Best practices documentation for MeeGo 1.2 SDK===
'''Area owners:''' Taru Laine

'''Suggested location''': developer.meego.com (DMC), Guides/Guidelines

'''Changes since MeeGo 1.1 SDK''': New content area.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=12464 Feature 12464 ]

===Other documentations===
'''Note''': This feature will be divided in Bugzilla into the following new features:
* Debugging instructions for MeeGo 1.2 SDK
** Area owner: Taru Laine?
* Creating a Hello world application
** Area owner: Taru Laine (note that Netbook-related content is also needed, e.g. from Elliot)
* Instructions for building MeeGo image/QEMU image
** Area owner: Fathi Boudra? (Is this needed in MeeGo 1.2 SDK developer documentation set?)

'''Area owners:''' Taru Laine (and Elliot Smith?)

'''Suggested location''':
* Debugging: developer.meego.com (DMC), Guides
* Creating a Hello World application: developer.meego.com (DMC), Guides
* Instructions for building MeeGo image/QEMU image: wiki.meego.com

'''Changes since MeeGo 1.1 SDK''':
Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* [[SDK/Docs/1.2/Developing_for_MeeGo |Developing for MeeGo]]
* [[SDK/Docs/1.2/Creating Hello World |Creating and running your first application]]
* [[SDK/Docs/1.2/Debugging with Qt Creator |Debugging with Qt Creator]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9493 Feature 9493]

===Packaging instructions (OBS)===
'''Area owners:''' Elliot Smith

'''Suggested location''': developer.meego.com (DMC), Guides

'''Changes since MeeGo 1.1 SDK''': New content area.

'''Status''': Not started

'''Link to MeeGo Wiki:'''
//to be added//

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9484 Feature 9484]

===Packaging instructions (Application SDK)===
'''Area owners:''' Taru Laine

'''Suggested location''': developer.meego.com (DMC), Guides

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started

'''Link to MeeGo Wiki:'''
* Can this be included in:
** [[SDK/Docs/1.2/Creating Hello World |Creating and running your first application]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9485 Feature 9485]

===Troubleshooting information for MeeGo 1.2 SDK===
'''Area owners:''' Taru Laine and Elliot Smith

'''Suggested location''': developer.meego.com (DMC), Guides/FAQ or wiki.meego.com

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* [[SDK/Docs/1.2/Troubleshooting|Troubleshooting]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=12462 Feature 12462]

=== Publishing instructions ===

'''Area owners:''' Taru Laine

'''Suggested location''': developer.meego.com (DMC), Guides

'''Changes since MeeGo 1.1 SDK''':
New content area.

'''Status''': Initial content with summary and links to currently open or planned vendor developer areas (where more instructions can be found). Also link to open-source repository apps.meego.com (work in progress).

'''Link to MeeGo Wiki:'''
http://wiki.meego.com/SDK/Docs/1.2/Publishing

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9486 Feature 9486]

==UI guidelines==

=== Handset UX guidelines ===

'''Area owners:''' Ronan MacLaverty

'''Suggested location''': developer.meego.com (DMC), Guidelines

'''Changes since MeeGo 1.1 SDK''':
Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* will probably be published in meego.com, in the following sections:
** [http://meego.com/developers/meego-ux-design-principles UI design principles]
** [http://meego.com/developers/ui-design-guidelines UI design guidelines]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9487 Feature 9487]

=== Netbook UX guidelines ===

'''Area owners:''' Elliot Smith

'''Suggested location''': developer.meego.com (DMC), Guides

'''Changes since MeeGo 1.1 SDK''':
New content area.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
//to be added//

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9488 Feature 9488]

==Reference material==
=== Architectural overview===
'''Area owners:''' Taru Laine

'''Suggested location''': meego.com, Architecture (?)

'''Changes since MeeGo 1.1 SDK''':
Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* to be published in meego.com, see the following figures: [http://meego.com/developers/meego-architecture MeeGo architecture overview], [http://meego.com/developers/meego-architecture/meego-architecture-layer-view MeeGo architecture layer view],
[http://meego.com/developers/meego-architecture/meego-architecture-domain-view MeeGo architecture domain view], and
[http://meego.com/developers/meego-architecture/meego-architecture-api-view MeeGo architecture API view]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9489 Feature 9489]

===API reference (MeeGo API)===
'''Area owners:''' Murali-Krishna Punaganti

'''Suggested location''': developer.meego.com (DMC), References

'''Changes since MeeGo 1.1 SDK''':
Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* will probably be published in meego.com

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9490 Feature 9490]

===API reference (Platform API)===
'''Area owners:''' Murali-Krishna Punaganti

'''Suggested location''': wiki.meego.com

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* will probably be published in meego.com

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9491 Feature 9491]

=== Links to relevant Qt documentation===
'''Area owners:''' Taru Laine

'''Suggested location''': various (depending on the page)

'''Changes since MeeGo 1.1 SDK''':
New content area.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* This feature covers various pages in the SDK developer documentation.

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=12463 Feature 12463]

===Glossary for MeeGo 1.2 SDK===
'''Area owners:''' Taru Laine

'''Suggested location''': developer.meego.com (DMC), Glossary

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* [[SDK/Docs/1.2/Terminology | Glossary]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=12241 Feature 12241]

==Sample Applications==
'''Area owners:''' Ville Lavonius.

'''Suggested location''': developer.meego.com (DMC), Guides/Samples

'''Changes since MeeGo 1.1 SDK''': New content area.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* [[SDK/Docs/1.2/Example_applications | Example applications]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9492 Feature 9492]

SDK/Docs/1.2/Publishing

2011-02-22T07:18:56Z

Verbosemode:

Get your apps published! This list is under development as more vendors and marketplaces are expected to support distribution of apps for MeeGo devices.

== App stores ==

The MeeGo platform offers wide-reaching market opportunities to app developers because multiple app stores are distributing MeeGo apps. The store support is growing as MeeGo continues to evolve and more MeeGo devices appear on the market.

Current and stores that support MeeGo include:

[http://appdeveloper.intel.com Intel AppUp]

Intel AppUp allows you to distribute and sell your applications to millions of netbook users. AppUp features a broad distribution model with multiple storefronts.

[http://www.forum.nokia.com/Distribute Ovi Store by Nokia]

Ovi Store has a global reach, attracting users from over 190 countries and in 30 languages. Operator and credit card billing offer easy ways for people to buy apps from Ovi Store.

[http://wetab.mobi/en/developers/ WeTab Market]

The WeTab marketplace will open in early 2011.

== Free marketplaces and repositories ==

You can also publish your application through open source marketplaces and repositories.

[http://apps.meego.com MeeGo Apps]

Coming soon! MeeGo Apps is the repository where software created by the MeeGo community can be found. Developers can build their applications on the [http://wiki.meego.com/Build_Infrastructure#Community_Build_System MeeGo Community OBS], a sophisticated build system, and publish them in the Apps repository. Get more info about MeeGo Apps from the [http://wiki.meego.com/MeeGo_Apps MeeGo wiki].

SDK/Docs/1.2/Publishing

2011-02-22T07:18:24Z

Verbosemode: /* Free marketplaces and repositories */

Get your apps published! This list is under development as more vendors and marketplaces are expected to support distribution of apps for MeeGo devices.

== App stores ==

The MeeGo platform offers wide-reaching market opportunities to app developers because multiple app stores are distributing MeeGo apps. The store support is growing as MeeGo continues to evolve and more MeeGo devices appear on the market.

Current and stores that support MeeGo include:

[http://appdeveloper.intel.com Intel AppUp]

Intel AppUp allows you to distribute and sell your applications to millions of netbook users. AppUp features a broad distribution model with multiple storefronts.

[http://www.forum.nokia.com/Distribute Ovi Store by Nokia]

Ovi Store has a global reach, attracting users from over 190 countries and in 30 languages. Operator and credit card billing offer easy ways for people to buy apps from Ovi Store.

[http://wetab.mobi/en/developers/ WeTab Market]

The WeTab marketplace will open in early 2011.

== Free marketplaces and repositories ==

You can also publish your application through open source marketplaces and repositories.

[http://apps.meego.com MeeGo Apps]
Coming soon! MeeGo Apps is the repository where software created by the MeeGo community can be found. Developers can build their applications on the [http://wiki.meego.com/Build_Infrastructure#Community_Build_System MeeGo Community OBS], a sophisticated build system, and publish them in the Apps repository. Get more info about MeeGo Apps from the [http://wiki.meego.com/MeeGo_Apps MeeGo wiki].

SDK/Docs/1.2/Publishing

2011-02-22T07:17:53Z

Verbosemode: /* Free marketplaces and repositories */

Get your apps published! This list is under development as more vendors and marketplaces are expected to support distribution of apps for MeeGo devices.

== App stores ==

The MeeGo platform offers wide-reaching market opportunities to app developers because multiple app stores are distributing MeeGo apps. The store support is growing as MeeGo continues to evolve and more MeeGo devices appear on the market.

Current and stores that support MeeGo include:

[http://appdeveloper.intel.com Intel AppUp]

Intel AppUp allows you to distribute and sell your applications to millions of netbook users. AppUp features a broad distribution model with multiple storefronts.

[http://www.forum.nokia.com/Distribute Ovi Store by Nokia]

Ovi Store has a global reach, attracting users from over 190 countries and in 30 languages. Operator and credit card billing offer easy ways for people to buy apps from Ovi Store.

[http://wetab.mobi/en/developers/ WeTab Market]

The WeTab marketplace will open in early 2011.

== Free marketplaces and repositories ==

You can also publish your application through open source marketplaces and repositories.

[http://apps.meego.com link MeeGo Apps]
Coming soon! MeeGo Apps is the repository where software created by the MeeGo community can be found. Developers can build their applications on the [http://wiki.meego.com/Build_Infrastructure#Community_Build_System MeeGo Community OBS], a sophisticated build system, and publish them in the Apps repository. Get more info about MeeGo Apps from the [http://wiki.meego.com/MeeGo_Apps MeeGo wiki].

Documentation Backlog for MeeGo 1.2

2011-02-22T06:27:21Z

Verbosemode: /* Publishing instructions */Some initial content and links

[[Category:meego-1.2]]

= Contents of this page =

This site is used for mapping documentation content areas for the MeeGo 1.2 SDK developer documentation release. Eventually, the page will contain links to all relevant MeeGo 1.2 developer documentation content in wiki and to the developer documentation related features in Bugzilla.

'''Please be patient while the content on this page is being updated.'''

Note that this page will not link to any other documentation, such as
* instructions about writing documentation
* platform development instructions
* process descriptions describing how MeeGo OS work is carried out

If you are currently working on draft material for MeeGo 1.2, add links to all the pages you are updating here. Mark the status as: Not started, ongoing, to be reviewed, ready.

= Developer documentation =

'''Area owners:''' Taru Laine

'''Changes since MeeGo 1.1 SDK''':
Updates according to SDK implementation.

'''Status''': Ongoing.

'''Link to MeeGo Wiki:'''
[[SDK/Docs/1.2 | Table of Contents for MeeGo 1.2 SDK developer documentation]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9479 Feature 9479 ]

==Getting started ==
===Release notes for MeeGo 1.2 SDK===
'''Area owners:''' Veli Kaksonen, Bob Spencer

'''Suggested location''': developer.meego.com (DMC), References

'''Changes since MeeGo 1.1 SDK''': New content area.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* will probably be published in meego.com, in [http://meego.com/downloads/releases MeeGo release notes]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=12461 Feature 12461]

===Download site for MeeGo 1.2 SDK===
'''Area owners:''' Veli Kaksonen, Bob Spencer

'''Suggested location''': developer.meego.com (DMC), SDK

'''Changes since MeeGo 1.1 SDK''': New content area.

'''Status''': Not started

'''Link to MeeGo Wiki:'''
* probably provided through meego.com

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=12788 Feature 12788 ]

===Getting started with MeeGo application development===
'''Area owners:''' Ronan MacLaverty

'''Suggested location''': developer.meego.com (DMC), Guides/Getting started

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started

'''Links to MeeGo Wiki:'''
* [[SDK/Docs/1.2/MeeGo_overview| MeeGo application development overview]]
* [[SDK/Docs/1.2/MeeGo_developer_story| MeeGo developer story]]

//are these both needed for MeeGo 1.2?//

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9480 Feature 9480 ]

===Installation instructions (OBS)===
'''Area owners:''' Elliot Smith

'''Suggested location''': developer.meego.com (DMC), Guides

'''Changes since MeeGo 1.1 SDK''': New content area.

'''Status''': Not started

'''Link to MeeGo Wiki:'''
//to be added//

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9481 Feature 9481]

===Installation instructions (application SDK)===
'''Area owners:''' Taru Laine for Linux, Max Yu for Windows

'''Suggested location''': developer.meego.com (DMC), Guides or SDK tools

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started

'''Link to MeeGo Wiki:'''
* [[SDK/Docs/1.2/Supported_operating_systems |Supported guest operating systems]]
* [[SDK/Docs/1.2/Installing_and_configuring_MeeGo_SDK_for_Linux|Installing and configuring MeeGo SDK for Linux]]
* [[SDK/Docs/1.2/Checking_virtualization_support|Checking your system's graphics capabilities]]
* [[SDK/Docs/1.2/Getting_started_with_the_MeeGo_SDK_for_Windows|Installing and configuring MeeGo SDK for Windows]]
* [[SDK/Docs/1.2/Configuring_QEMU |Setting up the emulator]]
* //Are these still needed?//
** [[SDK/Docs/1.2/MeeGo_SDK_with_Xephyr|Developing with Xephyr]]
** [[SDK/Docs/1.2/Building_a_MeeGo_chroot_on_Linux|Creating a MeeGo chroot]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9482 Feature 9482]

===Device provisioning instructions===
'''Area owners:''' Taru Laine for Handset, Elliot Smith for Netbook

'''Suggested location''': developer.meego.com (DMC), Guides

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started

'''Link to MeeGo Wiki:'''
* [[SDK/Docs/1.2/Setting_up_handset|Setting up your handset ]]
* [[SDK/Docs/1.2/Setting_up_netbook|Setting up your netbook]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9483 Feature 9483]

==Developing with MeeGo SDK ==

===Best practices documentation for MeeGo 1.2 SDK===
'''Area owners:''' Taru Laine

'''Suggested location''': developer.meego.com (DMC), Guides/Guidelines

'''Changes since MeeGo 1.1 SDK''': New content area.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=12464 Feature 12464 ]

===Other documentations===
'''Note''': This feature will be divided in Bugzilla into the following new features:
* Debugging instructions for MeeGo 1.2 SDK
** Area owner: Taru Laine?
* Creating a Hello world application
** Area owner: Taru Laine (note that Netbook-related content is also needed, e.g. from Elliot)
* Instructions for building MeeGo image/QEMU image
** Area owner: Fathi Boudra? (Is this needed in MeeGo 1.2 SDK developer documentation set?)

'''Area owners:''' Taru Laine (and Elliot Smith?)

'''Suggested location''':
* Debugging: developer.meego.com (DMC), Guides
* Creating a Hello World application: developer.meego.com (DMC), Guides
* Instructions for building MeeGo image/QEMU image: wiki.meego.com

'''Changes since MeeGo 1.1 SDK''':
Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* [[SDK/Docs/1.2/Developing_for_MeeGo |Developing for MeeGo]]
* [[SDK/Docs/1.2/Creating Hello World |Creating and running your first application]]
* [[SDK/Docs/1.2/Debugging with Qt Creator |Debugging with Qt Creator]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9493 Feature 9493]

===Packaging instructions (OBS)===
'''Area owners:''' Elliot Smith

'''Suggested location''': developer.meego.com (DMC), Guides

'''Changes since MeeGo 1.1 SDK''': New content area.

'''Status''': Not started

'''Link to MeeGo Wiki:'''
//to be added//

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9484 Feature 9484]

===Packaging instructions (Application SDK)===
'''Area owners:''' Taru Laine

'''Suggested location''': developer.meego.com (DMC), Guides

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started

'''Link to MeeGo Wiki:'''
* Can this be included in:
** [[SDK/Docs/1.2/Creating Hello World |Creating and running your first application]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9485 Feature 9485]

===Troubleshooting information for MeeGo 1.2 SDK===
'''Area owners:''' Taru Laine and Elliot Smith

'''Suggested location''': developer.meego.com (DMC), Guides/FAQ or wiki.meego.com

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* [[SDK/Docs/1.2/Troubleshooting|Troubleshooting]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=12462 Feature 12462]

=== Publishing instructions ===

'''Area owners:''' Taru Laine

'''Suggested location''': developer.meego.com (DMC), Guides

'''Changes since MeeGo 1.1 SDK''':
New content area.

'''Status''': Initial content with summary and links to currently open or planned vendor developer areas (where more instructions can be found). Also link to open-source repository apps.meego.com (work in progress).

'''Link to MeeGo Wiki:'''
http://wiki.meego.com/SDK/Docs/1.2/Publishing

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9486 Feature 9486]

==UI guidelines==

=== Handset UX guidelines ===

'''Area owners:''' Ronan MacLaverty

'''Suggested location''': developer.meego.com (DMC), Guidelines

'''Changes since MeeGo 1.1 SDK''':
Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* will probably be published in meego.com, in the following sections:
** [http://meego.com/developers/meego-ux-design-principles UI design principles]
** [http://meego.com/developers/ui-design-guidelines UI design guidelines]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9487 Feature 9487]

=== Netbook UX guidelines ===

'''Area owners:''' Elliot Smith

'''Suggested location''': developer.meego.com (DMC), Guides

'''Changes since MeeGo 1.1 SDK''':
New content area.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
//to be added//

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9488 Feature 9488]

==Reference material==
=== Architectural overview===
'''Area owners:''' Taru Laine

'''Suggested location''': meego.com, Architecture (?)

'''Changes since MeeGo 1.1 SDK''':
Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* to be published in meego.com, see the following figures: [http://meego.com/developers/meego-architecture MeeGo architecture overview], [http://meego.com/developers/meego-architecture/meego-architecture-layer-view MeeGo architecture layer view],
[http://meego.com/developers/meego-architecture/meego-architecture-domain-view MeeGo architecture domain view], and
[http://meego.com/developers/meego-architecture/meego-architecture-api-view MeeGo architecture API view]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9489 Feature 9489]

===API reference (MeeGo API)===
'''Area owners:''' Murali-Krishna Punaganti

'''Suggested location''': developer.meego.com (DMC), References

'''Changes since MeeGo 1.1 SDK''':
Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* will probably be published in meego.com

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9490 Feature 9490]

===API reference (Platform API)===
'''Area owners:''' Murali-Krishna Punaganti

'''Suggested location''': wiki.meego.com

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* will probably be published in meego.com

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9491 Feature 9491]

=== Links to relevant Qt documentation===
'''Area owners:''' Taru Laine

'''Suggested location''': various (depending on the page)

'''Changes since MeeGo 1.1 SDK''':
New content area.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* This feature covers various pages in the SDK developer documentation.

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=12463 Feature 12463]

===Glossary for MeeGo 1.2 SDK===
'''Area owners:''' Taru Laine

'''Suggested location''': developer.meego.com (DMC), Glossary

'''Changes since MeeGo 1.1 SDK''': Updates according to SDK implementation.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* [[SDK/Docs/1.2/Terminology | Glossary]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=12241 Feature 12241]

==Sample Applications==
'''Area owners:''' Ville Lavonius.

'''Suggested location''': developer.meego.com (DMC), Guides/Samples

'''Changes since MeeGo 1.1 SDK''': New content area.

'''Status''': Not started.

'''Link to MeeGo Wiki:'''
* [[SDK/Docs/1.2/Example_applications | Example applications]]

'''Link to related feature in Bugzilla:'''
[http://bugs.meego.com/show_bug.cgi?id=9492 Feature 9492]

Publishing

2011-02-22T06:24:03Z

Verbosemode: moved Publishing to SDK/Docs/1.2/Publishing: Material created in wrong place

#REDIRECT [[SDK/Docs/1.2/Publishing]]

SDK/Docs/1.2/Publishing

2011-02-22T06:24:03Z

Verbosemode: moved Publishing to SDK/Docs/1.2/Publishing: Material created in wrong place

SDK/Docs/1.2/Publishing

2011-02-22T06:22:17Z

Verbosemode:

SDK/Docs/1.1/Developing for MeeGo

2011-02-17T09:52:47Z

Verbosemode: /* Building and packaging */ Packaging link broken. Fixed.

[[category:Meego-1.1]]

= MeeGo development process =

The MeeGo software development process consists of:
# [[#Analysis|Analysis]]
# [[#Design|Design]]
# [[#Coding|Coding]]
# [[#Building and packaging|Building and packaging]]

'''Note''': For an example of a Hello World application which illustrates the coding, building, and packaging phases of the application development process, see [[SDK/Docs/1.1/Creating_Hello_World |Creating and running your first application]].

== Analysis ==

In the analysis phase, read through the following sections:
* [[SDK/Docs/1.1/MeeGo developer story | MeeGo developer story]] which describes the MeeGo 1.1 application development process.
* [[SDK/Docs/1.1/MeeGo_overview | MeeGo overview ]] which describes the developer offering for MeeGo 1.1 and contains an overview of MeeGo websites and their purpose.

Select the following:
* Development target:
** MeeGo for netbooks
** MeeGo for handsets
* Development tool:
** MeeGo SDK
** Web SDK

== Design ==

To ensure the usability and user-friendliness of your application, take into consideration the following guidelines for MeeGo application development:

* [http://meego.com/developers/ui-design-guidelines UI Design Guidelines]
* [http://meego.com/developers/meego-ux-design-principles| MeeGo User Experience Design Principles ]

== Coding ==
Currently, the main SDK is the MeeGo SDK, which allows you to create native applications using Qt/C++ and Qt Quick. This SDK is based on the Qt Creator SDK, and contains support for Qt 4.7 and Qt Mobility 1.0.2 frameworks.

When you have created your project with the selected SDK, you can start coding your application.

If you are using the MeeGo SDK, you can use Qt Creator during the coding process for on-device debugging, such as setting breakpoints, and other standard debugging activities. To debug your application, follow the instructions in [[SDK/Docs/1.1/Debugging with Qt Creator | Debugging with Qt Creator]].

== Building and packaging ==
The MeeGo SDK generates packages for deploying software to MeeGo devices. When you run your application with Qt Creator, an .rpm package is created automatically. You can also package your application without running it with Qt Creator.

For more information on packaging, see [http://wiki.meego.com/SDK/Docs/1.0/Packaging_MeeGo_applications Packaging MeeGo applications].

Marketing/Why MeeGo

2011-02-12T11:40:35Z

Verbosemode: /* Application developers */

We are discussing these drafts at [http://bugs.meego.com/show_bug.cgi?id=11499 Bug 11499].

== Ibrahim's draft ==

<h1>What Makes MeeGo Unique?</h1>

<h2>MeeGo is a full open source project hosted under the auspices of the Linux Foundation</h2>
<ul>
<li>Open discussion forums, open mailing lists, open technical steering committee meetings
<li>Governed according to best practices of open source development
<li>Open source code repository
<li>Open governance model
<li>Open roadmap process & established 6 months release cycle
</ul>

<h2>MeeGo is aligned with upstream open source projects</h2>
MeeGo is aligned closely with upstream projects and combines development resources towards a unified platform that supports multiple device types (handsets, tablets, netbooks, connected-TVs, in-vehicle infotainment systems). It requires that submitted patches also be submitted to the appropriate upstream project and be on a path for acceptance. As a result, a large number of upstream projects will benefit from the MeeGo contribution.

<h2>MeeGo offers a complete and optimized software stack</h2>
MeeGo offers a complete and optimized software stack, from the kernel to the libraries and middleware components up to reference UX implementations, along with a rich cross-platform development environment and tools.

<h2>MeeGo has a very active developer community</h2>
MeeGo has a very active community that consists of more than 12,000 participants registered at MeeGo.com contributing source code, QA, documentation, translation, etc.

<h2>MeeGo offers equal opportunities</h2>
MeeGo offers equal opportunities for all industry players to participate in the evolution of the software platform and to build their own assets on MeeGo and offers differentiation abilities through the customization and branding of the user experience. Furthermore, it offers the ability to participate in the evolution of the software platform, and other Linux mobile and desktop efforts will benefit from MeeGo’s work.

<h2>MeeGo and App Developers</h2>
For application developers, MeeGo has a very attractive offering:
<ul>
<li>Support for a single set of APIs across client devices (easily and rapidly create and deploy apps)
<li>Support for five different device types (create apps and run it on multiple device types)
<li>Support for multiple app stores (host apps in several app stores, or even create your own app store)
</ul>

<h2>MeeGo Compliance Program</h2>
MeeGo also offers a compliance program to certify software stacks and application portability from the get go.

<h2>MeeGo supports multiple hardware architectures</h2>
MeeGo supports multiple hardware architectures. Currently, ARM and x86 processors are supported with possibly support for additional architectures in near future.

<h2>MeeGo offers opportunities for differentiation </h2>
MeeGo offers differentiation abilities through UX customization. You can use the reference UXs and customize it for your own brand or create your own UX.

<h2>In a nutshell ... </h2>
<ul>
<li>Great UX
<li>Great OS
<li>Multi-category
<li>Multi-HW
<li>Active community
<li>Open governance model
<li>Close relation with upstream projects
<li>A partnership project
<li>Compliance program
<li>Successful app store story
<li>Successful app dev story
<li>Ability to provide areas for differentiation and support for proprietary add-ons
</ul>

<h1>Benefits of the MeeGo Platform</h1>
The MeeGo open source project is unique in that it offers benefits to everyone in the ecosystem starting from the developer all the way up to the operator and the industry as a whole. Meego allows participants to get involved and contribute to an industry-wide evolution towards richer devices, to rapidly address opportunities and to focus on differentiation in their target markets.

<h2>Benefits to Open Source Developers</h2>
The MeeGo project is a true open source project hosted by the Linux Foundation and governed by best practices of open source development. From meego.com, as an open source developer, you have access to tools, mailing lists, discussion forum, accessibility to technical meetings, and multiple options to make your voice heard over technical and non-technical MeeGo related topics. Furthermore, all source code contributions needed for MeeGo will be submitted to the upstream open source projects from which MeeGo will be built.

<h2>Benefits to App Developers</h2>
As an application developer, MeeGo significantly expands the market opportunities for you being the only open source software platform that supports deployments across many computing device types. MeeGo offers Qt and Web runtime for application development, cross platform environments, so application developers can write their applications once and deploy easily on many types of MeeGo devices or even on other platforms supporting the same development environment.
Furthermore, MeeGo offers a complete set of tools for developers to create easily and rapidly a variety of innovative applications (see http://meego.com/developers/getting-started). The major advantage from this approach is having a single set of APIs across client devices. In addition, in this context multiple devices is much broader than just multiple handset for instance; MeeGo device types include media phones, handhelds, IVI systems, connected-TVs and netbooks.
In addition, MeeGo application developers will the opportunity to make their applications available from multiple application stores such as the Nokia’s Ovi Store and the Intel’s AppUp Center. In addition, there is the opportunity of hosting the applications on other app stores for specific carriers carrying MeeGo devices as part of their device offering. These MeeGo capabilities, cross-device and cross-platform development, are major differentiator and offer huge benefits to the developers.

<h2>Benefits to Device manufacturers</h2>
MeeGo helps accelerate time to market using an off-the-shelf, open source and optimized software stack targeted for the specific hardware architecture the device manufacturer is supporting. From a device manufacturer perspective, MeeGo lowers complexities involved in targeting multiple device segments by allowing the use of the same software platform for different client devices. In addition, as an open source project, MeeGo enables device manufacturers to participate in the evolution of the software platform and build their own assets for it through the open development model.

<h2>Benefits to Operators/Carriers</h2>
For operators, MeeGo enables differentiation through user interface customization. Although many devices can be running the same base software platform, they can all have different user experiences. Furthermore, it provides a single platform for multitude of devices, minimizing the efforts needed by the operators in training their teams and allows their subscribers to be familiar with the experience common to many device types.

<h2>Benefits to the Linux Technical Platform</h2>

== Alisson's draft for product developers ==

Goes here. Feel free borrowing other texts in this page.

== Application developers ==
'''Note: This needs fact-checking.''' The text was written to follow directly after the question Why MeeGo? or Why develop on Meego?, so that is why it is written in this style.

'''Be a part of an open, collaborative ecosystem'''

MeeGo is a fully open-source project hosted by the Linux Foundation – meaning it’s not under a single company’s control like other mobile platforms. An open, collaborative environment encourages innovation through:

*free exchange of ideas and source code
*peer review
*unifying development across multiple device categories, and
*contributions to and development of other Linux mobile and desktop efforts that use the components of MeeGo

'''Development is fast and easy'''

*With the MeeGo SDK, you can create applications for a range of devices from a single code base
*MeeGo uses the Qt framework, allowing rapid UI development based on QML and JavaScript, and is also easily extensible with C++ objects
*Because MeeGo is built upon the Linux kernel, most of the APIs, development tools and libraries available in Linux are available in MeeGo too

'''Wide-reaching publishing opportunities'''

*Rapidly deploy applications across:
**multiple device types – smartphones, tablets, netbooks, connected TVs and in-vehicle infotainment systems
**multiple app stores – MeeGo is backed by multiple vendors, so apps can be published in Intel’s AppUp, WeTab Market, Alive by Acer, and more, or in community app marketplaces like MeeGo Apps (coming soon)
**multiple platforms – Qt and Web runtime are the basis for MeeGo application development, so apps can be deployed on virtually any platform supporting these cross-platform development frameworks

'''Get help when you need it'''

*Become part of a friendly community with active mailing lists and forums
*Find complete documentation and code samples to walk you through the development process

---------------
Original from Quim:

MeeGo is a vehicle for fostering innovations through an open collaborative environment promoting exchange of ideas and source code, peer review, unifying development from across multiple device categories, and driving contributions and technical work upstream to the various open source projects. In addition, MeeGo is helpful for Linux as a platform as it combines mobile development resources that were recently split in the Maemo and Moblin projects into one well-supported, well-designed project that addresses cross-platform, cross-device and cross-architecture development. One major benefit from the MeeGo project is that all other Linux mobile and desktop efforts that use the components as MeeGo will benefit from the increased engineering efforts on those components. This is the power of the open source development model.

Marketing/Why MeeGo

2011-02-12T11:29:23Z

Verbosemode: /* Application developers */

We are discussing these drafts at [http://bugs.meego.com/show_bug.cgi?id=11499 Bug 11499].

== Ibrahim's draft ==

<h1>What Makes MeeGo Unique?</h1>

<h2>MeeGo is a full open source project hosted under the auspices of the Linux Foundation</h2>
<ul>
<li>Open discussion forums, open mailing lists, open technical steering committee meetings
<li>Governed according to best practices of open source development
<li>Open source code repository
<li>Open governance model
<li>Open roadmap process & established 6 months release cycle
</ul>

<h2>MeeGo is aligned with upstream open source projects</h2>
MeeGo is aligned closely with upstream projects and combines development resources towards a unified platform that supports multiple device types (handsets, tablets, netbooks, connected-TVs, in-vehicle infotainment systems). It requires that submitted patches also be submitted to the appropriate upstream project and be on a path for acceptance. As a result, a large number of upstream projects will benefit from the MeeGo contribution.

<h2>MeeGo offers a complete and optimized software stack</h2>
MeeGo offers a complete and optimized software stack, from the kernel to the libraries and middleware components up to reference UX implementations, along with a rich cross-platform development environment and tools.

<h2>MeeGo has a very active developer community</h2>
MeeGo has a very active community that consists of more than 12,000 participants registered at MeeGo.com contributing source code, QA, documentation, translation, etc.

<h2>MeeGo offers equal opportunities</h2>
MeeGo offers equal opportunities for all industry players to participate in the evolution of the software platform and to build their own assets on MeeGo and offers differentiation abilities through the customization and branding of the user experience. Furthermore, it offers the ability to participate in the evolution of the software platform, and other Linux mobile and desktop efforts will benefit from MeeGo’s work.

<h2>MeeGo and App Developers</h2>
For application developers, MeeGo has a very attractive offering:
<ul>
<li>Support for a single set of APIs across client devices (easily and rapidly create and deploy apps)
<li>Support for five different device types (create apps and run it on multiple device types)
<li>Support for multiple app stores (host apps in several app stores, or even create your own app store)
</ul>

<h2>MeeGo Compliance Program</h2>
MeeGo also offers a compliance program to certify software stacks and application portability from the get go.

<h2>MeeGo supports multiple hardware architectures</h2>
MeeGo supports multiple hardware architectures. Currently, ARM and x86 processors are supported with possibly support for additional architectures in near future.

<h2>MeeGo offers opportunities for differentiation </h2>
MeeGo offers differentiation abilities through UX customization. You can use the reference UXs and customize it for your own brand or create your own UX.

<h2>In a nutshell ... </h2>
<ul>
<li>Great UX
<li>Great OS
<li>Multi-category
<li>Multi-HW
<li>Active community
<li>Open governance model
<li>Close relation with upstream projects
<li>A partnership project
<li>Compliance program
<li>Successful app store story
<li>Successful app dev story
<li>Ability to provide areas for differentiation and support for proprietary add-ons
</ul>

<h1>Benefits of the MeeGo Platform</h1>
The MeeGo open source project is unique in that it offers benefits to everyone in the ecosystem starting from the developer all the way up to the operator and the industry as a whole. Meego allows participants to get involved and contribute to an industry-wide evolution towards richer devices, to rapidly address opportunities and to focus on differentiation in their target markets.

<h2>Benefits to Open Source Developers</h2>
The MeeGo project is a true open source project hosted by the Linux Foundation and governed by best practices of open source development. From meego.com, as an open source developer, you have access to tools, mailing lists, discussion forum, accessibility to technical meetings, and multiple options to make your voice heard over technical and non-technical MeeGo related topics. Furthermore, all source code contributions needed for MeeGo will be submitted to the upstream open source projects from which MeeGo will be built.

<h2>Benefits to App Developers</h2>
As an application developer, MeeGo significantly expands the market opportunities for you being the only open source software platform that supports deployments across many computing device types. MeeGo offers Qt and Web runtime for application development, cross platform environments, so application developers can write their applications once and deploy easily on many types of MeeGo devices or even on other platforms supporting the same development environment.
Furthermore, MeeGo offers a complete set of tools for developers to create easily and rapidly a variety of innovative applications (see http://meego.com/developers/getting-started). The major advantage from this approach is having a single set of APIs across client devices. In addition, in this context multiple devices is much broader than just multiple handset for instance; MeeGo device types include media phones, handhelds, IVI systems, connected-TVs and netbooks.
In addition, MeeGo application developers will the opportunity to make their applications available from multiple application stores such as the Nokia’s Ovi Store and the Intel’s AppUp Center. In addition, there is the opportunity of hosting the applications on other app stores for specific carriers carrying MeeGo devices as part of their device offering. These MeeGo capabilities, cross-device and cross-platform development, are major differentiator and offer huge benefits to the developers.

<h2>Benefits to Device manufacturers</h2>
MeeGo helps accelerate time to market using an off-the-shelf, open source and optimized software stack targeted for the specific hardware architecture the device manufacturer is supporting. From a device manufacturer perspective, MeeGo lowers complexities involved in targeting multiple device segments by allowing the use of the same software platform for different client devices. In addition, as an open source project, MeeGo enables device manufacturers to participate in the evolution of the software platform and build their own assets for it through the open development model.

<h2>Benefits to Operators/Carriers</h2>
For operators, MeeGo enables differentiation through user interface customization. Although many devices can be running the same base software platform, they can all have different user experiences. Furthermore, it provides a single platform for multitude of devices, minimizing the efforts needed by the operators in training their teams and allows their subscribers to be familiar with the experience common to many device types.

<h2>Benefits to the Linux Technical Platform</h2>

== Alisson's draft for product developers ==

Goes here. Feel free borrowing other texts in this page.

== Application developers ==
'''Note: This needs fact-checking.''' The text was written to follow directly after the question Why MeeGo? or Why develop on Meego?, so that is why it is written in this style.

'''Be a part of an open, collaborative ecosystem'''

MeeGo is a fully open-source project hosted by the Linux Foundation – meaning it’s not under a single company’s control like other mobile platforms. An open, collaborative environment encourages innovation through:

*free exchange of ideas and source code
*peer review
*unifying development across multiple device categories, and
*contributions to and development of other Linux mobile and desktop efforts that use the components of MeeGo

'''Development is fast and easy'''

*With the MeeGo SDK, you can create applications for a range of devices from a single code base
*MeeGo uses the Qt framework, allowing rapid UI development based on QML and JavaScript, and is also easily extensible with C++ objects
*Because MeeGo is built upon the Linux kernel, most of the APIs, development tools and libraries available in Linux are available in MeeGo too

'''Wide-reaching publishing opportunities'''

*Rapidly deploy applications across:
**multiple device types – smartphones, tablets, netbooks, connected TVs and in-vehicle infotainment systems
**multiple app stores – MeeGo is backed by multiple vendors, so apps can be published in Intel’s AppUp, WeTab Market, Alive by Acer, and more, or in community app marketplaces like MeeGo Apps (coming soon)
**multiple platforms – Qt and Web runtime are the basis for MeeGo application development, so apps can be deployed on virtually any platform supporting these cross-platform development frameworks

'''Get help when you need it'''

*Join a friendly community with active mailing lists and forums
*Find complete documentation and code samples to walk you through the development process

---------------
Original from Quim:

MeeGo is a vehicle for fostering innovations through an open collaborative environment promoting exchange of ideas and source code, peer review, unifying development from across multiple device categories, and driving contributions and technical work upstream to the various open source projects. In addition, MeeGo is helpful for Linux as a platform as it combines mobile development resources that were recently split in the Maemo and Moblin projects into one well-supported, well-designed project that addresses cross-platform, cross-device and cross-architecture development. One major benefit from the MeeGo project is that all other Linux mobile and desktop efforts that use the components as MeeGo will benefit from the increased engineering efforts on those components. This is the power of the open source development model.

Marketing/Why MeeGo

2011-02-12T11:28:47Z

Verbosemode: /* Tiffiny's draft for app developers */ Marketing to App Developers 101

We are discussing these drafts at [http://bugs.meego.com/show_bug.cgi?id=11499 Bug 11499].

== Ibrahim's draft ==

<h1>What Makes MeeGo Unique?</h1>

<h2>MeeGo is a full open source project hosted under the auspices of the Linux Foundation</h2>
<ul>
<li>Open discussion forums, open mailing lists, open technical steering committee meetings
<li>Governed according to best practices of open source development
<li>Open source code repository
<li>Open governance model
<li>Open roadmap process & established 6 months release cycle
</ul>

<h2>MeeGo is aligned with upstream open source projects</h2>
MeeGo is aligned closely with upstream projects and combines development resources towards a unified platform that supports multiple device types (handsets, tablets, netbooks, connected-TVs, in-vehicle infotainment systems). It requires that submitted patches also be submitted to the appropriate upstream project and be on a path for acceptance. As a result, a large number of upstream projects will benefit from the MeeGo contribution.

<h2>MeeGo offers a complete and optimized software stack</h2>
MeeGo offers a complete and optimized software stack, from the kernel to the libraries and middleware components up to reference UX implementations, along with a rich cross-platform development environment and tools.

<h2>MeeGo has a very active developer community</h2>
MeeGo has a very active community that consists of more than 12,000 participants registered at MeeGo.com contributing source code, QA, documentation, translation, etc.

<h2>MeeGo offers equal opportunities</h2>
MeeGo offers equal opportunities for all industry players to participate in the evolution of the software platform and to build their own assets on MeeGo and offers differentiation abilities through the customization and branding of the user experience. Furthermore, it offers the ability to participate in the evolution of the software platform, and other Linux mobile and desktop efforts will benefit from MeeGo’s work.

<h2>MeeGo and App Developers</h2>
For application developers, MeeGo has a very attractive offering:
<ul>
<li>Support for a single set of APIs across client devices (easily and rapidly create and deploy apps)
<li>Support for five different device types (create apps and run it on multiple device types)
<li>Support for multiple app stores (host apps in several app stores, or even create your own app store)
</ul>

<h2>MeeGo Compliance Program</h2>
MeeGo also offers a compliance program to certify software stacks and application portability from the get go.

<h2>MeeGo supports multiple hardware architectures</h2>
MeeGo supports multiple hardware architectures. Currently, ARM and x86 processors are supported with possibly support for additional architectures in near future.

<h2>MeeGo offers opportunities for differentiation </h2>
MeeGo offers differentiation abilities through UX customization. You can use the reference UXs and customize it for your own brand or create your own UX.

<h2>In a nutshell ... </h2>
<ul>
<li>Great UX
<li>Great OS
<li>Multi-category
<li>Multi-HW
<li>Active community
<li>Open governance model
<li>Close relation with upstream projects
<li>A partnership project
<li>Compliance program
<li>Successful app store story
<li>Successful app dev story
<li>Ability to provide areas for differentiation and support for proprietary add-ons
</ul>

<h1>Benefits of the MeeGo Platform</h1>
The MeeGo open source project is unique in that it offers benefits to everyone in the ecosystem starting from the developer all the way up to the operator and the industry as a whole. Meego allows participants to get involved and contribute to an industry-wide evolution towards richer devices, to rapidly address opportunities and to focus on differentiation in their target markets.

<h2>Benefits to Open Source Developers</h2>
The MeeGo project is a true open source project hosted by the Linux Foundation and governed by best practices of open source development. From meego.com, as an open source developer, you have access to tools, mailing lists, discussion forum, accessibility to technical meetings, and multiple options to make your voice heard over technical and non-technical MeeGo related topics. Furthermore, all source code contributions needed for MeeGo will be submitted to the upstream open source projects from which MeeGo will be built.

<h2>Benefits to App Developers</h2>
As an application developer, MeeGo significantly expands the market opportunities for you being the only open source software platform that supports deployments across many computing device types. MeeGo offers Qt and Web runtime for application development, cross platform environments, so application developers can write their applications once and deploy easily on many types of MeeGo devices or even on other platforms supporting the same development environment.
Furthermore, MeeGo offers a complete set of tools for developers to create easily and rapidly a variety of innovative applications (see http://meego.com/developers/getting-started). The major advantage from this approach is having a single set of APIs across client devices. In addition, in this context multiple devices is much broader than just multiple handset for instance; MeeGo device types include media phones, handhelds, IVI systems, connected-TVs and netbooks.
In addition, MeeGo application developers will the opportunity to make their applications available from multiple application stores such as the Nokia’s Ovi Store and the Intel’s AppUp Center. In addition, there is the opportunity of hosting the applications on other app stores for specific carriers carrying MeeGo devices as part of their device offering. These MeeGo capabilities, cross-device and cross-platform development, are major differentiator and offer huge benefits to the developers.

<h2>Benefits to Device manufacturers</h2>
MeeGo helps accelerate time to market using an off-the-shelf, open source and optimized software stack targeted for the specific hardware architecture the device manufacturer is supporting. From a device manufacturer perspective, MeeGo lowers complexities involved in targeting multiple device segments by allowing the use of the same software platform for different client devices. In addition, as an open source project, MeeGo enables device manufacturers to participate in the evolution of the software platform and build their own assets for it through the open development model.

<h2>Benefits to Operators/Carriers</h2>
For operators, MeeGo enables differentiation through user interface customization. Although many devices can be running the same base software platform, they can all have different user experiences. Furthermore, it provides a single platform for multitude of devices, minimizing the efforts needed by the operators in training their teams and allows their subscribers to be familiar with the experience common to many device types.

<h2>Benefits to the Linux Technical Platform</h2>

== Alisson's draft for product developers ==

Goes here. Feel free borrowing other texts in this page.

== Application developers ==
'''Note: This needs fact-checking.''' The text was written to follow directly after the question Why MeeGo? or Why develop on Meego?, so that is why it is written in this style.

'''Be a part of an open, collaborative ecosystem'''

MeeGo is a fully open-source project hosted by the Linux Foundation – meaning it’s not under a single company’s control like other mobile platforms. An open, collaborative environment encourages innovation through:

*free exchange of ideas and source code
*peer review
*unifying development across multiple device categories, and
*contributions to and development of other Linux mobile and desktop efforts that use the components of MeeGo

'''Development is fast and easy'''

*With the MeeGo SDK, you can create applications for a range of devices from a single code base
*MeeGo uses the Qt framework, allowing rapid UI development based on QML and JavaScript, and is also easily extensible with C++ objects
*Because MeeGo is built upon the Linux kernel, most of the APIs, development tools and libraries available in Linux are available in MeeGo too

'''Wide-reaching publishing opportunities'''

*Rapidly deploy applications across:
**multiple device types – smartphones, tablets, netbooks, connected TVs and in-vehicle infotainment systems
**multiple app stores – MeeGo is backed by multiple vendors, so apps can be published in Intel’s AppUp, WeTab Market, Alive by Acer, and more, or in community app marketplaces like MeeGo Apps (coming soon)
**multiple platforms – Qt and Web runtime are the basis for MeeGo application development, so apps can be deployed on virtually any platform supporting these cross-platform development frameworks

'''Get help when you need it'''

*Join a friendly community with active mailing lists and forums
*Find complete documentation and code samples to walk you through the development process

*********************
Original from Quim:

MeeGo is a vehicle for fostering innovations through an open collaborative environment promoting exchange of ideas and source code, peer review, unifying development from across multiple device categories, and driving contributions and technical work upstream to the various open source projects. In addition, MeeGo is helpful for Linux as a platform as it combines mobile development resources that were recently split in the Maemo and Moblin projects into one well-supported, well-designed project that addresses cross-platform, cross-device and cross-architecture development. One major benefit from the MeeGo project is that all other Linux mobile and desktop efforts that use the components as MeeGo will benefit from the increased engineering efforts on those components. This is the power of the open source development model.

SDK/Docs/1.2/Publishing

2011-02-09T11:04:52Z

Verbosemode:

Get your apps published

== App stores ==

The MeeGo platform offers wide-reaching market opportunities to app developers because multiple app stores are distributing MeeGo apps. The store support is growing as MeeGo continues to evolve and more MeeGo devices appear on the market.

Current and stores that support MeeGo include:

[http://appdeveloper.intel.com Intel AppUp]

Intel AppUp allows you to distribute and sell your applications to millions of netbook users. AppUp features a broad distribution model with multiple storefronts.

[http://www.forum.nokia.com/Distribute Ovi Store by Nokia]

Ovi Store has a global reach, attracting users from over 190 countries and in 30 languages. Operator and credit card billing offer easy ways for people to buy apps from Ovi Store.

[http://wetab.mobi/en/developers/ WeTab Market]

The WeTab marketplace will open in early 2011.

== Free marketplaces and repositories ==

You can also publish your application through open source marketplaces and repositories.

[http://apps.meego.com MeeGo Apps]

Coming soon! MeeGo Apps is the repository where software created by the MeeGo community can be found. Developers can build their applications on the MeeGo Community OBS, a sophisticated build system. These applications can then be published into the Apps repository after certain conditions have been met.

[http://wiki.meego.com/MeeGo_Apps MeeGo Apps wiki]