We've introduced exciting changes to creating and customizing the Navigation Menu in Cosmos. This revamped feature offers enhanced flexibility and personalization options. Find out what’s new and how it works below. Happy navigating!
...
Cp content card macro | ||
---|---|---|
|
Locating the Configuration
Navigate to the settings icon in the sidebar and select.
Navigate to Navigation Menu → Configuration, and select.
Locate the toggle at the top of the drawer to enable or disable navigation.
You'll find a real-time preview on the right side of the screen.
...
Confluence is great for teamwork and managing projects, but finding your way around all the content can be tough. Cosmos Navigation adds a helpful navigation bar just under Confluence's top bar, making it easier to get to important pages and content quickly.
...
Locating the Navigation configuration
From your Confluence navigation bar, access Cosmos by selecting it from the Apps dropdown.
Within Cosmos, proceed to the Settings area.
In the Settings menu, locate the Navigation section and click on Configuration.
Navigation styles
Unlike the previous approach, where changes affected the entire menu, you can now select a specific style when adding a new entry. We've introduced three new styles in addition to the existing ones:
...
London and Sydney → These styles offer a familiar layout with minor design enhancements.
Denver → A visually oriented style featuring an image with multiple links, offering different image sizes (S, M, L) and design options (icon or plain text).
Palo Alto → Choose from a wide range of icons (including custom ones from /wiki/spaces/MAC/pages/18259300) to create a visually appealing menu.
Hum → A minimalistic style with a simple link – perfect for streamlined navigation
Intranet Entry
An Intranet entry is now a permanent addition at the beginning of the menu.
This entry links to the Cosmos Dashboard.
While the name can be customized, it cannot be deleted.
Editing entries
Click on the entry edit icon.
Edit the icon and the entry title.
Toggle icons and descriptions on/off if needed.
Editing Subentries
Click on the subentry edit icon.
Edit the icon, name, and description, and insert a link to the link box.
Design Customization
Navigate to the Design tab for overall menu design customization.
If using MacroSuite, adjust the background, text, icon colors, and hover effects to match the branding.
Personalization with Collections
Create Collections to group users by specific criteria.
Assign menu entries to specific Collections, tailoring the menu for different teams.
Space-Based Navigation
Personalization is available with Content Viz.
The menu adapts to Confluence's space structure.
Display different entries based on the active space, ensuring contextual relevance.
Publishing the Navigation Menu
Don’t forget to save! Once you finish creating your navigation menu, click Publish and share it with everyone. The Cosmos Navigation Menu is visible across all Confluence. Ready, set, navigate!
...
Transitioning from Previous Menus
For existing users, rest assured that your old navigation will seamlessly integrate with the new changes. You'll find your familiar menu intact while having the option to explore the exciting new styles.
...
Houston → Engaging display of spaces within the navigation, ensuring users have quick access to the most relevant and important information source.
Steps to add new navigation entries
Click on the Add Menu Option button; a screen showcasing various navigation styles will appear.
...
Hover over each style to view a preview of how it looks.
Select the navigation style you wish to use by clicking on it.
...
Once selected, a navigation entry is created. At this point, you'll need to configure its layout and design. Each navigation style comes with its unique layout and design options.
Go back to the main navigation settings and find the newly created navigation entry. Here, you can start adding subentries, defining their design, and linking content.
...
Remember, the changes you make won't be visible to other users until you hit the save button located in the right bottom corner.
Personalize navigation entries
By setting view permissions based on Collections, admins can ensure that navigation entries are visible only to relevant user groups. Furthermore, admins have the ability to specify the Confluence spaces where each navigation entry should be displayed, providing a tailored navigation experience that aligns with the unique structure and needs of the organization.
Steps to customize navigation entry visibility
Click on the edit button for the desired navigation entry.
...
Find and click on the lock button located in the right upper corner.
Set the visibility options:
Determine if the navigation entry should be visible to anonymous users. (Only applied if the Confluence instance is opened for anonymous access)
Specify the Confluence spaces where this navigation entry will be displayed.
Use collections as an additional filter to define which user groups can view the navigation entry.
...
Publish navigation
Within the navigation configuration interface, there's a toggle feature that provides a straightforward way to enable or disable navigation for the whole Confluence instance. This functionality allows admins to easily publish the navigation once its configuration is complete, ensuring everything is set up perfectly before making it visible to users.
...
Additionally, this toggle offers the flexibility to hide the navigation from all users at any time, granting admins control over the availability and visibility of navigation options based on the organization's current needs or preferences. This feature ensures that navigation can be managed efficiently, keeping the user experience optimized and aligned with ongoing updates or changes.
Warning |
---|
Please note an important consideration regarding the navigation feature and Atlassian's native PDF export functionality. When navigation is enabled within Cosmos, it becomes part of the content exported using Atlassian's built-in page PDF export feature. This behavior has been identified, reproduced, and formally reported to Atlassian's technical team for review and resolution. |