Reading Versioned Documentation in Public Views

Opening a Versioned Documentation Page from a Public URL

When you open public documentation in Atloria, you do not need to sign in first. A public page opens directly in the browser and is designed for reading, browsing, and moving between published releases. Unlike the private workspace, there is no project dashboard, editing toolbar, or publishing screen in this view. You arrive straight on the documentation page itself.

A versioned public link usually includes a release-specific part in the web address. That version segment is what tells you which release you are reading. For example, one public link may open the current documentation set, while another includes a version name in the path and opens an older published release. Even if the page title is the same, the version segment in the address helps confirm whether you are on the latest documentation or a frozen historical copy.

As soon as the page loads, look for the visible version cues in the page layout. In Atloria, this may appear as a version label in the top area of the page, a release badge near the page title, or a version switcher in the header. These are the quickest signs that you are reading a specific published release rather than a general landing page.

Because this is a public reading experience, the screen focuses on navigation controls such as the header, sidebar, breadcrumbs, and version selector. You can move through pages, open related topics, and switch releases, but you will not see editing actions such as creating pages, changing content, or publishing updates.

Recognizing Which Release You Are Reading

The most reliable way to confirm the active release is to check the version information shown in the page layout before you start reading. In Atloria, the active release may appear in several places at once: the top navigation area, a breadcrumb trail, a badge near the page title, or the version switcher itself. If more than one of these is visible, use them together. That makes it easier to avoid confusing an older release with the current one.

This matters most when two releases contain a page with the same title. For example, a page called Getting Started can exist in both the current documentation set and an archived release. The title alone does not tell you which one you are viewing. Instead, compare:

• The version label shown in the header or near the title
• The version segment in the web address
• Any release badge or archived notice on the page

When you are on the current documentation set, Atloria may show cues that indicate you are reading the latest published version rather than a fixed older release. That cue might appear in the version switcher, in the top page area, or through the absence of an archived-version notice. If you move into an older release, the page layout should continue to show that older release name as you browse from page to page.

That persistent version context is important. As you use the sidebar, breadcrumbs, or in-page links, keep an eye on the release label. If the label stays the same, you are still inside the same documentation set. If it changes, you have moved to a different release and should recheck the page before relying on the content.

For a broader explanation of public page context before focusing on releases, see Understanding Public Document Views and Version Context.

Moving Between Current and Older Documentation Versions

To move between releases in Atloria, use the version switcher or release dropdown shown in the public page header. This is the safest way to change versions because it keeps you inside the published navigation instead of forcing you to guess the correct web address.

1. Open the public documentation page you want to read.
2. Find the version switcher or release dropdown in the top area of the page.
3. Click the current release name to open the list of available versions.
4. Select the release you want to view.

If the same page exists in both releases, Atloria should keep you on the equivalent page after the switch. The page title may stay the same, but the version label and the web address will update to match the release you selected. This is useful when you want to compare how a single topic changed over time without manually searching for it again.

Sometimes the selected release does not include that page. In that case, Atloria may take you to the release home page, the nearest available section, or show a message that the page is not available in that version. If that happens, use the sidebar or breadcrumbs inside that release to find the closest matching page.

To return to the latest documentation, open the version switcher again and choose the current release. If Atloria shows a latest-version link or a clearly labeled current release option in the page header, use that instead of editing the web address by hand.

Comparing the Reading Experience Across Releases

Reading across releases in Atloria often feels familiar, but the structure can change from one version to another. The sidebar may contain different sections, page names may move to new locations, and the order of topics can shift as documentation evolves. When you open an archived release, expect the navigation menu and page hierarchy to reflect how the documentation looked at the time that release was published.

Older releases may also include extra visual cues that affect how you read. For example, an archived version can show a release-specific notice, an outdated-content warning, or a message that a newer release is available. These notices help you understand that the content is still available for reference but may no longer describe the recommended workflow.

Version context should stay consistent while you browse. If you click a sidebar item, a breadcrumb link, or a cross-reference inside the page, Atloria should keep you inside the same selected release whenever that content exists there. Search results and internal links should behave the same way. If you started in an older release, the destination page should continue to show that release label so you do not accidentally jump to the latest content without noticing.

A practical way to compare releases is to open the latest documentation in one browser tab and an older release in another. That lets you check differences in wording, page placement, and release notices side by side. If you are researching historical behavior or validating instructions from an older rollout, this approach is usually faster than switching back and forth repeatedly in one tab.

