Understanding Public Navigation and Content Discovery

Finding your way with the public sidebar

In Atloria’s published documentation, the public sidebar is the main place readers use to move from one page to another. It shows the published documentation structure as a visible list of categories and pages, so readers can understand both what is available and where they are in the overall set of docs. If you already know the basics of moving through public docs, this section builds on Using Public Navigation to Browse Documentation and focuses on how readers discover content more efficiently.

When you look at the sidebar, you will usually see:

• Top-level categories that group related topics
• Nested categories under broader sections
• Individual page titles listed inside those groups
• A clear active page highlight showing the page currently open

That active highlight matters because it helps readers stay oriented while moving through a large documentation set. Instead of guessing where a page belongs, they can glance at the sidebar and see the surrounding category and nearby related pages.

If a category contains more content, readers can expand it to reveal child categories or page titles, then collapse it to reduce clutter and focus on the section they need. This is especially useful when a project has many published pages and readers want to scan only one branch of the documentation tree at a time.

Selecting a page title in the sidebar opens that published page in the main reading area. Readers do not need editing access or project workspace access to do this. They simply use the public navigation to move through available content.

A well-organized sidebar turns the published documentation into a browsable map. Readers can move confidently because the page list, category grouping, and current-page highlight all work together.

Browsing documentation through categories and page hierarchies

In Atloria, categories and pages do different jobs in public navigation. A category helps organize related content into a section, while an individual page is the actual document a reader opens and reads. Understanding that difference makes it much easier to scan the sidebar and predict where information is likely to be found.

Readers often move through public documentation in layers:

• Start with a top-level category
• Open a child category if the topic is broken into smaller sections
• Select a specific published page
• Continue deeper if more nested content is available

This hierarchy is what makes long documentation sets manageable. Instead of showing one long, flat list of page titles, Atloria groups content into meaningful sections. A reader looking for setup instructions, for example, can first identify the broad section, then narrow down into a more specific subgroup, and finally choose the exact page they need.

Nested category structures are especially helpful when documentation includes:

• Introductory pages
• Task-based guides
• Reference pages
• Audience-specific sections
• Detailed subtopics under a larger feature area

For documentation managers, category names and page order strongly affect public discovery. Readers scan quickly, so labels should be clear and specific. A category name should tell readers what kind of content sits inside it, and page titles should distinguish one topic from another without forcing readers to open several pages just to compare them.

Ordering also matters. Readers usually expect pages to appear in a sensible sequence, such as from basic to advanced, from overview to detail, or from setup to troubleshooting. If related pages are scattered across unrelated categories, readers are more likely to miss important content.

When categories are named clearly and arranged logically, readers can discover content by browsing, not just by already knowing the exact page title.

Moving between pages with in-content links

The sidebar is not the only way readers move through published documentation in Atloria. Many pages also include links inside the page content that point to related published pages. These in-content links help readers continue naturally from one topic to the next without returning to the sidebar each time.

This creates two different navigation styles:

• Sidebar navigation for browsing the overall documentation structure
• In-content links for following a guided reading path inside the page itself

Both are useful, but they support different reading habits. A reader who wants to explore broadly may rely on the sidebar to compare sections and jump between categories. A reader who is already on the right topic may prefer to follow links in the page body to go directly to the next related page.

This is especially helpful for guided content flows, such as:

• Moving from an introduction page to a detailed setup page
• Jumping from a feature overview to a task-specific guide
• Opening a related troubleshooting page from a how-to article
• Following a sequence from summary content into deeper subpages

When a reader selects one of these links, Atloria opens the linked published page in the main content area. The sidebar updates to reflect the new location, showing the newly active page and its place within the category structure. That means readers do not lose context when they navigate by link instead of by sidebar.

This combination is important for content discovery. The sidebar helps readers understand the full structure, while in-content links help them move through related topics at the moment they need them. If you are planning public reading paths, use links to connect pages that are commonly read together rather than forcing readers to backtrack through the category tree every time.

Using the table of contents to jump within a page

On longer published pages in Atloria, the table of contents helps readers move within the current page instead of between different pages. It is built from the page’s visible headings, so section titles become clickable jump points that take readers directly to the part of the page they want.

This is useful when a page covers several related topics, such as an introduction, setup notes, examples, and troubleshooting details all in one document. Rather than scrolling through the entire page, readers can scan the table of contents and jump straight to the section name that matches what they need.

The table of contents helps readers by:

• Showing the page’s section structure before they scroll
• Making long pages easier to scan
• Letting them jump directly to a lower section
• Revealing whether the page includes the topic they are looking for

Because the table of contents depends on heading structure, clear heading labels improve navigation. Readers benefit most when headings are specific and easy to recognize. A heading like Troubleshooting login issues is much easier to spot in the table of contents than a vague heading like More information.

Heading levels also matter. When headings are used consistently, the table of contents reflects the page structure more clearly, showing main sections and supporting subsections in a readable way. That improves both on-page navigation and overall discoverability, because readers can understand the page at a glance.

