New Toolbar Roadmap: Path to Beta & Stable

Thank you @ldonelan! I've updated the links to use the pattern for issue numbers so the state gets pulled automatically.

More issues added to define the plan better.

Bumped 📌 Revert to default in navigation layout settings from the UI Active down to "Could Have" as a lower priority non-MVP item, after discussion on the weekly Admin UI call. @ckrina to follow up with @laurii about this feature as well to get some clarity around it. More details in the ticket.

Adding 📌 Decide strategy to customize or provide 1st level menu items' icons Active as a Stable Must Have.

@ckrina, I reorganized tickets based on our discussion. Let me know if this looks OK or if you'd like a different format.

Updating with completed, specially to get a sense of missing tasks for the beta release.

From looking at https://git.drupalcode.org/project/navigation/-/commit/17970de1ed6b4129d... it looks like there is not yet a caching strategy for the menu links in the navigation module.

The existing toolbar has a very developed caching system already, this was implemented in #1814932: Caching strategy for D8 toolbar → , #1137920-303: Fix toolbar on small screen sizes and redesign toolbar for desktop → and #1805054: Cache localized, access filtered, URL resolved, and rendered menu trees → and has not significantly changed since.

It was necessary to add this because rendering a full tree of admin menu links is very expensive both in terms of server-side processing (hundreds of milliseconds every request) and page weight (potentially hundreds of extra kb every request).

I think we need an issue to port this logic across from the existing toolbar.

Thanks @catch! I've created the issue to keep track of it 📌 Implement a caching strategy for the menu links Active and added it as stable blocker.

Moving 📌 [META] Implement the final design system Fixed to done, and removing 🌱 [PLAN] Accessibility review Active from beta blocker as the reviews have started. Any issue found will be added as Stable blocker if necessary.
Also adding 📌 Remove postcss-px-to-rem from Navigation Active as it'd be a really nice cleanup to have.

Added a few more issues.

Removing the Beta section since everything needed for beta has been done and we're about to launch beta 3.

I moved 🌱 [PLAN] Accessibility review Active to the Should have, and if any Accessibility bug found becomes an Stable blocker it'll be included into the "Must have" section.

Updated with new stable blockers and removed fixed issues.

Adding 📌 Investigate using the core "User account menu" in favor of custom Navigation Block for same Active as stable blocker.

Added ✨ For RTL languages, Navigation menu should show on the right Active . IMHO is a "must" for stable, but we would want to check with RTL languages' native speakers.

Adding a new stable blocker: 🐛 Navigation layout Drag is not working in some browers Active .

Adding 📌 Mark Navigation as beta experimental Active as a reference for beta stability sign-offs.

📌 Decide strategy to customize or provide 1st level menu items' icons Active appears twice under the must have list, not sure if that was an oversight or if one of those was meant to be a link to a different issue?

Cleaning up the Stable blockers.

Moving 🐛 The toolbar should be usable without JS Needs work to the Should have section.

Added 🐛 Special Menu items are rendered as empty links in navigation RTBC

Adding 🌱 [META] Migrate Navigation to SDC Active and removing completed tasks.

May I ask why you removed the links to the issues, @ckrina?

- <li>
            
              
              
              🌱
              [PLAN] Icons for the sidebar
                Active
              
             (Ability to choose icons on the UI)</li>
+ <li>Ability to choose icons on the UI</li>

- <li>Environment Indicator</li>
+ <li>
            
              
              
              ✨
              Support for core navigation experimental module 
                Needs work
              
            </li>

Updating with the issues for core modules that need integrations.

Removing fixed issues.

Moving another one into the should have. This is not a critical action for the navigation itself, only if you want to customize it. It should get done, but not block this becoming stable.

Removing a fixed already issue.

There are two more issues that have originally been reported on in the feedback issue, that have not been prioritized yet:

• 🐛 Second level menu items can't be reached if they have children Active
• ✨ Navigating to first level menu items is not obvious Active

✨ Provide Config Action to add new blocks to navigation from recipes Active looks to me like it wouldn't need to be stable blocking too - it's not user-facing and it won't require any API deprecations or storage changes, just a small API addition. I realise it might be Drupal CMS blocking but that's different thing in terms of module stability.

Adding a couple of issues marked stable blocker that were not in the issue summary here under "Must Have".

Updating Top Bar Navigation blockers.

Added 🐛 Second level menu items can't be reached if they have children Active under "Could have"

Removing fixed issues! :D

✨ Provide Config Action to add new blocks to navigation from recipes Active

Updated top bar explanation based on discussion with @ckrina

Added 🐛 Layout Builder Create Inline blocks logic should be optional Active as Must have.

Removed 🐛 Layout Builder Create Inline blocks logic should be optional Active per conversation in Slack from Must have, dropped to Should have.

With 📌 Implement a caching strategy for the menu links Active RTBC, I am starting to think we could skip doing 📌 Implement a caching strategy for the menu links Active , especially if we can figure out 📌 Render the navigation toolbar in a placeholder Active . We probably want to check exactly how much HTML we're sending to the browser, but otherwise those two issues should speed things up considerably.

Discussed the above a bit more with @plopsec and swapped out 📌 Implement a caching strategy for the menu links Active for 📌 Render the navigation toolbar in a placeholder Active in the issue summary.