launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #00208
Re: RFC NavigationMenu primer
On Thu, 2009-08-06 at 11:52 -0500, Edwin Grubbs wrote:
> On Thu, Aug 6, 2009 at 11:27 AM, Curtis Hovey<curtis.hovey@xxxxxxxxxxxxx> wrote:
...
> > Working with two menus
> > ----------------------
> >
> > There are a few cases where a page may need two menus. One for actions
> > that change an object that are not possible to move into the main content,
> > the other for pages related to the content of the page. NavigationMenus
> > can be created for content objects and views.
>
> What is the deciding factor for whether an action can be placed in the
> main content? Is the Related Pages menu supposed to be in the main
> content or the sidebar? Can you provide an example of the contents of
> the two menus for an overview page, an edit page, and a bugs page for
> a single object?
The action menu is for actions that change the context object. Many
objects do have content to place a link near. Common examples in the 2.0
UI is Change details and Administer. Recent examples are Change password
and Change visibility (pubic/private). Since these links modify the
context object, they will probably only appear on the context's index
page. Something is wrong if:
* The menu shows up on many pages
* The menu has more than 3 links (experience may change this
number)
* The link does not modify the context
Related pages are in the content, probably near the bottom of the page.
They help the user who has read the content to find related content.
Since search all launchpad.net will be in the footer, the user will have
two ways of finding related content. The product edit pages have links
to the related edit pages: branding, people, and some users will also
see review and administer. The series page will have links to all series
and all milestones. A PPA page might have links to see the other ppas
--
__Curtis C. Hovey_________
http://launchpad.net/
Attachment:
signature.asc
Description: This is a digitally signed message part
Follow ups
References