Michelle Olson wrote: > Martin Walsh wrote: >> >>> >>> [mo-1] I noticed that if I login, I don't have a 'Repositories' link >>> in the left-navigation. But, after I click on one of the repo links, >>> the Repositories left-nav link appears. It seems like it should >>> always appear in the left-nav, even at first login. Also, if I click >>> the Project, Leader or Operations links after viewing a repo, the >>> Repositories link disappears from the left-nav view. This requires me >>> to learn that I have to click Project first, then choose from the >>> table on that page to access a repo. It would be easier to use if >>> there was always a link to Repositories in the left-nav. >>> >>> I'd suggest either naming the Project link to Project Repositories, >>> to match the the page name. Or, separate out a new page for the >>> Repositories table. So, when you click Project you see a page called >>> Project with just the name and description. And when you click >>> Repositories, you see a page called Repositories with the table. >> >> I am just thinking further about this point. The reason that their is >> no repositories link is because repositories are contained within a >> project. The project page will be the entry point of the application, >> when it is deployed live. Therefore the user will have direct access >> to a repository. Is this not better than having to click another link >> to view the repositories? > > They will only have direct access to the repos from the main Project > page, correct? So, from any other page on the Project they will need to > click the Project page to get to the repos links, which isn't intuitive > because the link is called Project XYZ, not Repositories. It is better > to have a separate, accurately named page with a navigation link than to > only have the links to repositories on the main project page. If they > find a Repository by way of a direct link and then later can't find a > link called 'Repository' in the navigation, they'll feel lost and > frustrated. >
OK, so how about we have a Project link, containing the project description etc, and the table of repositories like it is now. But also have a repositories link that just shows the table of repositories. e.g. Project - Leaders - Operations - Repositories (This is just the table of repos) - Repository (This is a repo that has been selected. Note this is always there now. Although the naming could be confusing!) Do you think this could be acceptable? As there would effectivly be the shortcut directly from the project page, but also a specific 'repositories' page. >> >> You also mention that the links should be the same name as the page >> headers. e.g. 'Leaders' should have a title & header of 'Leaders' not >> 'Project Leaders' The reason I put it as 'Project Leaders' is because >> the leaders link is a child link of Project. Do you think this will >> be a problem? > > Yes, it is confusing to click a link with one name and arrive at a page > with a different name. It seems trivial, but it is important for user > confidence because folks will spend an extra second, as soon as they see > the word Project, questioning whether they clicked the right link just > then, because their brain is expecting to see the word Leaders. > > Folks don't think about hierarchy and parent/child page relationships as > they navigate our site, they find a link that seems like what they need > and if they click it and get something called by a different name, they > perceive a disconnect and give up, or best case, send us mail about it. > OK I will update the names, and see how that looks. Martin
