# Drupal Navigation module on production sites in 2026

Enable core Navigation, retire Toolbar safely, and test keyboard and mobile admin before editors hit production.

- Date: 2026-10-14
- Category: Drupal

## Table of contents

- Why the Drupal Navigation module matters in 2026
- How the Drupal Navigation module works with Toolbar
- Drupal Navigation module production checklist
- What breaks when you enable Navigation
- How to measure a Navigation rollout
- Related Drupal work on this site
- FAQ
  - Should I enable the Drupal Navigation module on every Drupal 11 site?
  - Do I uninstall Toolbar when Navigation is enabled?
  - Is the Drupal Navigation module the same as the contrib Navigation project?
  - What Drupal version do I need for stable Navigation?

The Drupal Navigation module is the admin sidebar I enable when a Drupal 11 site has outgrown the horizontal Toolbar but editors still refuse a separate admin theme. I am Alan Vo, a Gold Coast web developer with 18 years on Drupal catalogues, regulators, museums, and property listings. In October 2026 the module is stable in core, not experimental, and the release notes say it is safe on production sites when you plan the Toolbar cutover and test accessibility like any other editor-facing change.

This note is for teams on Drupal 11.3 or newer (patch to at least 11.3.5 if Navigation ever threw errors on missing menu URLs). It pairs with [Drupal CMS recipes for faster site builds](https://alanvo.com/blog/drupal-cms-recipes/) when you are standing up a greenfield admin, and with [Drupal Canvas vs Layout Builder](https://alanvo.com/blog/drupal-canvas-vs-layout-builder/) when merchandisers customize pages while editors live in core admin. Official background lives in the [Navigation module guide](https://www.drupal.org/docs/develop/core-modules-and-themes/core-modules/navigation-module) and the [Drupal 11.3.0 release notes](https://www.drupal.org/project/drupal/releases/11.3.0).

## Why the Drupal Navigation module matters in 2026

The Drupal Navigation module matters in 2026 because Drupal core marked it stable in 11.3.0 and described it as a collapsible vertical sidebar that replaces the old top Toolbar for day-to-day administration. The [11.3.0 announcement](https://www.drupal.org/blog/drupal-11-3-0) encourages existing sites to switch even though the Standard install profile still ships Toolbar until a later minor enables Navigation by default. That gap is why I see half-migrated stacks: Navigation enabled, Toolbar still installed, Shortcuts still fighting for pixels, and a requirements warning on every status report.

For catalogue and content-heavy sites the win is depth. Sub-menus open in a full-height drawer instead of cramming every task into a horizontal strip. The module ships a content creation and management menu aimed at editors who only need nodes, media, and menus. Site builders can add and reorder menu blocks in the UI, including Layout Builder-backed blocks, which matches how I already customize admin on multi-section government and culture builds. None of that changes the public theme. It only changes how staff reach `/admin/content` and configuration.

Performance work in 11.3 and 11.4 is separate from Navigation, but the same upgrade window is when I roll admin UX forward. I do not enable Navigation to fix LCP. I enable it so editors stop losing tasks in Toolbar overflow on laptop screens.

## How the Drupal Navigation module works with Toolbar

The Drupal Navigation module works as a left-aligned, collapsible sidebar on large viewports and as an overlay on small screens, per the [module overview](https://www.drupal.org/docs/develop/core-modules-and-themes/core-modules/navigation-module). When both Navigation and Toolbar are enabled, Navigation is intended to replace Toolbar behavior. Core's `navigation_requirements()` runtime check warns that both modules are installed and suggests uninstalling Toolbar if you plan to keep Navigation, as documented in [navigation.install](https://api.drupal.org/api/drupal/core%21modules%21navigation%21navigation.install/11.x).

![Drupal Navigation module documentation open beside a laptop](../../images/blog/drupal-navigation-module-production-1.jpg)

Practical steps on a site I control:

1. Upgrade core to Drupal 11.3.x or 11.4.x on staging first. Read the minor release notes for Navigation fixes (for example 11.3.5 addressed Navigation errors on missing URLs).
2. On staging, enable the Navigation module at `/admin/modules` (Extend). Confirm the new sidebar appears for users with administration permissions.
3. Walk the menus your editors use daily: content, media, structure, configuration, reports. Custom modules that only registered Toolbar links may need follow-up if a task disappears from the new tree.
4. When editors sign off, uninstall the Toolbar module (and decide whether Shortcuts still earns its place). The legacy [Toolbar guide](https://www.drupal.org/docs/8/core/modules/toolbar/working-with-the-toolbar) still describes permissions such as "Use the administration toolbar"; Navigation uses the same broad admin permission model but the chrome is different.
5. Export configuration if menu block placement changed. Navigation customization through the UI should land in config sync like any other block.

Navigation is not the public site menu. Do not confuse it with Main menu blocks on the front end. It only wraps administrative routes.

## Drupal Navigation module production checklist

A Drupal Navigation module production checklist starts with staging, a named editor cohort, and explicit Toolbar retirement, not with enabling the module on Friday afternoon.

1. **Baseline on Toolbar.** Record screen recordings of five common editor journeys (create article, upload media, edit menu, clear cache, view reports). You need a before clip when someone asks what changed.
2. **Core version.** Target 11.3.5+ or current 11.4.x patch. Stable Navigation shipped in 11.3.0; patch releases fixed real Navigation bugs.
3. **Enable Navigation on staging.** Confirm no PHP errors on `/admin` for administrator and for a content-editor test account without full config rights.
4. **Keyboard and mobile pass.** The 11.3.0 release notes list known accessibility issues (Escape closing hover submenus, focus in collapsed sidebar, mobile focus trap, reduced motion). Test keyboard-only navigation and a phone-width viewport even if your editors insist they only use desktop. Log defects before production.
5. **Custom admin links audit.** Modules that inject Toolbar items may need updates for Navigation. Check contrib release notes for admin UX modules you rely on.
6. **Training snippet.** One page with screenshots: how to collapse the sidebar, where content tasks moved, how to log out. Editors adapt faster when the help is internal, not a Drupal.org handbook link alone.
7. **Uninstall Toolbar on staging** once Navigation covers every required task. Resolve the requirements warning before go-live.
8. **Production change window.** Enable Navigation, smoke-test the same five journeys, uninstall Toolbar if that was the plan, run `drush cr` or equivalent cache rebuild.
9. **Monitor support tickets** for two weeks. Admin changes feel breaking even when nothing on the public site moved.
10. **Recipes and new builds.** When Drupal CMS recipes start enabling Navigation by default, align new installs with this runbook so legacy Toolbar habits do not creep back on greenfield sites.

![Team workshop around a table planning a CMS rebuild](../../images/blog/drupal-navigation-module-production-2.jpg)

## What breaks when you enable Navigation

What breaks when you enable Navigation is usually process, not PHP. Editors muscle-memory the old horizontal menus. A missing custom Toolbar link looks like "the module broke my site" when a contrib module never registered the route in Navigation. Running both Toolbar and Navigation triggers a permanent status warning and confusing double chrome until you uninstall Toolbar.

Accessibility gaps called out in core release notes are not theoretical. If your organisation has a VPAT or internal a11y gate, treat Navigation like any other UI swap: document known issues, retest after each minor, and do not assume stable means "WCAG signed off". Mobile overlay behavior differs from desktop collapse; test both.

Patch 11.3.5 explicitly fixed Navigation throwing on missing URLs. If you saw white screens or logged exceptions tied to bad menu links, upgrading the patch line is the fix, not disabling Navigation forever.

Training debt hits multilingual teams hardest. Admin language negotiation still follows user preferences, but menu labels move. Update internal docs in every language editors actually use.

## How to measure a Navigation rollout

How to measure a Navigation rollout is editor time and support noise, not Google Analytics pageviews. I track tasks per session in staging usability tests: time to publish a revision, time to find media library, error clicks on the wrong menu. After production I watch helpdesk tags for "cannot find" and "admin looks different" for fourteen days.

Technical checks stay lightweight: no new PHP fatal errors in logs on `/admin/*`, requirements report clean after Toolbar uninstall, and no spike in failed logins (sometimes tied to overlay confusion on mobile, not security).

![Library stacks used as a stand-in for structured content](../../images/blog/drupal-navigation-module-production-3.jpg)

If you also ship [Drupal SEO Tools recipe](https://alanvo.com/blog/drupal-seo-tools-recipe/) configuration, confirm editors can still reach metatag and redirect screens through Navigation without bookmarking old Toolbar paths.

## Related Drupal work on this site

Navigation sits beside the CMS work I document for clients with large editorial teams. On [NDIS Commission](https://alanvo.com/work/ndis-commission/) style regulator builds, admin clarity matters as much as public information architecture. [Royal Ontario Museum](https://alanvo.com/work/royal-ontario-museum/) scale catalogues mean dozens of content types; a vertical admin tree scales better than horizontal overflow. [Immobel](https://alanvo.com/work/immobel/) property listings tie Drupal content to external commerce surfaces; editors still live in core admin daily, so Navigation is worth the migration week even when JSON:API feeds the storefront.

When a site already runs Canvas or Layout Builder for landing pages, Navigation does not replace that editor experience. It replaces how staff reach those tools. Read [Drupal Canvas vs Layout Builder in 2026](https://alanvo.com/blog/drupal-canvas-vs-layout-builder/) for the public-side split; use this note for the `/admin` split.

## FAQ

### Should I enable the Drupal Navigation module on every Drupal 11 site?

You should enable the Drupal Navigation module on Drupal 11.3+ when editors spend real time in core admin and the horizontal Toolbar is already a complaint. Core marks the module stable for production, but the same release notes document accessibility issues you must retest. Skip it only on headless or nearly headless stacks where nobody logs into `/admin` except developers, or until you are on a supported 11.3 patch line.

### Do I uninstall Toolbar when Navigation is enabled?

You should plan to uninstall Toolbar once Navigation covers every administrative task your team needs. Core warns when both modules are installed because Navigation replaces Toolbar functionality. Keeping both creates noise on the status report and confuses editors who see legacy patterns in documentation. Uninstall on staging first, export config, then repeat on production in a named window.

### Is the Drupal Navigation module the same as the contrib Navigation project?

It is not the same deliverable anymore. The contrib [Navigation project on Drupal.org](https://www.drupal.org/project/navigation) was merged into core; the project page tells you not to install the outdated contrib module. Your production path is core Navigation on Drupal 11.3 or newer, documented under [core Navigation module](https://www.drupal.org/docs/develop/core-modules-and-themes/core-modules/navigation-module).

### What Drupal version do I need for stable Navigation?

You need Drupal 11.3.0 or later for Navigation marked stable in core release notes. Run a current 11.3.x or 11.4.x patch release so you pick up Navigation bugfixes such as missing URL handling. Drupal 10 sites may have seen experimental Navigation earlier; for a stable, supported path in 2026, plan the upgrade to 11.3+ as part of the same admin UX project.


![Government-style office desks and screens](../../images/blog/drupal-navigation-module-production-4.jpg)


HTML version: https://alanvo.com/blog/drupal-navigation-module-production/