Understanding What Documentation Managers Control in Public Version Views

What you see in a public versioned page is shaped by publishing choices made by the people managing documentation in Atloria. Readers do not control which releases appear in the version switcher. That list depends on which releases were published publicly and which one was marked as the current release.

From a reader’s point of view, the visible clues are straightforward:

• The release names shown in the version switcher
• Which release appears as the current or latest option
• Whether an older release shows archived or outdated messaging
• Which pages are available inside each release

Those cues come from decisions made before the public documentation was shared. If a page was included when a release was published, readers can open it in that release. If it was not included, it will not appear there later just because the page exists in a newer release. This is why one version may contain a page that another version does not.

Documentation managers also shape how easy public navigation feels by choosing clear release names and by deciding how archived releases are labeled. A well-named release in the version switcher makes it much easier for readers to choose the right documentation set without opening several pages first.

The boundary is simple: public readers can browse, read, and switch between the releases that are available to them, but they cannot change release labels, mark a release as current, add missing pages, or publish updates from the public view. If you manage documentation and want to understand the publishing side behind these reader-visible results, see Managing Version Visibility and Reader Access and Controlling Version Visibility and Export Options.

Fixing Confusing Version Navigation and Missing Pages

Version confusion usually happens when the page title looks correct but the release is not. In Atloria, start by checking the version badge, release label, or version switcher in the page header. Do not rely on the page title alone. The same title can appear in multiple releases.

If you think you are on the wrong release:

• Check the version label in the top page area
• Open the version switcher and choose the release you actually want
• Confirm that the web address updates after the switch

If a bookmarked link opens an outdated page:

• Look at the version segment in the web address
• Use the version switcher to move to the current release
• If Atloria shows a latest-version link in the page header, use that to jump back to the newest published set

If the release you selected does not show the page you expected:

• The page may not have existed when that release was published
• Open the release home page if Atloria sends you there automatically
• Use the sidebar, breadcrumbs, or section navigation to find the nearest equivalent page in that release

If links or search results seem to jump between releases unexpectedly:

• Check the version label before and after you open the destination page
• Confirm whether the destination stayed in the same release
• If not, return to the version switcher and reselect the release you want before continuing

When version-related navigation still feels inconsistent, compare the current page’s release label, web address, and sidebar position together. Those three cues usually reveal whether you are on the correct page in the correct release.

Overview

Versioned public documentation in Atloria lets you read published content by release without entering the private workspace. The key idea is simple: the page title tells you what topic you are reading, while the version label and web address tell you which release that topic belongs to. You need both pieces of information to read confidently.

As you move through public documentation, watch for these reader-facing elements:

• A version switcher or release dropdown in the page header
• A release label or badge near the page title
• Breadcrumbs and sidebar navigation that stay inside the selected release
• Archived or outdated notices on older documentation sets

The current release is usually the easiest place to start when you want the most up-to-date instructions. Older releases are useful when you need to confirm historical behavior, review past wording, or match documentation to an earlier rollout. Atloria supports both reading styles by keeping public pages read-only and centered on browsing rather than editing.

This guide focused on how to identify version context, move between releases, and handle common problems such as outdated bookmarks or missing pages. If you need background on how public page context appears before switching releases, return to Understanding Public Document Views and Version Context.

The next topic expands from version awareness into broader discovery patterns across public documentation: Understanding Public Navigation and Content Discovery.

Prerequisites

Before using versioned public documentation in Atloria, make sure you have the basics needed to follow release-specific pages without confusion:

• A public documentation link that opens in your browser
• Access to a published documentation set that includes more than one release, if you want to compare versions
• Familiarity with basic public navigation elements such as the header, sidebar, breadcrumbs, and page links
• A general understanding that public documentation is read-only and does not include editing or publishing actions

It also helps if you already know how Atloria presents public page context. If you have not reviewed that yet, read Understanding Public Document Views and Version Context first.

You do not need:

• An Atloria sign-in for public reading
• Admin access
• Project editing permissions
• Access to the private workspace

When reading across releases, keep these simple habits in mind:

• Check the version label before trusting the content
• Use the version switcher instead of changing the web address manually
• Expect some pages or navigation sections to differ between releases
• Use separate browser tabs when comparing the latest and archived documentation side by side

These basics are enough to follow the workflows in this guide and move through public versioned documentation with fewer mistakes.