Managing Reader Navigation Across Public Documentation

Opening the docs and orienting yourself in the sidebar

When you open public documentation in Atloria, the page is organized into three reading areas. On the left, you see the navigation sidebar. In the center, you see the current article. On the right, you may see a table of contents for the page you are reading. This layout makes it easy to move between topics without leaving the documentation view.

The left sidebar is the main place to get oriented. It shows the documentation structure as a list of categories and pages. Some items act as section headers that can be expanded or collapsed, while others open a specific article. If you already know part of the topic name, use the search input in the sidebar to quickly narrow the list and jump to the page you want without guessing the page address.

As you move through the docs, Atloria highlights the page you are currently reading in the sidebar. Parent sections stay open so you can see exactly where that page sits in the larger documentation structure. This is especially helpful when you arrive from a shared link and want to understand the surrounding topic area.

You may notice three kinds of pages while browsing:

• Landing pages introduce a broader documentation area.
• Category pages collect related articles under one topic.
• Individual documentation pages contain the full article content.

If you need a refresher on basic public browsing before working across multiple sections, see Understanding Public Navigation and Content Discovery.

Browsing categories and moving between related pages

Category pages help you move through related content without starting over from the top of the documentation each time. In Atloria, a category groups articles that belong to the same subject area, so you can begin with a broader page and then open more specific child pages from there.

In the sidebar, categories usually appear as expandable items. When a category is collapsed, you only see the category label. When you expand it, the child pages appear underneath, often indented to show the navigation level. Some categories may contain additional nested levels, which helps organize larger documentation sets into smaller, easier-to-scan sections.

You can move through a category in several ways:

1. Click the category name in the sidebar if it opens an overview page.
2. Expand the category and select a child page directly from the navigation tree.
3. Use links inside the current page to open related pages in the same section.
4. Use the Previous and Next links at the bottom of an article to continue through a sequence.

Those Previous and Next links are especially useful when you are reading a guided set of articles in order. They let you continue to the next topic without reopening the sidebar after every page.

As you browse, visible parent category names and the open navigation path help you understand where you are. If you move deep into a nested section, you can still look at the expanded sidebar and trace your way back to the broader topic. For more detail on finding pages inside published docs, see Browsing Published Documentation and Finding the Right Page.

Using the table of contents to scan long pages

On longer documentation pages in Atloria, the right side of the screen may show a table of contents. This panel is built from the headings inside the article, so it reflects the actual sections on the page you are reading. Instead of scrolling through the full article to find one topic, you can use this list to jump straight to the section you need.

Each entry in the table of contents matches a heading in the article. When you click one of these entries, Atloria scrolls the page to that heading. This is useful when a page includes several tasks, examples, or reference sections and you only need one part of the article.

As you scroll through the page, the table of contents also helps you keep your place. The heading for the section you are currently reading is highlighted, so you can tell where you are within the article at a glance. If the page has multiple heading levels, the table of contents may show a nested structure, making it easier to understand how sections relate to one another.

You may not always see a table of contents. Short pages with only a title and a small amount of content may not have enough headings to generate one. On those pages, the right side may be empty or contain only a very short list. That does not mean anything is wrong with the page; it usually just means the article is brief.

If you are working with public pages that include version context or technical reference sections, the table of contents becomes even more useful for jumping between larger blocks of content. Related reading: Reading Versioned Documentation in Public Views.

Switching between documentation versions without losing context

If a documentation set in Atloria includes multiple releases, you can switch between them using the version selector. This control appears in the public documentation header or page chrome and lets you choose which version of the docs you want to read.

The version selector is useful when instructions differ between releases. For example, you might compare the current documentation with an older version or check a prerelease set before rollout. Each version is labeled so you can tell whether you are reading the current release, an earlier release, or a prerelease version.

When you choose a different version, Atloria tries to keep you in the same place by opening the matching page in that version when it exists. This saves time because you do not need to manually browse back to the same topic after every switch. If the page is available in both versions, you stay on the equivalent article and can compare the content more easily.

Sometimes the page you are reading does not exist in the version you selected. In that case, Atloria may open the version home page or the nearest available page instead. If that happens, check the sidebar after the switch. The active page highlight and expanded category path will help you confirm where you landed and whether you need to open a different article in that version.

