Re: Defining products list and pages
On Wed, 2006-08-09 at 13:56 +0200, Gergely Nagy wrote: On Wed, 2006-08-09 at 12:58 +0200, Claus Schwarm wrote: Maybe it's useful to remember that the products.html page was in the 'About' section: The navigation of the product pages needs some serious thought unless we want to go deeper than a 3 level navigation or make 'Products' a top-level item. When I was writing my BSc thesis on accessible CMSs, I did some research on navigation. According to [1] the optimal size for a menu is about 5-7 entries, and that they are preferably shallow, so avoid deep hierarchies. This is indeed pretty standard usability advice, although as usual with this sort of thing it's not completely cut and dried. Some more useful analysis/references here: http://www.humanfactors.com/downloads/apr03.asp . Cheeri, Calum. -- CALUM BENSON, Usability Engineer Sun Microsystems Ireland mailto:[EMAIL PROTECTED]Java Desktop System Group http://ie.sun.com +353 1 819 9771 Any opinions are personal and not necessarily those of Sun Microsystems -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: Defining products list and pages
GnomeWeb/SoftwareMap is now http://live.gnome.org/GnomeWeb/GnomeProducts I've tried to summarize there the agreements, the planning work needs to concentrate now on the draft sections and the update of deletion of the Needs update section. Hopefully this is something Simon can do without much surprises, following the lines of his last email. El dt 08 de 08 del 2006 a les 18:11 +0200, en/na Simon Rozet va escriure: Which contents on this page ? - To start with see the work done by Claus at http://gnome-apps.berlios.de/ , also what he attached at http://mail.gnome.org/archives/marketing-list/2006-August/msg00046.html Claus, if I'm missing other drafts you have provided about product pages please let us know. - A part with structured informations : website, maintainer, ... This part can be machine-generated. Going into details, select the DOAP properties to be used in the product pages - http://www-128.ibm.com/developerworks/xml/library/x-osproj3/ - A free-part wish feature the application in a cool way with screenshots. Right. I think that even this could be shared with the projects via DOAP / syndication. Think that now most of them have websites in just one language, very few have 2 or 3. We are going to translate the product pages in n supported languages. Imagine they could offer these summary pages in their own website with a marketing approach and in several languages, with no extra effort. Example : http://ploum.frimouvy.org/?2006/03/15/100-why-you-should-try-epiphany-as-your-default-browser-with-gnome-214 Well, too long and detailed. A page like this would be useful in a Epiphany in a nutshell page in the Epiphany project page, I think. Do you agree we go for something like a 20sec ad? - Auto-generated. - URL: http://www.gnome.org/desktop/products http://www.gnome.org/products is better. Specially if we aim to cover the 4 release suites, from which just 1 is desktop. Which apps ? I propose to start with a small list of clear candidates (Like gedit, rhythmbox, epiphany, ...) Let's apply the framework of the GNOME release suites proposed by Jeff. Going into details, define a draft list of product pages. IMO it is better to start with few but very well done. For the selection have in mind http://live.gnome.org/GnomeWeb/UseCases So... whit DOAPs, we can auto-generate (in several languages) Going into details, define how this will work. Marketing, developers and translators will be editing the same DOAP files? Where and how? Simon, thank you for your patience. You are about to reach the start of the implementation. :) -- Quim Gil /// http://desdeamericaconamor.org | http://guadec.org signature.asc Description: Això és una part d'un missatge, signada digitalment -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: Defining products list and pages
On Wed, 09 Aug 2006 11:46:02 +0200 Quim Gil [EMAIL PROTECTED] wrote: Claus, if I'm missing other drafts you have provided about product pages please let us know. No, I don't think so. Maybe it's useful to remember that the products.html page was in the 'About' section: The navigation of the product pages needs some serious thought unless we want to go deeper than a 3 level navigation or make 'Products' a top-level item. Theoretically, there could be other ways, too: For example, a feature section that changes content every day? I admit this is similar to the gnomefiles 'App-of-the-week' box but I like it. This may be possible even if the backend remains basically static; it would be sufficient if pages are re-generated every day, using a PHP or Python generator code (web coders are more familiar with templates than makefiles, in general, so this shouldn't be a major problem -- and smarty has full language support IIRC) Additionally, after reading Jeff's suggestion, again, and Joachim's navigation draft, we may need to remember that we probably have a top link for third-party developers and potential contribution coders. It's probably more appropriate to feature technical details about the developement platform (and maybe the embedded stuff) there -- instead of using the 'About GNOME' section which is probably more orienteded towards users and the general public. [snip] Example : http://ploum.frimouvy.org/?2006/03/15/100-why-you-should-try-epiphany-as-your-default-browser-with-gnome-214 If anybody wants to write something like the above (more text, less images, maybe), consider to sent it to the GNOME Journal! :-) Cheers, Claus -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: Defining products list and pages
On Wed, 2006-08-09 at 12:58 +0200, Claus Schwarm wrote: Maybe it's useful to remember that the products.html page was in the 'About' section: The navigation of the product pages needs some serious thought unless we want to go deeper than a 3 level navigation or make 'Products' a top-level item. When I was writing my BSc thesis on accessible CMSs, I did some research on navigation. According to [1] the optimal size for a menu is about 5-7 entries, and that they are preferably shallow, so avoid deep hierarchies. A completely filled 3 layer menu with 7 entries each provides for a whopping 343 pages! I'm sure there is also googleable info on this topic. [1] Stephan Lamprecht. Webdesign-Handbuch (2001, Carl Hanser Verlag) -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
