Finding Content Through Public Documentation Structure

Understanding How Published Docs Are Organized

In Atloria’s published documentation, you move through a structured reading experience rather than an editing workspace. You are not expected to create pages, change settings, or use project tools here. Instead, you read through a public documentation site that is organized into sections, pages, and headings.

At the highest level, readers usually begin on a documentation home page or a category landing page. These top-level areas group related topics together so you can start broad and narrow down. A category might contain a parent page that introduces the topic, followed by child pages that cover specific tasks or detailed explanations. When a section contains multiple layers, the navigation shows that hierarchy so you can tell which pages belong under the same topic.

Inside an individual page, Atloria also helps you move through the content with heading-based navigation. This on-page table of contents is different from the main sidebar. The sidebar helps you move between pages and categories. The table of contents helps you jump to a section within the page you are already reading. If you want another topic, use the sidebar. If you want another section on the same page, use the table of contents.

You can also confirm your location by checking visible page cues:

• The page title at the top
• Section headings inside the page
• The surrounding page hierarchy in the navigation
• Any breadcrumb-style location trail shown above the content

These cues work together. If the title says one thing but the headings focus on something else, you may be on a broader parent page instead of the exact task page you need.

If you already worked through Managing Reader Navigation in Published Documentation, think of this guide as the next step: using that structure to locate the exact page more quickly.

Browsing Categories from the Main Documentation Navigation

When you want to find a topic in Atloria’s published docs, start with the main documentation navigation rather than scrolling through random pages. The left navigation area or primary sidebar is where related content is grouped into categories. This is the fastest way to move from a broad subject to a specific page.

1. Open the published documentation home page or any page in the docs site.
2. Look at the left sidebar for the main category list.
3. Select a category that matches your goal as closely as possible.
4. Expand that category to reveal child pages or nested sections.
5. Keep opening deeper levels until you see page titles that match the task you want.

As you expand the navigation tree, pay attention to how page names are written. Some labels signal broad orientation pages, while others clearly point to a task. For example:

• Broad pages often use wording like “Understanding,” “Overview,” or a category name by itself.
• Task pages usually begin with action words such as “Using,” “Managing,” “Creating,” “Configuring,” or “Reviewing.”
• Reference-style pages often focus on a specific content type, screen, or detailed reading topic.

This matters because a category landing page may help you understand the section, but it may not answer a specific question. If you need instructions, continue into the child pages under that category instead of stopping at the first matching title.

Expanded navigation is especially useful when several topics look similar. Rather than backing out to the documentation home page each time, stay inside the same branch and compare nearby pages. If one page feels too general, the next level down often contains the exact task-focused page you need.

Following the category hierarchy in this way helps you stay oriented. You always know whether you are still in the same topic area or whether you have moved into a different part of the documentation set.

Using the Table of Contents to Scan a Page Quickly

Once you open a page in Atloria’s published docs, the fastest way to judge whether it contains the answer you need is the on-page table of contents. This area is built from the page’s section headings and gives you a quick preview of what the page actually covers.

Before reading the full page, scan the table of contents and compare the heading names with your question. If you are looking for a specific task and the headings focus on background or general explanation, you may be on the wrong page. If the headings match the steps or concepts you expected, stay on the page and jump directly to the section you need.

1. Open the page from the sidebar navigation.
2. Find the table of contents near the page content.
3. Read the heading names from top to bottom.
4. Select a heading to jump straight to that section.
5. Use the table of contents again whenever you need to move to another section on the same page.

This is especially useful on long pages. Instead of scrolling back and forth, you can move directly between sections such as setup details, workflow steps, and related reading areas. If you are comparing parts of the same page, the table of contents becomes your shortcut for repeated movement.

The heading names also help you decide whether to stay on the page or return to the surrounding category. For example:

• If the headings describe a complete workflow, the page is likely task-focused.
• If the headings explain ideas or definitions, the page is likely conceptual.
• If the headings break down items, fields, or detailed structures, the page may be more reference-oriented.

When the heading you need is missing, that is a strong sign to check a sibling page in the same category rather than forcing your way through unrelated content.

Using the table of contents this way turns each page into a quick decision point: read here, jump within the page, or return to nearby pages in the same branch.

Choosing the Right Page from Titles, Headings, and Navigation Cues

In Atloria, the best way to confirm that you are on the right page is to compare several visible cues together instead of relying on the page title alone. A title may place you in the correct topic area, but the headings and surrounding navigation tell you whether the page is the exact match for your goal.

Start with the page title at the top of the content area. Then compare it with the label highlighted in the sidebar. If both match, you know which page you opened. Next, look at the section headings or the table of contents. These show what the page actually covers in detail.

Use these cues to judge the page type:

• A page with broad headings is often a parent topic or orientation page.
• A page with action-based headings usually supports a task or workflow.
• A page with tightly focused headings often serves as a detailed reading or reference page.

