Update top nav

[ElenaFdR]

The current top nav on publiccode.net links to our other repos, but doesn't provide any context to suggest you're navigating to a separate website.

Separately, one convention for websites that represent a Github repo is to include a link to the Github repo in the top right corner of the website (often represented by the Octocat).

We propose the following top nav instead, which includes our most important links, most of which are to pages within this repo.

[angelplasma]

Proposed nav links:
Stewardship - Media - Join Us - Project Resources - Who We Are - Github (as logo)

[ElenaFdR]

In a previous iteration of the top nav, we also thought it might be nice to link to this, but it's not as important as the other links and certainly not a blocker.

• Media (projects.publiccode.net PR 16)

[angelplasma]

Updated nav suggestion attached, based on the following factors:

1. Focuses on most essential info and actions for both new and familiar audiences.
2. Previous comp was future-facing, and incorporated future additions to site (e.g. Media)
3. Elena and I feel "Resources" is a succinct encapsulation of what is contained on projects.publiccode.net, which seems to correspond to sentiments expressed here: Proposal: definition of a project projects#10

[Ainali]

Is this top nav configurable or will it be the same on About, Blog and Standard?

[angelplasma]

@Ainali Would love to hear your thoughts on desirable configurations.

Our thought was to update the universal nav to be more useful now, and then explore context-specific modularity.

[Ainali]

I don't have any ideas, but if they are the same, wouldn't this still be the case?

The current top nav on publiccode.net links to our other repos, but doesn't provide any context to suggest you're navigating to a separate website.

For example, from the blog all the top nav bar links would still go to another website. So even though we improve the links and fix the GitHub link we might still have one problem to solve.

[angelplasma]

Very true that links to other repos would continue to lack aforementioned context.

However—and I say this not yet having tested my assumptions + talked to enough of the team—I am not so sure the differences between repos/subdomains are currently so meaningful to most users that they need special prefacing...

Would love to hear more on the need for clear repo dividers—this is certainly an area of exploration for the upcoming site architecture conversation.

[Ainali]

I think you are right there, it might not be a very meaningful division for users as such. What could matter though, is that once you leave the blog for the website, it is not obvious how to navigate back.