Project Zero website UX Recommendations

1
Project Zero website - UX Recommendations

• Sheena Lewis
• May 9, 2008

2
Outline

• These slides identify possible opportunities for
  improving consumability of the website content
• Issues are prioritized as followed
• Priority 1 High priority issue Large impact on
  user experience (may result in some users
  experiencing significant difficulty using site)
• Priority 2 Medium priority issue
• Priority 3 Low priority issue Small impact on
  user experience

• Priority indicated in parentheses at the
  beginning of each issue, as in the priority 3
  issue seen below

• Priority 1 issues highlighted with pink
  background, as seen below

(3) These separators are difficult to see
consider using a darker color.
(1) Lots of empty white space here. Consider
rearranging page elements for a better fit.
3
(2) There should be one home that is not a link
since this is the homepage.
(2) Too much white space.
(1) There should be dates on each headline under
the Spotlights.
(1) Bug in feed wrt quotes
(2) There should be a place for users to see new
articles that have rolled off the Spotlight list.
more
(1)There is no indication if you mouse over the
download widget that additional information will
be displayed. Also, the white on white isnt
visible while the widget in loading (which takes
approx. 11 sec if not cached).
4
(3) Make the instructions more personal by
removing the users
(2) Make this a link to the section.
(1) Correct this link by making it link to the
Getting Started Guide landing page (an expected
behavior).
(1) The IBM JDK information should be in the Java
section
(2) Update the Sun link to point to Java 1.6
instead of 5 since it is being phased out.
5
(3) Clarify the download links better than Java
and PHP (keeping in mind, people dont really
read).
6
(1) User Profile is not the correct breadcrumbs
for the final download page.
(1) Add links on the final download page that
goes back to the installation instructions and
other information
(2) Remove unnecessary white space in the footer
7
(1) There should be a link that allows users to
easily switch back to the CLI or PHP download.
Also, since we do not plan to continue building
on the Eclipse plugin, we should strongly
encourage users to use the CLI.
(1) Is this correct in that it is still under
development? If its attached to M6 then we should
let users know that.
8
(1) There should be a link that suggests to users
that they should use the CLI version and include
a link that allows them to switch from PHP to the
Java version.
(1) On the PHP download page, the header says
that it is for configuring the java/groovy plugin.
(3) Distinguish header title on from the table.
(1) The latest version is M6 and not the still
being built.. We can change the text to say M6,
add an asterisk to explain that we are taking a
new direction and encourage them to use the CLI
or the WebIDE
(1) These are not the complete instructions.
Provide a link to the Documentation with the
complete install instructions or complete the
instructions here.
9
(2) Include dates (times are not necessary) for
the blog posts.
(2) Include dates (times are not necessary) for
the forum topics to give users context.
(2) Remove unnecessary white space in the footer
10
(3) There should be more places to access the
FAQs.
11
(2) There are no links to go back to the top of
the page.
(2) This should link to the direct answer in the
Developers guide.
(2) This should link to the direct answer in the
Developers guide.
12
(2) The sub headers (bold words) should have
separators (e.g. -, )
(3) see the Milestones Documentation is not
clear where it is. Point that is on the right
hand side. Keep in mind that users dont read.
(2) The heading Developer should be replaced
with words that align with the other headers.
(2) Include a link to all the full list of
samples.
Remove unnecessary white space in the footer
13
(1) Change the breadcrumb to reflect true path,
which is HomegtDocumentationgtDevelopers Guide.
(2) Sometimes it is referred to as Developers
Guide but here it is Developer Guide. The
title should be consistent.
(1) These topics should be condensed into
information that is more user friendly. A page
like this assumes that users read, which is not
the case. Typical users skim and 11 pages is too
much to skim. This page should be broken into
smaller topics that users can then explore for
more information. A first time user coming to
this page would be overwhelmed with information.
14
(3) The URL for the documentation would be easier
for users to remember if it was in the
documentation PATH instead of the download path.
(3) The search box is not consistent with the PZ
pages.
(1) Change the breadcrumb to reflect true path,
which is HomegtDocumentationgtGetting Started Guide.
(2) Remove extra black space. By making the
footer a set height.
15
(1) The breadcrumb section at the top of the
documentation must be easy to use and navigate.
Heuristic evaluations and usability tests suggest
this is not the case. Users typically go back to
the documentation landing page to get to another
(or previous) section in the doc rather than
trying to use the navigation. This can and should
be corrected through better design.
(3) Considering that we are not updating Eclipse,
we should continuously encourage users to use the
CLI version or the new WebIDE. This is a good
page to link to the Zero download page.
16
(1) There should be a header with the page name
in order to be consistent with all PZ pages.
(3) Change the PZ logo on the forums to use the
same font type that is on the PZ main pages.
(2) The signup and login link location should be
consistent on each page.
(3) Make the menu words consistent with PZ main
pages (e.g. same font).
(3) Make the menu behavior consistent with the
main pages (e.g. mouse over behavior)
17
(3) Styles should be consistent with the PZ main
site.
18
(3) Currently, there is no way for users to
easily tell how many blogs we have written and
where they are in the list.
(2) Replace the header font size to be consistent
with the PZ main pages.
(3) Font sizes should be consistent with the PZ
main site.