Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sub nav updates: #14751

Merged
merged 4 commits into from
Jul 10, 2024
Merged

Sub nav updates: #14751

merged 4 commits into from
Jul 10, 2024

Conversation

1. Update /firefox to have consistent sub navs
2. Remove and re-order links on /firefox/more page
@wen-2018 wen-2018 added Frontend HTML, CSS, JS... client side stuff Needs Review Awaiting code review Review: S Code review time: 30 mins to 1 hour P2 Second level priority - Should have labels Jun 28, 2024
Copy link
Contributor

@reemhamz reemhamz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good job getting this done, you've done it pretty smoothly!
I just have a couple of questions regarding some files, and I think we should push this to a demo URL so Adria could have a look before we merge. I can take care of that while you're on PTO 👍🏼 I'll approve once some changes are done and Adria gives us the go-ahead

be-bold-and = Be bold and courageous when choosing which browser is right for you.
comparing-firefox-edge = Comparing { -brand-name-firefox-browser } with { -brand-name-microsoft } { -brand-name-edge }
youll-never-guess = You’ll never guess which browser has the edge when it comes to speed and features..
we-compare-firefox-v2 = We compare { -brand-name-firefox } with Chrome, Edge, Safari, Opera and Brave to help you make your decision
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This string can be removed since it's not being used anywhere

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: Should we also be adding the subnav to this page?

Copy link
Contributor

@janbrasna janbrasna Jul 2, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The subnav is also missing in these places: (where it also often links… and getting back from there is a pita…)

  • firefox/features (and all features subpages too)
  • firefox/browsers/compare (there the actual comparisons then have their own submenu)
  • firefox/faq has its own submenu that'd be worth updating with this too
  • firefox/browsers/what-is-a-browser and firefox/browsers/browser-history then kinda reuse the faq submenu but again in a way the IA for browsing back and forth doesn't work, it all leads deeper or away, to isolated silos of pages that don't offer a good hierarchy how to navigate them, and eventually return someplace else. So including these in the subnav overhaul would be awesome 🚀

BTW the "FAQ" page could itself be a good addition to the subnav, as it's not linked from anywhere visible?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OTOH there's one tiny issue now introduced with the default firefox subnav being also used for firefox/enterprise (which previously was on the beta/developer subnav) — the actual "firefox/enterprise" page is not part of this subnav here, therefore you can't get to it via navigation, and can't see the page bolded (aria current page role) when you're there, as it's not in the subnav at all.

I don't think the previous enterprise grouping with beta, dev, mobile beta & TestFlight pages in one subnav was too bad, esp. that the IA in footer also groups ESR with dev and other channels so at least that felt consistent. I never saw the brief so this might have been decided already, but if there's still some undefined leeway in possibility to better group the other channels together, this might be a good opportunity to fix up also their distinct submenu (which, like the issue being tamed here, has the items all over the place when navigating around), so that one could also undergo a little cleanup, making all the items for pages as:

  1. https://www.mozilla.org/firefox/enterprise/
  2. https://www.mozilla.org/firefox/developer/
  3. https://www.mozilla.org/firefox/channel/desktop/
  4. https://www.mozilla.org/firefox/channel/android/
  5. https://www.mozilla.org/firefox/channel/ios/

one neat consistent submenu for channels.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @janbrasna -- as usual, your findings are always super impactful to our decision-making‼️
I brought up the fact that the subnav should be on the firefox/browsers/compare and firefox/features pages and the team agreed and Wen has updated that part.

However, would you mind explaining why the firefox/faq and its connected page in this subnav update? I think it would be worthwhile making new subnavs for these pages rather than use the one that was created in this code update.

Regarding the firefox/enterprise page, alongside its old subnav + its connected pages, I brought this up with the SEO manager and will see what they say 👍🏼 as I think it would be worth it to have a discussion/see the reasoning behind these pages.

Copy link
Contributor

@janbrasna janbrasna Jul 9, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh I should have separated out what's probably worth taking care of with this changeset and is actionable, from just thinking out loud about all the interconnected content silos with their own local subnavs that I wanted to actually take a look at improving someday, as I regularly get lost in the IA;)

I will explain it better in an issue once I do a little bit of experimenting to see what would help, translating it into some form of drawing mapping out the IA compared to the local navigation content provided. But just to quickly follow up:

  • The Enterprise vs. channels is a tricky one as Enterprise is one of the product options for /firefox, but is not in the nav there; it was always grouped in the navigation (=see footer) together with channels. But it's good to have more ways of organising the content to cater to different mental models of where to look for the pages anyways.
  • FAQ and the pages its submenu link to have inconsistent subnavs each so trying to navigate from/around FAQ via subnav you're being taken to places quite randomly;) It's now removed from nav so it's slightly less of an issue, but basically why I mentioned it was that its individual submenus, linking between /faq and /browsers/* seo pages could use a similar tidying up like this one day, to a "stable" shared subnav instead of a handful of oneoffs;)

In an ideal world I would love a breadcrumb+subnav combo;) using the left part for hierarchy, and the right corner for topic-level siblings (think "Firefox › Mobile › Focus" left ~ "Desktop Mobile Feature Compare FAQ" right etc.) to explain the local navigation options a bit more.

I'm basically holding off for the potential nav/masthead redesign before looking into more nav issues myself, so that's just what's been on my mind when it came to nav improvements in general…

But none of that is relevant to this change, so sorry for mixing it up all in one place.

(I'm just super excited to see this happening, so I might have gotten carried away a bit too much…;))

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spoke to SEO manager, and she mentioned that since the Enterprise page is linked directly in the products page, that it would be worthwhile in the meantime to also have it share the new Firefox subnav. In the future, if we decide to move the Enterprise page from the main products page, then we'll have it share a subnav with the developer page group and tidy them up. Since these subnav changes are incremental and are currently being worked on, we'll hopefully be seeing more changes come soon

@reemhamz reemhamz removed the Needs Review Awaiting code review label Jul 2, 2024
Copy link

codecov bot commented Jul 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.18%. Comparing base (decefb0) to head (bf3770e).
Report is 21 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #14751      +/-   ##
==========================================
- Coverage   77.21%   77.18%   -0.03%     
==========================================
  Files         159      159              
  Lines        8219     8239      +20     
==========================================
+ Hits         6346     6359      +13     
- Misses       1873     1880       +7     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@reemhamz reemhamz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🍪🥛 r+!

@reemhamz reemhamz merged commit 7babc30 into mozilla:main Jul 10, 2024
7 checks passed
@wen-2018 wen-2018 deleted the sub-nav-update branch July 11, 2024 13:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Frontend HTML, CSS, JS... client side stuff P2 Second level priority - Should have Review: S Code review time: 30 mins to 1 hour
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update secondary nav in fx category
3 participants