The surrounding navigation gives even more context. Check:

• The parent category above the current page
• Nearby pages in the same expanded branch
• Nested items under the same section
• Any breadcrumb-style trail shown above the content

These clues help when two pages have similar names. One may be an introduction, while another may be the practical page you actually need. For example, a broader page may explain how a documentation area is organized, while a neighboring page may show how to complete a specific reading task inside that area.

Consistent heading structure also helps you understand where you are in the full documentation set. If the page begins with orientation sections and then moves into detailed task sections, you may be on a parent page. If it starts immediately with direct instructions, you are more likely on the right destination.

When these cues line up, you can move forward confidently. When they do not, use the current branch in the navigation to check the closest related pages before leaving the topic area entirely.

Moving Between Related Pages Without Losing Your Place

When you browse published docs in Atloria, you do not need to restart from the documentation home page every time a page is close but not quite right. The easiest approach is to move within the same navigation branch so you can compare related pages while keeping your place in the overall structure.

1. Start on the current page and check the table of contents for the section you need.
2. If the heading is missing, look back to the left navigation.
3. Use the expanded category branch to open a nearby page in the same section.
4. If you need a broader explanation, return to the parent category or parent page.
5. Watch which page stays highlighted so you always know your current location.

This approach works well because related pages usually sit next to each other in the same branch. If one page is too broad, a child page may be more specific. If one page is too narrow, the parent category may give you the context you need before you continue.

The sidebar is especially helpful here. Keep an eye on:

• Which category is expanded
• Which page is highlighted
• Which neighboring pages appear above and below the current page
• Whether the current page sits under a parent topic with additional child pages

If Atloria shows a breadcrumb-style trail above the content, use it when you want to step back one level without losing the section you were exploring. This is often faster than collapsing and reopening categories in the sidebar.

A good habit is to use the table of contents first and the sidebar second. That keeps you on the current page when the answer is already there. Only switch pages when the heading structure shows the content is missing.

By moving this way, you stay inside the same topic area, compare pages more easily, and avoid the common problem of losing your place after several clicks.

Fixing Common Problems When You Can't Find the Right Page

Sometimes a page in Atloria looks promising at first, but once you open it, the content is either too broad, too narrow, or focused on a different question. When that happens, use the visible structure of the published docs to recover your place instead of starting over.

If a category feels too broad, the usual fix is to expand deeper levels in the navigation tree. A top-level category often contains several child pages, and those child pages may contain even more specific subpages. Keep opening the branch until you reach individual task pages rather than stopping at the first category label that sounds familiar.

If the current page seems related but does not include the section you need, check the on-page table of contents. This is the quickest way to confirm whether the missing topic is actually covered. If the heading is not listed, return to sibling pages in the same category. Staying in the same branch is usually faster than jumping to a completely different section.

When page titles are similar, use multiple clues together:

• Compare the page title with the highlighted sidebar label
• Check the breadcrumb-style hierarchy
• Read the first few section headings
• Scan the table of contents for task wording versus general explanation

This helps you tell the difference between an introductory page and a detailed how-to page.

If you lose your place while browsing, simplify the navigation view. Collapse unrelated categories so only the branch you are using stays open. Then look for the highlighted current page in the sidebar. That highlight is your anchor point. From there, you can move up to the parent page or sideways to a sibling page without guessing.

These small adjustments make a big difference. Most “I can’t find it” moments are really navigation-structure problems, and Atloria’s category tree, page headings, and current-page highlight usually give you enough information to get back on track.

Overview

• This guide focuses on how to find the right page in Atloria’s published documentation by using visible structure rather than search or editing tools.
• You use two different navigation aids for two different jobs:
  • The sidebar or category navigation helps you move between sections and pages.
  • The table of contents helps you move within the page you are already reading.
• The most reliable way to confirm you are in the right place is to compare:
  • The page title
  • The highlighted page in the sidebar
  • The section headings
  • The breadcrumb-style hierarchy, if shown
• When a page is close but not exact, stay in the same navigation branch and compare nearby sibling pages before leaving the topic area.
• If you lose your place, use the expanded category state and the highlighted current page in the sidebar to reorient yourself quickly.

This guide builds on Managing Reader Navigation in Published Documentation by showing how to use that navigation structure to pinpoint the page you actually need.

Prerequisites

• You should already be viewing a published documentation site in Atloria.
• You should be comfortable opening pages from the public navigation sidebar.
• It helps to understand the basic public reading experience covered in:
  • Using Public Navigation to Browse Documentation
  • Browsing Published Documentation and Finding the Right Page
• If your documentation uses audience-specific navigation, you may also want to review:
  • Using Public Navigation with Audience Specific Content

For the next step, continue to Finding and Reading Content in Published Documentation.