(Created page with "= Developer.MeeGo.Com Design Overview = During the first review of the developer.meego.com site there were several comments about the design. This page gives some background on…") |
(→Overall goals) |
||
| Line 5: | Line 5: | ||
== Overall goals == | == Overall goals == | ||
| - | One of the observations made by an educational consultant regarding the developer.android.com site was that it lacks signposts, to guide a user through the site. So one goal of developer.meego.com was to provide a user with contextual information to help them orientate within the site. A crucial aspect of this is to reduce the number of links presented to a user at one time (the classic usability rule of 7+-2 forms some guidance here). Another powerful | + | One of the observations made by an educational consultant regarding the developer.android.com site was that it lacks signposts, to guide a user through the site. So one goal of developer.meego.com was to provide a user with contextual information to help them orientate within the site. A crucial aspect of this is to reduce the number of links presented to a user at one time (the classic usability rule of 7+-2 forms some guidance here) and to provide text to explain the relevancy of the link. The header images+text in each of sections explains what the section is for. Another powerful for helping beginners is to emphasize the key links for a begineer (the accordion links in the home page does this). |
A second goal was to allow an experience user to access the information they want quickly and easily. This could require placing a large number of links on the home page, or (as implemented) using a 2 level navigation, so that an experienced user can navigate to the API references with one click. One crucial aspect for developers is the API reference section, which (although currently missing a search function) has a nice floating menu bar for consistent navigation of the documentation. | A second goal was to allow an experience user to access the information they want quickly and easily. This could require placing a large number of links on the home page, or (as implemented) using a 2 level navigation, so that an experienced user can navigate to the API references with one click. One crucial aspect for developers is the API reference section, which (although currently missing a search function) has a nice floating menu bar for consistent navigation of the documentation. | ||
During the first review of the developer.meego.com site there were several comments about the design. This page gives some background on the site design, or why it looks like it does.
One of the observations made by an educational consultant regarding the developer.android.com site was that it lacks signposts, to guide a user through the site. So one goal of developer.meego.com was to provide a user with contextual information to help them orientate within the site. A crucial aspect of this is to reduce the number of links presented to a user at one time (the classic usability rule of 7+-2 forms some guidance here) and to provide text to explain the relevancy of the link. The header images+text in each of sections explains what the section is for. Another powerful for helping beginners is to emphasize the key links for a begineer (the accordion links in the home page does this).
A second goal was to allow an experience user to access the information they want quickly and easily. This could require placing a large number of links on the home page, or (as implemented) using a 2 level navigation, so that an experienced user can navigate to the API references with one click. One crucial aspect for developers is the API reference section, which (although currently missing a search function) has a nice floating menu bar for consistent navigation of the documentation.
A third goal has been to make the site "MeeGo" branded. This dictates the colors, fonts, and logos used inside the site. The result is a site that looks similar to MeeGo.Com, but has the additional features (mentioned above). Because the site úses similar colors to MeeGo.Com and has a fixed width layout it looks similar, just as bugs.meego.com looks similar to the MeeGo.Com site.
The biggest change has been to re-orient the relationship of the site to other sites in the MeeGo Application Development ecosystem. The major functionality change has been to allow external guides, and other content to be linked easily from developer.meego.com.
This change allows the site to be configured as a full-fledged standalone site, or as a MeeGo application developer dashboard, where other content on the web is selected and linked.