Browsing Published Documentation and Finding the Right Page

Opening a Published Documentation Site

When you open a published Atloria documentation site, you are in a public reading view rather than an editing workspace. You do not need to sign in just to browse published pages. The screen is built for reading, so the main things to look for are the page title, the navigation areas, and the article content itself.

Most published documentation views in Atloria are easy to recognize because the page is arranged around a few clear reading regions:

• A top navigation area for moving between major sections
• A left-side navigation menu or category list for browsing pages in the current section
• A main content area where the full article appears
• A breadcrumb trail, when available, showing where the current page sits in the structure

A published site may first open on a landing page. A landing page usually introduces the documentation set and helps you choose where to start. It may contain a large title, short introductory text, and links into major sections. An individual documentation page is different: it focuses on one topic and shows the full article with headings and sections.

Use the page title and opening paragraph to confirm you are in the right place. If you see article-style content, section headings, and public navigation menus, you are likely in the published documentation view. If you were expecting to read documentation but instead see project setup, admin areas, or editing tools, you are not on the public reading side.

If you need a refresher on basic public browsing before choosing pages in more detail, see Using Public Navigation with Audience Specific Content.

Moving Through Categories and Navigation Menus

The fastest way to browse a published Atloria site is usually the left-side navigation. This area groups pages into sections so you can move from broad topics to more specific ones without opening every page one by one.

1. Start with the left navigation menu and look for section names that match your goal. These might represent broad topic areas such as getting started, project work, publishing, or reader help.
2. If a section contains subtopics, expand that group to reveal the pages underneath it. This helps you narrow the list before opening an article.
3. Collapse groups that are not relevant so the menu becomes easier to scan.
4. Click a page title to open it in the main content area.
5. If the site includes several major published areas, use the top navigation links to switch between them before returning to the left-side menu.

As you move around, pay attention to visual cues that show your current location. Atloria commonly highlights the page you are reading in the navigation menu. The parent category may also appear active or expanded, which helps you understand the section you are currently inside.

This is especially useful when several pages have similar names. For example, a page listed under a setup section usually serves a different purpose than a page with a similar title under a troubleshooting or policy section. The category around the page title gives you important context before you even open it.

When the menu feels crowded, do not try to read every title at once. Focus first on the category labels, then on the smaller list of pages inside the section that looks most relevant. That approach is usually faster than scanning the entire navigation tree from top to bottom.

Choosing the Right Page to Read

Finding the right page in Atloria is mostly about matching your task to the page title and its place in the documentation structure. Before opening several pages at random, compare the titles in the navigation menu and look for wording that matches what you are trying to do.

1. Read the page titles in the current category and look for direct task language. Titles that begin with words like “Creating,” “Managing,” “Using,” or “Reviewing” are often task-focused pages.
2. Use the category name to judge the page’s purpose. Pages near the top of a section are often introductory, while lower or nested pages are more specific.
3. Open the page that seems closest to your goal.
4. Scan the page heading, the first paragraph, and the visible section headings.
5. If the page is too broad, too advanced, or about a different workflow, return to the navigation menu and choose a nearby page in the same section.

This quick scan saves time. In many cases, the opening paragraph tells you whether the page is about setup, day-to-day use, administration, or published reading. The section headings help even more. If you are looking for instructions and the page only shows background information, move on quickly.

Breadcrumbs are also helpful here. If the breadcrumb path shows that the page sits under the wrong branch, you can tell immediately that you may have landed in a related but different topic. For example, a page under a broad reader section may not answer the same question as a page under a project-specific section.

A good habit is to compare three things together before settling on a page:

• The page title
• The category or parent section
• The visible section headings inside the article

When all three line up with your task, you have probably found the right page.

Orienting Yourself While Reading a Page

Once you open a page, staying oriented matters just as much as finding it. Atloria gives you several clues that help you understand where you are in the documentation and how the current article relates to the rest of the site.

1. Check the page title at the top of the article to confirm the topic.
2. Look at the breadcrumb trail, if shown, to see the path from the broader section to the current page.
3. Glance at the left navigation menu and note which page is highlighted and which category is expanded.
4. Use the article’s section headings to understand how the content is organized before reading every paragraph.
5. If a table of contents or heading list appears on the page, use it to jump directly to the section you need.

These elements work best together. The page title tells you what you are reading now. The breadcrumb trail tells you how you got there. The highlighted navigation item shows what sits next to it in the same section. When all three point to the same topic branch, you can read with confidence that you are in the right place.

For long pages, do not rely only on scrolling. Instead, pause at the heading structure. Headings break the article into smaller tasks or concepts, so you can skip directly to the part that answers your question. This is especially helpful when a page covers both basic and advanced material.

