> 27 nov. 2020 08:44 Lassi Kortela <xxxxxx@lassi.io> wrote:
>
>
>> I've added a simple horizontal menu to show what it would look like.  I skipped the hamburger menu, instead compacting the menu into two columns when the screen is too narrow for a single strip.  I haven't removed any of the list content yet, though.  This is just to get a feel for the idea.
> It looks great!
>
> But as with OCaml.org, the same items are shown below on the page. Is there a consensus among usability people that we should call attention to different things at the top of the page as opposed to front and center?

The consensus among usability people is that we don't know anything until we have tested it on real users, but that is not really possible in this case. My educated guess, however, is that items at the top of the page are viewed as being more primary (static) navigation, while items lower down are expected to be more fluid and interest-piquing.

A menu at the top of the page is also expected to persist on all the pages that are referenced in the menu, and probably on all their subpages. What counts as a subpage is tricky, but the Haskell documentation and download pages have some examples. I'm not saying that this is good or bad design, but it is a source of inspiration.

Haskell's documentation page is, as far as I can see, a collection of links to external documentation resources, which means that the menu looks the same on the front page and the documentation page, but when you go to a resource, the look changes completely (for obvious reasons). Maybe the links on that page could be more clearly indicating that they are external, otherwise it is not very suprising for the user.

Haskell's download page, on the other hand, has subpages. When I click the "Linux" link, the menu stays the same. For some reason, clicking "OS X" takes you to a different type of page, still with almost the same look and menu, but the menu now inexplicably has a "News" item.

/Magnus