Atlassian’s recent rollout of a refreshed navigation experience in Confluence Cloud—introducing a sleek, vertical sidebar—marks a significant evolution in how users browse spaces and content. The intention is clear—the new navigation is built for usability at scale with:
But even with this progress, many teams continue to rely on horizontal menus—custom top-level navigation that lives within Confluence pages themselves. Why? Because one size doesn’t fit all. Here’s why horizontal menus still matter.
For many companies, Confluence isn’t just a wiki—it’s a branded internal portal, documentation hub, or employee resource center. And those use cases demand more than functionality—they require visual consistency and user experience that matches the company’s identity.
Brand colors, icons, and layout all contribute to engagement.
Horizontal menus integrate cleanly with banners, cover images, and headings.
But here’s another benefit often overlooked:
🌍 For distributed, global teams, tools like Navigation Menus for Confluence Cloud make it possible to structure menus by Geographic Locations. Whether your offices are in Munich, São Paulo, or Tokyo, you can build menus that reflect local terminology, and language—all within the same Confluence site.
This level of localization and customization just isn’t feasible with the default vertical sidebar, especially when branding, structure, and accessibility need to coexist.
Different teams work and think differently. A single vertical sidebar can't serve everyone equally.
Product and engineering teams prefer project-centric overviews that span across multiple pages. Typical menu items might be “Product Specs,” “Sprint Backlogs,” “Architecture Docs,” or “Release Notes".
Onboarding and training teams benefit from guided, step-by-step navigation. Their menus could include “Start Here,” “Tools & Access,” “Team Intros,” “First Week Tasks,” and “Compliance Training.
While the new sidebar improves content discoverability at a system level, horizontal menus allow teams to curate how users move through specific content—within a space or across spaces.
Horizontal menus aren’t just prettier—they can be smarter. Navigation Menus for Confluence Cloud supports Confluence Query Language (CQL), allowing menus to dynamically populate based on metadata like:
Page labels
Update dates
Author or contributor
Mentions
and more...
This means you can build menus that auto-update—showing, for example, the most recently updated onboarding pages created by team HR without having to manually change anything. This level of automation goes beyond what’s possible with the built-in sidebar.
The new sidebar is a significant improvement. But that doesn’t mean horizontal menus are outdated—they’re just solving a different problem.
The sidebar is great for system-wide navigation across spaces and tools.
Horizontal menus shine when storytelling, branding, structure, and custom logic are required within content.
It’s not an either/or decision. The most effective Confluence setups combine both: letting the platform handle the infrastructure while teams customize the experience to match how they actually work. Want to see how they play nice in action? Find us on the Atlassian Marketplace, here.
Angela Thomas_Seibert Group
Product Marketing Manager at Seibert Group
Seibert Group
Munich, Germany
4 accepted answers
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
2 comments