Website feedback

[saloynton]

A placeholder for the feeback for the OMERO web site.
This information has been moved off the trac page.

The feedback is in relation to the upcoming work with the OMERO web site and documentation work. 
See User Story #3592

The following is a conversation with a scientist about how the web site might benefit 
in the layout and the navigation of the site. The key requirement highlighted was 
to have at least two key pathways of navigation on the web site front page. 
The request from the perspective of a scientist was that they wish to be able 
to access and download the software and then if necessary find any software 
documentation with minimal ease. Any cross over of information between the 
scientists and information for the external developers/expert users make 
the process for finding information more complex than necessary. 

This highlights the need to retain a scientist’s attention if they are 
getting lost or confused then they may leave the web site.

(Some of this point relates to preserving the 3 clicks rule to get to 
important information. A prototype/site map of the web site might help demonstrate this.)

The specific example of the Mozilla web site ( http://www.mozilla.org/) was discussed 
in how it both serves a very large user community and large development community. 
The site has two distinct pathways to accommodate for this. The users are directed 
to the recent downloads for the browser and the wide set of extension that the 
web browser now offers. The developers are accommodated for in the Mozilla community pages.

(See the following link for an initial set of possible web site navigation ideas 
the work would require further investigation to build a collection of ideas. 
http://www.webdesignerwall.com/trends/30-examples-of-attractive-nav/ )

The Mozilla Firefox browser specifically was also discussed to be a 
good example for informing users of the browser updates. There 
was an identification of the need to provide further details of 
the OMERO updates between the major releases to the local users. 
This was raised as a problem as the scientists are content with the
 stability of the software and so the perception of the minor  
updates can be viewed as a disruption to this. Any additional 
information that may help support the information behind incremental
release's updates, so that the users are aware of the progression
of the software and OMERO team.

It was also mentioned that a scientist had not received the upgrade
emails for OMERO is there a way I may add any outstanding users 
that I speak to the update list? 

[jburel]

on-going doc re-organization. Closing