Reading Audience Tailored Documentation

Opening Documentation in the Right Audience Context

When you open published documentation in Atloria, you may arrive in a general public view or in a view already tailored to a specific audience. This usually depends on how you entered the docs. A reader might start from the published documentation home page, click an audience-specific link shared by a Documentation Manager, or choose a path from public navigation after the site loads. If you planned these paths earlier, the setup described in Planning Audience Specific Release Views is what makes those entry points possible.

As soon as the page opens, look at the top area of the page for signs of the active audience context. In Atloria, this can appear as an audience label, a selected audience name in a switcher, or navigation that already reflects one audience path instead of the full public set of pages. If the page title and surrounding navigation feel narrower than the full site, you are likely already reading in a filtered audience view rather than the default public view.

The difference matters. The default public view is the broadest reading experience available to public visitors. An audience-tailored view narrows what you see so the page, navigation, and supporting guidance match a specific reader group. That can affect which pages appear in the sidebar, which notes show inside an article, and which examples are visible on the page.

Documentation Managers publish these audience-ready public views so readers can open them directly without signing in. If a public page has been prepared for a specific audience, you can read it from the published documentation site just like any other public page.
[SCREENSHOT: published documentation page showing page header with active audience label or switcher]

Following an Audience Path Through the Docs

1. Start on the published documentation home page in Atloria. Look for the audience selector, an audience-based landing choice, or navigation links that clearly point to a specific reader path.

2. Choose the audience that matches what you need to read. After you select it, open a section from the main page, sidebar, or featured links area. The page should load with navigation that reflects that audience instead of showing every available topic.

3. Check the left navigation, table of contents, or breadcrumb trail as you move deeper into the docs. These page elements help confirm that you are still following the same audience path. If the selected audience is active, the surrounding structure should stay consistent with that choice.

4. Continue opening related pages from links inside the article or from the sidebar. In a well-structured audience path, those links continue to surface content that belongs to the same audience view. You should not need to reselect the audience on every page if the public docs are set up correctly.

5. Watch for shared pages. Some articles are meant for everyone, so they may appear in more than one audience path with little or no visible change. Other pages may show different guidance, examples, or notes depending on the selected audience. If the article stays the same but the surrounding navigation still reflects your audience, you are likely on shared content.

This is especially useful when you want to read a sequence of pages without constantly checking whether you have drifted into a broader public view. The breadcrumb, sidebar, and page-to-page links are your best cues for staying inside the intended path.
[SCREENSHOT: documentation home page with audience choice and sidebar updating after selection]

Reading Tailored Content on a Page

Once you are inside an audience path, the article itself may change. In Atloria, audience-tailored content can appear as special callouts, audience-only notes, tabs with different guidance, banners, or full sections that show only when a certain audience is active. These changes are part of the reading experience, so pay attention not just to the page title but also to what appears between headings.

A common pattern is shared page structure with tailored details inside it. The main heading may stay the same for all readers, while examples, instructions, or inline guidance shift to match the selected audience. For example, one audience might see a more introductory explanation, while another sees more advanced operational guidance on the same page. If you notice a section that appears in one audience view but disappears after switching audiences, that is a sign the content is intentionally filtered.

Hidden content is handled by simply not showing it to public readers outside the intended audience. You do not see blocked placeholders or internal editing markers. Instead, Atloria presents only the material that belongs in your current reading context. That keeps the page cleaner and avoids mixing instructions meant for different reader groups.

Look for visual cues that separate shared content from tailored content. These may include an audience label near a note, a banner tied to the active audience, or a section that changes while the rest of the article remains unchanged. When only part of the page shifts after an audience change, that usually means the article contains both shared content and audience-specific content together.

If you want to confirm what changed, switch audiences and compare the same heading, note, or example block rather than scanning the whole page at once.
[SCREENSHOT: article page with shared headings and an audience-specific callout or section]

Checking That You Are in the Correct Reading View

1. Look near the page title or top header for the active audience name. In Atloria, this may appear as an audience badge, a selected value in the audience switcher, or another clear label showing which reader view is active.

2. Confirm the path around the article. Use the breadcrumb, section navigation, or page metadata to make sure the page belongs to the audience path you intended to follow. If the surrounding navigation looks too broad or unrelated, you may be in the default public view instead of a tailored one.

3. Compare the page with another audience view. Open the audience selector and switch to a different audience while staying on the same page if that option is available. Then watch for changes in notes, examples, banners, and section visibility. Even small changes can confirm that audience filtering is working.