If the article turns out to be too broad, use the side navigation to move to a neighboring page in the same category. If it is too advanced, go up one level through the breadcrumb trail or choose a more introductory page nearby.

Using Search and Page Context to Find Answers Faster

When browsing by category is too slow, use the search field if the published Atloria site provides one. Search works best when you enter the exact feature name, a clear task phrase, or the page title you expect to find.

1. Click the search field and enter a specific term.
2. Start with the most obvious wording, such as a feature name or task name.
3. Review the search results list and compare the page titles.
4. Use the short surrounding text shown with each result to tell similar pages apart.
5. Open the most likely result and confirm it by checking the page heading, category placement, and nearby navigation items.

Search results are most useful when you read them in context. A familiar title alone is not always enough, especially if several pages use similar words such as “managing,” “using,” or “reviewing.” The surrounding text often reveals whether the page is about setup, navigation, permissions, publishing, or another workflow.

If your first search returns too many results, make the wording more specific. Instead of searching for a broad word like “version,” try a phrase such as “version visibility” or “review status.” If you know the exact wording used in Atloria’s navigation or page titles, use that wording in the search box.

You can also combine search with navigation. After opening a result, check the left-side menu to see what related pages sit above and below it. Sometimes the result gets you close, and a neighboring page in the same section turns out to be a better match.

This approach is often faster than repeating new searches over and over, especially when you already know the general topic area but need the exact page.

When You Cannot Find the Page You Need

Sometimes the issue is not that the page is missing, but that you are looking in the wrong published site area or following the wrong topic branch. When that happens, use the visible page context in Atloria to reset your path instead of continuing to click deeper at random.

• Check the site title and the top-level navigation labels first. These help confirm that you are browsing the correct published documentation set.
• Look at the breadcrumb trail to see whether the current page belongs to the topic branch you expected.
• Review the highlighted page and its surrounding items in the left navigation. Related pages are often grouped together under the same parent section.
• Try a nearby category if the page is not where you expected. Some task pages are filed under a broader section rather than under the exact feature name you had in mind.
• Use both navigation browsing and search. Some readers find pages faster by scanning categories, while others find them faster by entering the page title or task phrase.

If a link opens an unexpected page, do not start over from the beginning right away. First, use the breadcrumb trail to move up one level, then review the expanded category in the side navigation. That usually shows whether you are close to the right page or in the wrong section entirely.

It also helps to compare the current page’s title with the titles around it. If the neighboring pages all focus on a different kind of task, switch categories rather than continuing in the same branch.

When you need a broader understanding of how public sections are organized before drilling into individual pages, continue with Managing Reader Navigation in Published Documentation.

Overview

This guide focuses on the public reading experience in Atloria and shows how to move from opening a published documentation site to identifying the exact page you need. The main idea is simple: use the visible reading tools on the page together instead of relying on only one of them.

Key parts of the published reading view include:

• The top navigation for moving between major published areas
• The left-side navigation for browsing categories and page lists
• The main article area for reading the selected page
• The breadcrumb trail for understanding where the page sits in the documentation structure
• The search field, when available, for finding pages by title, feature, or task

This document does not repeat the basics of public browsing already covered in Using Public Navigation with Audience Specific Content. Instead, it focuses on what to do after you have reached a published documentation site and need to choose the right page quickly.

Use this guide when you want to:

• Tell the difference between a landing page and a full article page
• Browse categories without getting lost in a long navigation tree
• Confirm whether a page matches your task before reading the whole article
• Stay oriented inside long pages using headings, breadcrumbs, and highlighted navigation
• Recover when a link or search result takes you to the wrong place

The most effective reading pattern in Atloria is to combine title, category, and page structure. If the page title matches your task, the category matches your topic, and the section headings match your question, you are usually on the right page.

Prerequisites

Before using the steps in this guide, make sure the following are true:

• You have access to a published Atloria documentation site
• You can open the site in your browser and view public pages
• You want to read documentation, not edit project content or manage internal workspace settings
• You are comfortable using common page elements such as menus, links, and search fields

You do not need to sign in just to browse published documentation. This guide is written for readers using the public documentation view.

It helps if you already know one of the following:

• The general topic you want to read about
• A feature name used in Atloria documentation
• A task phrase that matches what you are trying to do
• Part of the page title you expect to find

If you are still learning how public navigation works at a basic level, review Using Public Navigation with Audience Specific Content first. That guide explains how public-facing navigation behaves when documentation is organized for different reader groups.

You may also find this guide easier to follow when the published site includes these visible elements:

If one of these elements is not shown on a particular published site, you can still use the same approach by relying on the page title, nearby navigation items, and section headings inside the article.