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

Task:Improving maemo.org

Revision as of 12:42, 1 July 2008

This article is continued discussion from the maemo.org brainstorm Please see the 100 Days agenda for more.

This task is in the list of maemo.org development proposals, please help planning and getting it ready for a sprint. Put a note on the talk page if you're interested in helping work on this task. Please see the talk page for discussion.

Content

• Website information does not suit the needs of newcomers: How to install or do xy on the IT? Where is recent information about OS2008? Is this page, which I am looking at, an outdated or a recent page on maemo.org? What resources are available for me (alias I am confused by unconnected information sources: gronmayer, internettablettalk, planet.maemo, official Nokia site, internettabletschool, maemo ...) Where is a detailed roadmap for Maemo? Is there an application wishlist for OS2008? Where can I give input/ideas as end-user?

All good points, agreed.--qgil 07:38, 2 June 2008 (UTC)

• planet-maemo in other languages: For me planet maemo is a very nice aggregation service. This should be available in other languages too. Maybe there should be two versions (per language) of planet maemo: one for developers and one for end users.

We can do multiple languages by creating a folder for each language and adding the proper feeds to those folders. There is also a possibility to display news based on what you have thumbed up and down in the past, but that would be something that can only be done after the planned server upgrade. --xfade 13:49, 2 June 2008 (UTC)

• I'd like to see something like library.gnome.org - searchable content, generated from latest documentation in packages where possible, and updated regularly. --dneary 10:39, 3 June 2008 (UTC)

Interesting. Currently the API documentation is published in a suboptimal way. If this is feasible to do with our current setting then I guess it would be really useful. Worth being a 100 Days proposal by its own.--qgil 10:33, 4 June 2008 (UTC)

Introduction

• Re-write and expand Introduction to better serve as a useful introduction for newcomers to the platform.
  • Intro section should include "Who is the maemo community?, What is the maemo platform? The maemo software architecture, How does maemo.org work? Quick start guide to develop on maemo software, and presentations".

The whole intro section should to be redesigned and turned into a proper starting point for new visitors. --xfade 13:49, 2 June 2008 (UTC)

Agreed, and I even got a volunteer in Nokia for the next sprint (Peter).--qgil 10:33, 4 June 2008 (UTC)

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)

Style and format

• Maemo.org can benefit from some face lifting - right now on 1280x1024 (this resolution seems to be very common to developers) only half of the real screen estate is used. With some loose block positioning both 800x480 and bigger resolutions can be supported. Maybe even specialized tablet finger-friendly look for those preferring it.

Agreed, we have a lot of size and font problems that need to be addressed. Some example stylesheets would be welcome though. --xfade 13:49, 2 June 2008 (UTC)

I'll see to that bundyo 20:41, 2 June 2008 (UTC)

Resolution seems fine to me at the moment, and it works fine on the tablet without requiring the extra effort of maintaining a separate tablet style. Perhaps reducing the min-width to not require horizontal scrolling with the tablet browser windowed would be useful, though. generalantilles 21:02, 29 May 2008 (UTC)

There won't be any extra effort on the resolution maintainment - this can be done with minor CSS modifications. As for the separate tablet style - this really requires extra effort and if done should be entirely optional. bundyo 21:26, 29 May 2008 (UTC)

• More relevant information displayed on front page, preferably customizable blocks like Netvibes and iGoogle. Since the content is gzipped, that won't be too harming to the traffic. Blocks can be optionally auto updated for those that like to keep their browser pages open (and if Prizm is ported - even in the tray). For instance, a "new bugs" section with voting on the fly will boost bugzilla usage.
• Make links more standardized. New users often expect links would be underlined, even subtly, or appear to be a button of some kind. Don't rely on hover effects because the tablet can't practically use them. See Wikipedia on 'Mystery Meat Navigation'

This is much less of an issue for a lot of people —generalantilles 19:49, 31 May 2008 (UTC)

Please stop expecting your advanced experience of new users. Read up on web accessibility, be inviting to the new users.--boxofsnoo 23:08, 31 May 2008 (UTC)

I really don't see the issue (and never particularly have with this much-abused "Mystery Meat" nonsense), and I don't think it has anything to do with my experience, wikipedia (your source) uses the exact same system for link identification. . . . Some specific examples would probably help your case. Anyway, this should probably be taken to the talk page. —generalantilles 23:20, 31 May 2008 (UTC)

• Format and style need to be unified across as much of the site as possible (excluding things like Garage and Bugzilla). Take, for instance Planet and News, two pages that should be very similar, if not the same. Perhaps take News' style and format and apply it to Planet (add the contributor's avatar to the upper right of each article? Much like slashdot does with their article category images.), as the News style seems to offer a cleaner look that better utilizes the available space.

There is a difference between News and Planet, because they both serve a different role. The planet aggregates every blog feed that is added. The News page only shows the news items that the community rates as being important/interesting. --xfade 08:00, 3 June 2008 (UTC)

Yes, but they should at least share common style, they're quite different right now. bundyo 09:40, 3 June 2008 (UTC)

• For the outliers like Garage and Bugzilla, at least the style should largely be unified with the main site—using the same fonts, same colors, etc.

OK to have a well integrated, efficient and nice-looking layout across maemo.org. Ok to discuss in detail in a page apart and ok to have a basic plan agreed in 100 Days. The execution will take longer, though.--qgil 07:38, 2 June 2008 (UTC)

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.