• Intro
• Downloads
• Community
• Development
• News
• TALK

Task:Improving maemo.org/proposal

Revision as of 15:56, 12 September 2008

Improving maemo.org

Goals

We will:

• Reorganise existing content to allow most common use-cases to be fulfilled easily
• Create new content where appropriate to fulfill use-cases
• Remove or move information which does not contribute to the most common use-cases
• Make the site visually attractive and fresh, to match the maemo.org visuals
• Make different maemo.org sites visually consistent
• Ensure the site works well on the tablets

Non-goals

We will not:

• Re-write all content
• Move away from Midgard
• Load the site with heavy visual content (see tablet goal).

Use cases

The following are the core use-cases to be addressed by the website rework:

1. A new tablet owner wants to install some software on his tablet. He arrives at http://maemo.org/downloads after a web search for "Nokia tablet software download", and navigating through the #6 link. (NOTE: search for "Nokia N810 software download", the download page on maemo.org is not on the first 10 pages).
2. An interested application developer comes to maemo.org to learn how to write a new application for the tablet.
3. An existing application developer comes to maemo.org looking for information on modifying his application for Maemo.
4. A Maemo Community member is looking for the latest news from around the world of Maemo
5. An interested user wants to know how he can help make Maemo better
6. A community member wants to know what the future plans for Maemo are, and wants to suggest features and priorities
7. A tablet user has a problem which they would like to resolve.
8. A site maintainer or community member wants to create a new news item, or promote new important content so that it gets more attention.

Current maemo.org website

For reference.

Content:

• Introduction
• Dowloads
• Community
• Development
• News

Sub-menu:

• • Documentation -> Development/Documentation
  • Tutorials -> Development/Documentation/Tutorials
  • Roadmap -> Development/Roadmap
  • Lists -> Community/mailing-lists.html
  • Bugzilla -> http://maemo.org/bugzilla
  • Wiki -> http://wiki.maemo.org
  • IRC -> Community/IRC
  • SDK -> Development/SDKs
  • Repositories -> community/wiki/applicationrepositories

Disparate websites

• http://maemo.org
• http://bugs.maemo.org
• http://wiki.maemo.org
• http://planet.maemo.org
• http://garage.maemo.org
• http://www.internettablettalk.com/
• http://www.gronmayer.com/it/
• http://maemo.org/downloads
• http://europe.nokia.com/A4579470

Plus: External articles, reviews, blogs, press, tutorials, FAQs, wikis, ...

Proposed steps for revamp

1. Theme:

Need a refreshed look & theme corresponding to maemo.org visual identity change. Proposal: Community generated mock-ups, perhaps one or two Nokia sponsored mock-ups.

Deadlines for mock-ups for design mid October

2. Content Organisation

There are two aspects: content and its organisation.

• Content: Need to evaluate existing content for its usefulness for common use-cases. Need to ensure it is obvious when content is out-dated/deprecated.
• Sub-sites:
  • Midgard vs Wiki vs gtkdoc vs ...
• Organisation: Existing content should be presented and linked to in a way that makes popular tasks easy, and unpopular tasks available through linking, and also through search (site search and web search).

We need to look at 3 things:

• Clean page layout for all portal pages - pages must bring you easily to the content you're interested in, if you are in the most common use-cases
• Efficient search on website
• Web search indexing of Maemo content
• Ensure all outdated content is removed from the primary navigation paths of users interested in common use-cases.

Proposal

• Proposals for information to be given place of honour on the maemo.org front page, and on each of the sub-portals, in particular documentation, news, community (see proposal by timsamoff at https://wiki.maemo.org/Task:Improving_maemo.org/community) but also review intro in light of redesign.
• Proposal for hierarchy which makes most useful information easily available

Proposals due for October 1st.

Suggested items for proposals:

• Delete old wiki content completely - it is polluting Google juice, and confusing users who see it as new information
• Ask gronmayer to take site off-line, in favour of a really useful extras (we're getting there)
• Re-organise documentation by release rather than by purpose:
  • OS2008/tutorials, OS2008/SDK reference, etc...
  • Currently, OS2008, OS2007, ... docs are all mixed together in each category
  • Makes it easier to archive outdated information when they're done this way
  • Link to HTML reference documentation in favour of PDF
  • Promote useful wiki pages to http://maemo.org/documentation
  • News page should include links to outside articles, blogs, official announcements, high-ranked ITT threads, etc. It should be a window on the highest-ranked Maemo time-sensitive content

I'm unsure what to do with outside content. The ideal would be to have a kind of call-back system, where we link to it from the most appropriate place in maemo.org, but this isn't a maintainable solution right now.

3. Marrying content and style

• Ruthlessly reduce the number of words on portal pages
• Need graphics and navigation structure which are ergonomic and attractive
• Suggest that web designers behind the themes must be involved at this stage. A first draft of the new portal pages can be part of the new theme proposals (thus the deadline for themes being later than content organisations.

Themes to be evaluated by a group of community members named by the council, winner to be chosen from mock-ups November 1st.

Deadline for accepting both theme and content re-organisation: November 1st.

Once we have a theme, and an organisation of the existing content which makes sense, we must execute, with the participation of the web design & graphics team and copy editors, to ensure that the portal sites fulfill their goal, while remaining manageable over time.

The website re-work should be completed by December 1st.