If a reader arrives on a long article from the sidebar or from an in-content link, the table of contents becomes the fastest way to refine their path. They can stay on the same page, skip to the right section, and continue reading without losing momentum.

Understanding how readers discover related content

Readers rarely move through published documentation in just one way. In Atloria, content discovery usually comes from several navigation elements working together: the sidebar, the category hierarchy, in-content links, and the table of contents. When these are aligned, readers can move from broad exploration to precise answers without feeling lost.

A common reading path looks like this:

• Enter the published docs on a landing or section page
• Use the sidebar to open a broad category
• Drill into a child category to narrow the topic
• Open a specific page from the page list
• Use the table of contents to jump to the right section
• Follow an in-content link to a related page for more detail

This layered workflow is what makes public documentation feel connected instead of fragmented. A reader might begin with only a rough idea of the topic, then use the sidebar to browse, the page title to confirm relevance, the table of contents to skip ahead, and inline links to continue into supporting material.

Documentation managers can make this easier by checking that major pages are reachable in at least one obvious way:

• Through the sidebar
• Through a clear category path
• Through contextual links from related pages
• Through recognizable page titles and section headings

Dead ends usually happen when an important page exists but is hard to discover from nearby content. If a reader finishes a page and has no visible next topic, they may stop even though useful related pages are available elsewhere in the published tree.

Consistent naming helps prevent that. When page titles, category labels, and heading names use the same language, readers can scan faster and trust that they are following the right path.

If you need more detail on version-aware reading while navigating public docs, see Reading Versioned Documentation in Public Views.

Fixing navigation problems readers may encounter

When readers struggle to move through published documentation in Atloria, the problem is usually visible in the navigation itself. Start by checking what the reader sees in the sidebar, on the page title, and in the table of contents. Small structural issues can make published content feel much harder to find than it really is.

If a page is hard to find in the sidebar, review whether it appears under the category readers would naturally expect. Also check its position in the page list. Even a correctly published page can be overlooked if it sits under an unexpected category or appears in an order that breaks the reading flow.

Look for issues such as:

• A page placed under the wrong published category
• A useful page title buried too low in a long section
• Related pages split across categories without clear labels
• A title that does not match the terms readers scan for

If readers cannot tell where they are, confirm that the current page is clearly reflected by the active page highlight in the sidebar and that the page title matches the surrounding category labels. Similar page names in the same section can make orientation harder, especially if nearby titles are too broad or repetitive.

When the table of contents is missing or incomplete, the page may not have a clear heading structure. Long pages are much easier to navigate when section headings are visible and distinct enough to appear in the on-page navigation.

If related topics feel disconnected, add or revise in-content links between pages that are commonly read together. Readers should not have to return to the sidebar after every page just to continue a common workflow.

A good troubleshooting check is simple: open the page as a reader, try to find the next likely topic, and see whether the sidebar, headings, and links make that path obvious.

Overview

Public navigation in Atloria helps readers do more than open pages one by one. It gives them a clear way to discover, compare, and move through published documentation using the structure visible on the page. The most important parts of that experience are the public sidebar, the category hierarchy, in-content links, and the table of contents.

Together, these elements support different reading behaviors:

• Browsing through categories in the sidebar
• Scanning page titles to find the right document
• Jumping within a long page through the table of contents
• Following links in the content to continue to related topics

For readers, this means they can start broad and become more specific as they go. They might first recognize a category name, then choose a page title, then jump to a section heading, and finally open another linked page for more detail. That is the core of content discovery in published documentation.

For documentation teams, the public reading experience improves when navigation elements stay aligned:

• Category names match the language readers expect
• Page titles clearly describe the topic
• Heading labels make sense when shown in the table of contents
• Related pages are connected through visible links

If one of those pieces is unclear, readers may still reach the content, but they will do it more slowly and with more guesswork. If all of them work together, the published docs feel easy to explore even when the documentation set is large.

This document focuses on how readers discover and move through public content. The next guide, Managing Reader Navigation Across Public Documentation, looks at how to shape that experience across the full published documentation set.

Prerequisites

Before using the navigation patterns in this guide, readers should already be comfortable opening and reading published documentation in Atloria. This topic assumes you can already recognize the public reading view and move around basic published pages.

You will get the most value from this guide if you already understand:

• How to browse published pages from the public reading experience
• How public navigation differs from editing inside project workspaces
• How version context affects what readers see in public docs
• How audience-specific content can change what appears in navigation

Helpful background reading includes:

• Using Public Navigation to Browse Documentation
• Browsing Published Documentation and Finding the Right Page
• Using Public Navigation with Audience Specific Content
• Reading Versioned Documentation in Public Views

You do not need access to Atloria’s editing screens, project setup screens, or admin areas to follow this guide. Everything here is based on the published documentation view that readers use publicly.

It also helps to have a documentation set with:

• More than one published category
• Several published pages
• Visible section headings on longer pages
• At least a few links between related pages

Those elements make it easier to see how discovery works in practice. If your published docs are still small, the same navigation ideas still apply, but the sidebar structure, page relationships, and table of contents will become more noticeable as your documentation grows.