When comparing releases, always look at the version label before following instructions or sharing a link. If you want a deeper explanation of how version context affects public reading, see Understanding Public Document Views and Version Context.

Sharing and revisiting the exact page you need

Public documentation in Atloria is designed so you can return to the same place later or share it with someone else. Each article has its own page address, and when versioned documentation is in use, the selected version is part of that context. That means the link you copy can point to the exact article and, when applicable, the exact release you were viewing.

If you want to share a specific section instead of the whole article, use the heading link from the page itself or from the table of contents. This is especially helpful on long pages where the person receiving the link only needs one section. A section link opens the page and jumps directly to the matching heading.

Browser navigation also works well with public docs. If you click several pages in the sidebar, use an in-page heading jump, or switch versions, the browser Back and Forward buttons can help you retrace your steps. This is useful when you follow a related link and then want to return to the exact article or section you were reading before.

Choose your bookmark based on what you need to revisit:

• Bookmark a category page if you want a broad starting point for a topic area.
• Bookmark an article page if you return to one guide often.
• Bookmark a version-specific page if the instructions matter for one release.
• Bookmark a section link if you repeatedly use one part of a long article.

For more on moving through public content before sharing links, see Using Public Navigation to Browse Documentation.

Fixing common navigation problems readers run into

Most public navigation issues in Atloria come down to page location, heading structure, or version context. If something does not look right, start by checking what page you are on, which version is selected, and what is highlighted in the sidebar.

If a page seems to be missing from the sidebar, first check the version selector. You may be viewing a release where that page does not exist or where it was reorganized. Next, expand nearby categories in the sidebar and look for the page under a different section. Because Atloria keeps parent categories open for the current page, the navigation tree often gives you a clue about where related content now lives.

If the table of contents is missing expected sections, look at the article itself. The table of contents is based on visible page headings. If the page is short or has only a few headings, the table of contents may be very small or absent. This usually reflects the structure of the page rather than a loading problem.

If the version selector opens a different page than you expected, the exact article may not be available in the version you selected. Atloria may send you to the version home page or another nearby page instead. Use the sidebar and the active-page highlight to find the closest matching article in that release.

If you lose your place after following links, try these options:

• Use the browser Back button to return to the previous page or section.
• Check the highlighted page in the sidebar to confirm your current location.
• Look at the expanded category path to move back to the broader topic.
• Reopen the section you were reading from the table of contents if you only lost your place within a long page.

For audience-specific public reading patterns, see Using Public Navigation with Audience Specific Content.

Overview

This guide focuses on how readers move through public documentation in Atloria once the docs are already published and available to browse. The main navigation tools are the left sidebar, the article area, the right-side table of contents when present, and the version selector for documentation sets that include multiple releases.

The sidebar helps you move across categories and articles, with the current page highlighted so you can always see where you are. Category pages give you a broader entry point into a topic, while individual pages let you read detailed instructions. On longer articles, the table of contents helps you jump to specific sections and keep track of your position as you scroll. When versioned docs are available, the version selector lets you compare releases without manually searching for the same topic again.

This guide is most useful when you want to do one of the following:

• Find a page from the public navigation tree
• Move through related articles in a category
• Jump to a section within a long article
• Switch to another documentation version
• Share or bookmark the exact page or section you need
• Recover quickly when a page appears missing or opens somewhere unexpected

It builds on the public reading concepts covered in Understanding Public Navigation and Content Discovery and stays focused on practical navigation behavior rather than content authoring or publishing setup.

Prerequisites

Before using the navigation patterns in this guide, make sure you have access to a public documentation site in Atloria and can open at least one published article. You do not need editing access, project permissions, or admin tools for the tasks described here. This guide is written for readers using the public documentation experience.

You will get the most value from this guide if the following are true:

• You can open the public docs and see the left navigation sidebar
• You can load an article page in the main reading area
• You may have a right-side table of contents on longer pages
• You may have a version selector available if the docs include multiple releases

It also helps if you are already familiar with the basics of public browsing, including opening pages from the sidebar and recognizing category-based navigation. If you have not covered that yet, read Using Public Navigation to Browse Documentation first.

Use this guide when you are trying to navigate more efficiently across a larger documentation set, compare versions, or return to a specific page later. If you need help with audience-based public views instead, refer to Viewing Public Documentation by Audience.