Glossary section is not reachable directly from anywhere

[OnkarRuikar]

The glossary section is reachable only from "See also" links. There needs to be a more explicit link to the glossary section.

a. In the 'References' submenu:

b. suggest more places...

What are your views on this?
Is this location ok? Please suggest other locations that you think would be suitable.

[OnkarRuikar]

Following are the comments from the old discussion.
Dipika:
I recently proposed internally to add a "?" help menu button at the bottom right corner on the website. The help menu could serve as the home for glossary, contribution guide, and our writing guidelines.

On click, it might look like this:

screenshot of proposed help button on MDN

---

Will:
As for the glossary, I don't think it's a big problem that it's not linked. The glossary exists so we have a place to define things in other pages. IMO it's not a particularly big use case for people to decide to browse a glossary. But if we want it, then (3) is reasonable, although I would make the explanation text something like "Glossary of web development terms".

---

Estelle:
Suggestion: Add "glossary" to the reference drop down, as per Onkar's screen shot.
Explanation: When I used to look for a link to the glossary, I would always open the references drop-down, as that is where intuitively I felt it would be. Now to get to the glossary, I use the search. I enter "RGB" in the search as it's just 3 characters and I know the first or second result is the glossary term. I think a link from the reference drop-down is more intuitive ;)

[OnkarRuikar]

In the community meeting on 27th March following things have been discussed:
a. Dipika gave 👍 to adding under references menu.
c. Mozilla team to get back later and convey the decision here.

[dipikabh]

Hi @OnkarRuikar, we discussed this topic internally. We're leaning towards not adding the Glossary option to the References menu at this time. However, to better understand the existing situation and propose potential improvements, this is now an action item with our UX designer, Anuja, to study how folks use the Glossary on MDN as well as research how similar resources are presented and used on other technical documentation websites. We're hoping this research will help us adopt a more informed strategy/solution. Happy to share that this project is now part of the Q3 goals for Anuja.

As always, we really appreciate you highlighting such concerns and sharing your proposals for improving MDN and user experience.

[estelle]

Per Mozilla Discord:
"we're aware the site search needs some work, but that won't be happening until post-platform work this year. For the Glossary - we won't be linking to it in the top nav - but are looking into the footer and/or other places"