also, if you are having some issues with terms for the interface for user guidance and support, there is a Names of user interface elements in Discourse and Discourse New User Guide
āHamburgerā is developer jargon. The customer-facing name of an icon menu is whatever its tooltip says, but in this case, thatās just āmenu,ā so thereās another UI / UX issue.
The word āhamburgerā does not appear in the Discourse New User Guide, which is good.
According to whom? You seem to strongly think that, but I donāt know where you get this idea from.
IMHO, it is a broadly accepted term, including among users, as @Lilly already suggested above.
Please do a few web searches around the term, and youāll see for yourself.
You can have a look at its wikipedia page too: Hamburger button - Wikipedia
If you prefer, you can call it ātriple barā button/menu.
I did a very scientific study consisting of interviewing subjects in two age cohorts (Gen X, Gen Z)[1] Zero percent of those interviewees had heard of the term. When shown an example, the Gen Z cohort responded with āoh, that makes senseā, while the Gen X group found the whole thing even more confusing.
-
Sample size of one per group. Specifically, my wife and daughter. ā©ļø
I appreciated the heads up. The new menu isnāt quite to my taste yet (I appreciated the chunkier look of its predecessor, preferring the two column approach) but definitely has some useful functionality and I appreciate the implementation gets you off the widget API.
Except imho, the slightly clunky ādrop down within a drop-downā which covers the other options instead of expanding. Not a fan. Is there a slightly slicker way to achieve a similar thing?
Btw Discourse without the Hamburger would be Paris without the Eiffel tower . I think itās ok to have some domain specific terms and a bit of personality.
If you say so. But not in Finland. And all of my US-friends who donāt work in this area use term hamburger.
One problem with the term āhamburger menuā is that sometimes it mutates into what I might call āthree dots menuā. Itās not a good term, where fashion changes, and people from different age cohorts have different cultural references. Try helping out some people in their 70s and 80s.
Good or bad, itās there. And that is one reason why familiar solutions should never change without really good reasons ā three dots at same place where practically every site uses hamburger is not such reason ā it would be a change because of change itself.
Situation would be totally different if layout and ways how to use sites would change drastically.
Butā¦ why are we discussing if name hamburger is valid for one menu? Iām bored and procastinating, but what is excuse for all others or you
Do you have an estimated date for this? Even āat some point after 30th juneā or something similar would be a useful estimate to plan around.
Documentation should refer to icon menus by their tooltips. E.g. the magnifying glass is Search. To make things clear, you can include the dingbat, e.g. ā (Search)ā.
The tooltip for Discourseās ā” menu is just āmenu,ā so you could refer to it as āā” (menu)ā.
Iām a tech writer and part of my job is keeping developer jargon out of customer-facing docs. āHamburgerā for ā” and ākebabā for ā® are jargon.
In a recent change, we removed the āmoreā link from the dropdown menu and have all the links displayed by default.
@craigconstantine @mattdm Weāve recently worked on a solution that adds sidebar compatibility for the category icons theme such that the custom category icons set will be used in the dropdown menu when a category is displayed.
In the long run though, we are discussing internally to make custom category and tag icons a first class Discourse feature. Once that happens, the category icons and tag icons theme components will no longer be required.
Great, thanks!!
Why arenāt the Categories title and the Tag title a link to the relevant pages? That seems like a missed opportunity. If you donāt configure any Tags there is no way to get to the Tags page. Thatās not good!
i suspect itās because in side-bar mode, those headers collapse and expand when clicked. iāve been thinking about this myself and i would prefer if the headers linked to those pages (categories / tags) and arrows collapse/ expand, but that wouldnāt make sense for the other sidebar section headers (although i suppose Community could just go to the userās default home page). i guess things can be programmed to be different in hamburger drop down mode, and it does make sense to have those sections linked there.
iāve also thought that it would a cool option to let users choose between side-bar or drop down mode in their preferences.
of course, good point!
this post is outdated now and there has since been an update - the review link is not dropping into More section the way it did before (or perhaps depending on where it is placed in the customization modal?). i like this and so do my mods. thank you team.
heh i see this recent fix too:
@here Do note that weāve made some changes to the plan here based on feedback which weāve received. Instead of dropping the legacy
navigation menu in the upcoming release, we will only be removing it in the release after. However, support for the legacy
navigation menu will be ceased from the next release onwards.
Just to (hopefully) clarify a bit further, since ānext releaseā could mean a few different things, and people can update their software any time, including between releases.
We had been planning to remove this before the v3.1 release that weāre planning to make towards the end of this month (July 2023), but now we plan to remove the legacy option shortly thereafter, leading up to one of the first beta releases for v3.2. This could happen as early as sometime in August.