NavigationUsability

Differences between revisions 1 and 10 (spanning 9 versions)
⇤ ← Revision 1 as of 2011-02-20 15:09:32 →
Size: 2499
Editor: 24
Comment:
← Revision 10 as of 2011-02-20 22:44:46 → ⇥
Size: 1967
Editor: ip5456cf16
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
 * '''Contributors''':
 * '''Packages affected''':		  * '''Contributors''': [[LaunchpadHome:mhall119]], [[LaunchpadHome:chrisjohnston]], [[LaunchpadHome:ronnie.vd.c]]
 * '''Sites affected''': http://loco.ubuntu.com
Line 14: Line 14:
This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.) == Rationale ==
Line 16: Line 16:
It is mandatory.

== Rationale ==		 Consistent UIs are intuitive UIs.
Line 24: Line 22:
== Design == == Design Rules ==
Line 26: Line 24:
You can have subsections that better describe specific parts of the issue.  * Only links to pages on LD should be navigation links
  * No external links
  * No links to feeds (rss/ical/etc)
 * Sub-nav links must be relevant to the page contents
 * Action links (those that affect page content) should be in-page.

=== Proposed Rules ===

 * "Add" action links should be above the list or table they will add to

=== Needed Rules ===

 * Where should Edit/Delete/Copy links be placed?
 * Where should feed links be placed?
 * Should in-page action links be short text, icons, or both?
 * How should external links be styled to indicate they are external?
 * No sub-nav on main page
Line 30: Line 44:
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:  * Separate search and sub-nav as on ubuntu.com to add the ability to remove the sub-nav on main page.
Line 34: Line 48:
Should cover changes required to the UI, or specific UI that is required to implement this  * New "top-nav" section above "main-nav" for login/logout and current user links
 * Separate sub-nav and search areas.


=== Sub-menu ===
'''Teams''': My Teams | Approved Teams | All Teams | Join a Team | Create a Team (first 3 views (from less to much) and then 2 informative pages about changing team membership)
Line 38: Line 57:
Code changes should include an overview of what needs to change, and in some cases even the specific details.
Line 42: Line 59:
Include:
 * data migration, if any
 * redirects from old URLs to new ones, if any
 * how users will be pointed to the new way of doing things, if necessary.		 Should be none.
Line 49: Line 63:
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

This need not be added or completed until the specification is nearing beta.
Line 55: Line 65:
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

== BoF agenda and discussion ==

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.		 == Comments ==

Summary

The navigation between the pages is not very usable at the moment. For example: It is hard to go to your own team page. Also the sub-navigation is very inconsistent and changes on every page. There is no logic!

Release Note

Rationale

Consistent UIs are intuitive UIs.

User stories

Assumptions

Design Rules

  • Only links to pages on LD should be navigation links
    • No external links
    • No links to feeds (rss/ical/etc)
  • Sub-nav links must be relevant to the page contents
  • Action links (those that affect page content) should be in-page.

Proposed Rules

  • "Add" action links should be above the list or table they will add to

Needed Rules

  • Where should Edit/Delete/Copy links be placed?
  • Where should feed links be placed?
  • Should in-page action links be short text, icons, or both?
  • How should external links be styled to indicate they are external?
  • No sub-nav on main page

Implementation

  • Separate search and sub-nav as on ubuntu.com to add the ability to remove the sub-nav on main page.

UI Changes

  • New "top-nav" section above "main-nav" for login/logout and current user links
  • Separate sub-nav and search areas.

Teams: My Teams | Approved Teams | All Teams | Join a Team | Create a Team (first 3 views (from less to much) and then 2 informative pages about changing team membership)

Code Changes

Migration

Should be none.

Test/Demo Plan

Unresolved issues

Comments

CategorySpec

LoCoTeamPortal/NavigationUsability (last edited 2011-11-12 01:57:44 by ip72-196-101-83)