The Great

revision

Goal:

Improve maemo.org

Goal:

World peace

Everest, by Andrew Purdhamhttp://flickr.com/photos/apurdam/189844612/

1. Getting to Nepal

Step 1:

Who is maemo.org for?

Users looking forsoftware

Who is maemo.org for?

Developers looking fortutorials

Who is maemo.org for?

A developer wants to find information on creating a new application with Maemo, or on porting an existing desktop application to Maemo

This covers training information, guides and tutorials, HIG guidelines for the tablet and porting guides.

Developers looking forreference documentation

Who is maemo.org for?

You're al existing developer, and you're stuck into making your application. You want API documentation, you want it to be searchable. You want to know how to store config options, how to find out what signals are exposed over D-Bus by application X or library Y.

Enthusiasts looking fornews and ways to help

Who is maemo.org for?

A Maemo Community member is looking for the latest news from around the world of Maemo

An interested user wants to know how he can help make Maemo better

I also include in this people who want to get in touch with the Maemo community but don't necessarily know how here's where we can direct people to IRC, mailing lists, itT, etc.

People interested in thefuture direction

Who is maemo.org for?

Interested users, community members and press want to know what the future direction of the project will be, and how they fit into it. A project roadmap, product announcements, etc. Community members want to know that their opinion counts, and that they can influence the future direction.

Users with problems

Who is maemo.org for?

People come to maemo.org when they have something they can't figure out, or something which isn't working as it should, to figure out how to make it work, to get help, to find others with the same issue to share their pain.

People with things to say

Who is maemo.org for?

maemo.org is not a read-only resource, it is also for Nokia and the Maemo community to announce what they're working on, to share news and announcements, and to collaborate together on the platform.

Step 2:

What content needschanging?

The next thing we need to do is filter what's good from what's not so good we don't want to rewrite everything, and official docs and API docs are very high quality documentation. What we need to do is improve the content that doesn't currently meet editorial standards, and streamline the site to make sure that our core use-cases can find where they need to go quickly.

Portal pages (Intro thanks Peter!, Community thanks Tim!, Development, News, homepage)

What content needs changing?

There are a number of common entry points to maemo.org the front page, the downloads page, the news page... we need to identify these entry points, and streamline them to allow people to get to where they need to be quickly

Official documentationstructure (more searchable, make latest docs more prominent)

What content needs changing?

When you go looking for official documentation now, you get brought to pages presenting docs for OS2006, 2007, and 2008.1 and typically the 2008.1 docs linked to are a PDF rather than HTML.

I think that we need to date articles, but avoid the intermediary step and link to the latest docs, while providing older docs in a harder-to-navigate to (but easy to link to) archive of docs.

We need to come up with a link structure that makes sense, and propose it to the documentation team for feedback and execution.

General navigationstructure (Cater to core use-cases ruthlessly,find & improve entry points)

What content needs changing?

Some simple tasks need many clicks now we need to find these, and make them easy, without burdening the portal pages with long lists of links.,

Update what needs updating

What content needs changing?

We can trawl the site, page by page, to decide what content needs updating, and then get it updated.

Decide what we canthrow out (old wiki, old docs, ...)

What content needs changing?

People come to maemo.org when they have something they can't figure out, or something which isn't working as it should, to figure out how to make it work, to get help, to find others with the same issue to share their pain.

Integration of wiki, itT,RSS feeds, ... into site

What content needs changing?

Righht now, outside sites are clearly different and external to maemo.org whether it's the wiki, itT or external documentation, tutorials and so on. We need to make sure that the best docs available are linked to from within maemo.org in the most appropriate place.

Referencing(see where maemo.org shows up when searching for Nokia N810 software downloads on Google,then try N810 software downloads)

What content needs changing?

For some common Maemo related searches I tried, maemo.org isn't very well ranked, or old wiki pages with outdated information out-rank the new wiki pages or updated docs. We need to make sure that, since Google is the primary way people come to the site, the correct informatin is what gets prominently featured and linked to on maemo.org and elsewhere.

Step 3:

What will it look like?

Fewer words

What will it look like?

Must be clean and easy to navigate in one glance

More graphics

What will it look like?

Nice (design work isn't my area :-) )

What will it look like?

We will refresh the style of the page, and we'll be looking for community submissions for this. Not my forte :).

Layout + minimal content + new style

What will it look like?

.

Step 4:

Putting it all together

Roll-out: December 2008 ???

Thanks!