Task:Improving maemo.org

This article is continued discussion from the maemo.org brainstorm
Please see the 100 Days agenda for more.
This task is completed and this page stays here for documentation purposes only. Please file bugs or propose a new, related task if you want to push this forward.
Please see the talk page for discussion.

Connected to Task:Content Cleanup


[edit] 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

[edit] Non-goals

We will not:

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

[edit] 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.
  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 or give feedback
  6. A tablet user has a problem which they would like to resolve.

[edit] Content

We need to change some of the content substantially:

We don't need to substantially revise the Intro, News or Downloads pages.

The front page will primarily be portal pages to help get people where they want to go, but also to let people get a flavour of the Maemo community.

The community page will show the Maemo community in all its glory - covering communication, people, projects, what's new, what's cool, what we're up to. The page will be almost entirely dynamic and will reflect the current state of Maemo.

The Development page should respond to four different needs - getting software development kits and images for development, getting general introductions, tutorials, overviews of the platform and other general information, exposing searchable reference documents for the Maemo platform APIs, and finally (but very importantly, giving a visitor a map of the developer-focused communication forums that exist in Maemo, including itT, mailing lists, IRC and the wiki.

[edit] Maemo.org Homepage refresh

The concept of the existing maemo.org homepage is good and we should keep it.

The final make-up of the maemo.org front-page will be based on Tim Samoff's final proposal:

  • A title bar with the new maemo.org logo
  • A menu containing:
  • A search box which will search the website. Ideally, the search results page will allow the user to filter parts of the site only.
  • Discrete "Log in / Register" links (or, when logged in, a link to the user's profile page, with "Welcome back, Dave Neary" or something similar)
  • Prominently featured at the top of the page, the current "Fresh" and "Hot" downloads, which should point to the latest updated application, and one of the featured application ("the pearl"), the most popular application or the best rated application (to be decided) on the downloads page.
  • News - the front page should feature a section with the 5 most recent headlines from http://maemo.org/news/, including the lead paragraph for the most recent news item
  • Sidebar - other elements in the page will be less prominently placed, in a side-bar
  • Page footer
    • Copyright notice (note content will be copyright Nokia and respective authors - wording to be clarified)
    • Legal notices - points to http://maemo.org/legal which will contain copyright & trademark notices and trademark style guide, terms of use and privacy policy
    • "Midgard CMS" - a link to http://www.midgard-project.org/
    • A notice that the site is "Sponsored by Nokia"

[edit] Design drafts

[edit] Tracking progress

Progress on the implementation of this new maemo.org style is being tracked on the page Task:Implement new maemo.org layout and style.

[edit] Community

Main Article: Task:Improving_maemo.org/Community

[edit] Functionality and navigation

  • Single sign on for maemo.org/garage.maemo.org/wiki/bugzilla -> would make community participation easier and the 'karma' calculation (if needed) too.
Ferenc is working on bugzilla, IIRC. The others already have one account for all. --xfade 13:49, 2 June 2008 (UTC)
The "one account for all" is not the same as Single Sign-On (SSO). SSO would need additional software and integration. The one account for all feature will be completed when bugzilla will use garage for authentication. This is work in progress and will be completed in the June sprint. --feri 14:08, 2 June 2008 (UTC)
  • The user login process really is broken. Secondly, the login for the wiki has terrible user interface design, as it does not point to a page where one can register, despite the fact that it is called the "Log in / create account" page. --mee 13:54, 7 June 2008 (UTC)

[edit] Style and format

Proposal: Open proposal for community generated mock-ups, and one or two Nokia sponsored mock-ups from INdT.

Main article: Task:Maemo.org facelift

See also Task:Improving maemo.org/Graphics

[edit] 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.
    • Delete old wiki content completely - it is polluting Google juice, and confusing users who see it as new information
    • 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
  • Integration with sub-sites and partner sites:
    • Midgard vs Wiki vs gtkdoc vs ...
    • Ask gronmayer to take site off-line, in favour of a really useful extras (we're getting there)
  • 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 will reorganise information on tutorials, SDKs, and platform APIs so that the site user will encounter the most up-to-date information by default, and must dig a bit deeper to get out-of-date legacy information
    • Move to OS2008/tutorials, OS2008/SDK reference, etc...
    • Currently, OS2008, OS2007, ... docs are all mixed together in each category
    • Link to HTML reference documentation in favour of PDF
    • Promote useful wiki pages to http://maemo.org/documentation

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.

[edit] Smoothing the introduction of new users to maemo.org

  • The development section should be organized in a simple, clear and centralized way to beginners. The following information is important and should be presented to the newcomers immediately they enter the development section.
  1. Simple steps of getting started should be presented in a clear and definite way ,on a conspicuous area with color. for example:
    1. Sign up a maemo account (link to register page)
    2. Download and set up development environment.(link to detailed method page)
    3. Create hello world application, Package and Test(link to several typical and simple examples,and useful links to advanced docs should be included)
    4. Collaboration on maemo.org and Launch app on the download section (link to pages including usage of project homepage)
  2. Key features of maemo platform should be presented on the section page explicitly.
    1. Free to develop and launch applications.
    2. Powerful enough to create advanced applications.
    3. Flexibility in programming (Gtk+/C,Python,Qt and etc)
    4. Easy to port existing application.
  3. Wiki on frequent technical problems in programming(the how-tos part),and entry to developer's disscusion board(link to ITT's or a new one) to help newcomers to find solutions to difficulty and ask for help.
  4. All docs in a catalog with good classification for look up.
  5. Maemo's roadmap and history, technical news and announcement about maemo.
  6. Maemo app gallery and entry to experienced and recently active developers' tech blogs.