4. Reload the page after selecting the audience. If the same audience label and the same tailored sections appear again, the view is loading consistently. This is a quick way to confirm that the audience context is not temporary.

5. Reopen the page from an audience-specific link if one was shared with you. When the page opens with the same audience already selected, you can be more confident that you are reading the intended public version.

This check is especially helpful before sharing a page with teammates or using the content in training, onboarding, or release communication. If the audience name, breadcrumb, and visible content all align, you are in the correct reading view.
[SCREENSHOT: page header showing audience badge next to title and breadcrumb below]

Switching Audiences Without Losing Your Place

1. Open the audience switcher on the current page. If Atloria supports the same article across multiple audiences, you can change the selected audience and stay on the current article instead of going back to the documentation home page.

2. After switching, look at the page title, audience label, and body content. If the article exists for the newly selected audience, the page stays in place while the tailored sections, notes, examples, or navigation update to match the new context.

3. If the article is not available for the audience you selected, Atloria may move you to a fallback view. Depending on how the public docs were published, this can mean showing shared content, opening a related page, or returning you to an audience landing page where you can choose another section.

4. Check in-page navigation after the switch. If the article includes anchor links, tabs, or a table of contents, make sure those still match the visible sections. When audience-specific sections disappear, some in-page links may also change because the page structure has been updated for the new audience.

5. Continue browsing to another page and confirm the audience remains selected. Atloria may preserve the chosen audience through the page address or through a saved reading preference, which helps keep the same context across multiple pages.

Switching audiences is most useful when you need to compare how the same topic is presented to different reader groups. Stay focused on one article at a time and watch what changes in the header, navigation, and content blocks after each switch.
[SCREENSHOT: audience switcher opened on an article page with current article retained after selection change]

Fixing Common Problems with Audience-Specific Views

If the audience view does not look right, start with the most visible clues on the page.

• Audience label is missing or incorrect

  • Reload the page and check the header again.
  • Open the audience switcher and reselect the intended audience.
  • Confirm that you opened a published public page, not a private workspace view.
  • If you used an old bookmark or copied link, reopen the page from the published documentation home page and choose the audience again.

• Expected tailored section does not appear

  • Check whether you are on a shared page. Some pages are intentionally the same across multiple audiences.
  • Switch to another audience and compare the same area of the article.
  • Look for changes in callouts, examples, tabs, or banners rather than expecting the whole page to change.
  • If nothing changes, return to the audience path entry page and reopen the article from there.

• Navigation shows the wrong pages

  • Go back to the audience landing page or documentation home page.
  • Reset the audience selection and choose the correct path again.
  • Reopen the section from the updated sidebar or navigation menu so the table of contents rebuilds around the right audience.

• A shared link opens the wrong context

  • Check whether the page address includes audience-specific details that may have been removed when the link was copied.
  • Reopen the page from the intended audience path instead of from a general public page.
  • After the correct audience loads, use that version of the link when sharing.

If you are reviewing a public reading experience before launch, the next guide, Reviewing Public Audience Pages Before Launch, walks through how to validate those pages more systematically.

Overview

• Atloria lets public readers open documentation in a general public view or in an audience-tailored view.
• The active audience is typically confirmed through the page header, an audience label, a selected audience switcher value, or navigation that reflects a specific audience path.
• Audience paths affect more than just the page list. They can also change breadcrumbs, section links, examples, callouts, and other guidance inside an article.
• Shared pages may appear in multiple audience paths with little change, while tailored pages can show different sections or hide content entirely depending on the selected audience.
• You can usually verify the correct reading view by checking the audience name near the page title, reviewing the breadcrumb trail, and comparing the same page across different audience selections.
• When Atloria supports it, switching audiences keeps you on the same article so you can compare how the content changes for different reader groups.
• If something looks wrong, the fastest fixes are to reload the page, reselect the audience, return to the audience landing page, and reopen the article from the correct public path.
• For planning decisions behind these reading experiences, refer back to Planning Audience Specific Release Views.

Prerequisites

• You need access to a published Atloria documentation site that has already been prepared for public reading.
• The documentation should include at least one audience path, audience selector, or audience-specific navigation option.
• It helps to know which audience you are trying to read as, especially if the same project includes shared pages and tailored pages.
• If you are comparing views, have a page open that is known to contain audience-specific notes, examples, tabs, or sections.
• If a Documentation Manager shared a direct public link for a specific audience, keep that link available so you can confirm it opens the correct reading context.
• For background on how these audience experiences are designed before publication, see Planning Audience Specific Documentation Experiences and Reviewing Audience Specific Pages in Public Documentation.