## Understanding the technical reference landing page In Atloria, the **technical reference landing page** is the starting point for browsing structured reference content inside a project or in a published documentation view. If you already know how project and public reference views differ, use [Reading API Reference in Project and Public Views](doc:reading-api-reference-in-project-and-public-views) as a companion while you browse. At the top of the page, look for the **page title** and the short **introductory description**. These tell you which reference area you are in and what kind of content is grouped there. This opening text usually summarizes the section instead of showing every detail immediately. Below or beside that heading, Atloria presents the reference content as a set of **section links**, **entity links**, or grouped entries. Depending on the page layout, you may see: - A **left navigation panel** with section names - A main content area with **cards**, **lists**, or linked entry names - Short summary text under each entry - Visual grouping under a shared **section heading** The key thing to notice is the difference between an **overview page** and an **entity detail page**: - An **overview page** groups several related entries together - An **entity detail page** focuses on one specific entry Before opening an entry, you can usually identify: - The **entity name** - A brief **description** - Its place inside a broader **reference section** That preview helps you decide whether you only need to scan the section or open the full page. When you click into a dedicated entry, the **page heading** changes to that specific item, and the browser address also changes to reflect the new page. [SCREENSHOT: technical reference landing page showing page title, intro text, left navigation, and linked reference entries] ## Moving between reference sections When you want to switch from one part of the technical reference to another, use the navigation elements that stay visible around the content. In Atloria, this usually means the **left navigation**, a **reference index**, or links inside the page itself. The **left navigation** is the easiest place to start. It shows the larger reference structure and helps you move from broad topics to narrower ones. As you browse, pay attention to: - **Top-level section names** for major reference areas - **Nested items** under a section for more specific topics - The **highlighted or active item**, which shows where you are now - Expanded groups that reveal the current section’s child pages If the page includes **in-page section links**, you can use those to jump within the current section without leaving the page. This is useful when a section overview is long and contains several grouped areas. Some reference areas also include a **top-level index**. Use it when you want to step back and choose a different section entirely rather than moving one page at a time. This is especially helpful if you opened a detail page directly and want to reorient yourself. To move back up the hierarchy, check for **breadcrumbs** near the top of the page. Breadcrumbs let you return from a narrow subsection to the broader section that contains it. Parent links are useful when you know the current page is correct, but you want to see the larger group around it again. A good habit is to confirm your location before clicking further. Match these three things together: - The **active navigation item** - The **page title** - The **breadcrumb trail** When all three agree, you can move between sections without losing your place. ## Opening an entity detail page from an overview From a section overview page in Atloria, open a dedicated reference entry by selecting the linked **entity name** in a list, table, or card layout. The overview page is meant for scanning, so it usually shows only a short summary for each entry rather than the full reference. After you click an entry, confirm that the correct detail page has opened by checking a few visible cues: - The **page heading** now shows the specific entity name - The browser address changes to a more specific page - The page displays an **entity-specific summary** or metadata area - The surrounding navigation highlights the current entry or its parent section This matters because overview pages and detail pages serve different purposes. On the **overview page**, you typically see: - A grouped list of related entries - Short descriptions - Section-level context On the **detail page**, you are more likely to find the complete information for that one entry, such as: - Full definitions - Properties or members - Related items - Links to connected entries - Examples or structured subsections, if available If the page still looks like a list of multiple entries, you are probably still on the overview page. If the page focuses on one named item, you are on the dedicated detail page. To return without losing context, use whichever option is most visible: - The browser **Back** button - The **breadcrumb** link to the parent section - A **parent section** link on the page - The **left navigation** item for the overview [SCREENSHOT: overview page with one linked entity selected, followed by the entity detail page with updated title and breadcrumb] ## Reading relationships between overview pages and detailed entries The easiest way to understand technical reference browsing in Atloria is to think of it as a simple hierarchy: - A **technical reference section** - An **overview page** inside that section - One or more **entity detail pages** linked from the overview The **section** gives you the broad topic. The **overview page** acts like a directory for related entries. The **detail page** gives the full reference for one specific item. This structure helps you read efficiently. Stay on the **overview page** when you want to: - Scan what is available in a section - Compare several entries quickly - Find the right name before opening a full page - Understand how entries are grouped Open the **detail page** when you need exact information, such as: - A precise definition - A complete list of properties or members - Relationship details - Entry-specific examples - Links to closely related entries Overview pages are not meant to replace detail pages. They help you narrow your search. If you need complete reference information, click through to the dedicated entry instead of relying on the summary text. You may also see **cross-links** between related entries. These links let you move directly from one detail page to another connected page without returning to the section overview first. That is useful when you are tracing how two entries relate to each other inside the same reference area. To stay oriented while following those links, keep checking: - The **breadcrumb trail** - The **page title** - The **section label** in navigation If you need a refresher on how individual reference entries are structured, see [Understanding Entity Detail Pages in Technical Documentation](doc:understanding-entity-detail-pages-in-technical-documentation). ## Using page elements to stay oriented while browsing Atloria gives you several on-screen cues that help you keep track of where you are while moving through technical reference content. Use these cues together instead of relying on only one. Start with the **breadcrumbs** near the top of the page. Breadcrumbs show the path from the broader reference area to the page you are currently reading. They are especially helpful after following several related links. Pair that with the **page title**, which confirms the current section or entity, and the **section label** shown in navigation. The **left navigation** provides another important clue. Watch for: - Which section is **expanded** - Which item is **highlighted** - Whether the current page appears under a broader parent group An expanded navigation tree tells you which section contains the page you are viewing. If you open a detail page and the parent group remains open, that is a quick sign that you are still in the same reference branch. On longer entity pages, Atloria may show **in-page anchors** or a **table of contents**. Use these links to jump directly to parts of the page instead of scrolling through everything. Depending on the page, these links may point to areas such as: - Definitions - Members or properties - Relationships - Examples You may also notice **related links**, **previous** or **next** links, or a **parent reference** link. Treat these as navigation aids. They help you move through connected content, but they do not mean you have left the technical reference area. When the page starts to feel unfamiliar, pause and compare: - The **breadcrumb path** - The **current page heading** - The **active item in the side navigation** Those three elements usually tell you exactly where you are. ## Fixing common navigation problems in the reference If a reference link opens a page you did not expect, first check the visible page markers instead of guessing. In Atloria, compare these items right away: - The **section heading** - The **breadcrumb trail** - The **page title** If the page title names a different entry than the one you meant to open, you likely followed a related link or selected a similarly named item from another section. The breadcrumb trail will usually reveal that immediately. When you lose your place in the hierarchy, use the fastest route back to a familiar point: - Click a **breadcrumb** to return to the parent section - Reopen the correct branch in the **left navigation** - Go back to the **technical reference index** or section landing page If an overview page does not show enough detail, that is usually expected. Overview pages summarize entries; they do not replace the full reference page. Open the linked entity entry to see the complete information for that item. Similarly named entries can be confusing. To confirm whether two entries are actually different, compare: - Their **parent section** - Their **page heading** - Any visible **metadata** or summary block on the page Two entries may share a similar name but belong to different parts of the reference. The parent section is often the quickest way to tell them apart. If you have been moving through project and public views and are unsure whether the layout change is affecting what you see, revisit [Using API Reference Pages in Published and Project Views](doc:using-api-reference-pages-in-published-and-project-views). A practical recovery pattern is: - Return to the **parent section** - Reconfirm the **active navigation item** - Open the entity again from the correct overview page That usually gets you back on track without restarting your search. ## Overview When you browse technical reference content in Atloria, the main goal is to understand how **section pages**, **overview pages**, and **entity detail pages** fit together. The landing page or section page gives you the broad category. The overview page helps you scan related entries. The detail page gives you the full information for one specific item. Keep these browsing patterns in mind: - Use the **page title** and **introductory description** to understand the current reference area - Use the **left navigation** and **breadcrumbs** to move between broader and narrower pages - Open a linked **entity name** when you need more than the short summary shown on an overview page - Check the **page heading** and browser address after opening a detail page to confirm you are in the right place - Use **related links** and **parent links** to move through connected entries without losing the larger context The most useful distinction is simple: - **Overview pages** are for scanning and choosing - **Detail pages** are for exact reference reading If you are still building confidence with the overall reference layout, it helps to pair this guide with [Managing Technical Documentation Browsing Inside Projects](doc:managing-technical-documentation-browsing-inside-projects) and [Reading API Reference in Project and Public Views](doc:reading-api-reference-in-project-and-public-views). Those guides explain where these pages appear and how the browsing experience changes depending on where you opened the documentation. Once you are comfortable moving between section overviews and entity pages, continue with [Using Technical Reference Pages During Documentation Work](doc:using-technical-reference-pages-during-documentation-work). ## Prerequisites Before this browsing flow makes sense, you should already be comfortable opening technical documentation in Atloria and recognizing the difference between project-based and published reading views. You do not need advanced setup or admin access for this topic, but you should know how to reach a technical reference area and move around basic documentation navigation. You are ready for this guide if you can already do the following: - Open a project’s documentation workspace or a published documentation view - Recognize the **left navigation**, **page title**, and **breadcrumb trail** - Open an API or technical reference section from the documentation menu - Read a linked reference entry without confusing it with regular document pages It also helps if you already understand the basics covered in these related guides: - [Reading API and Technical Reference Pages](doc:reading-api-and-technical-reference-pages) - [Exploring API Reference Sections Inside Projects](doc:exploring-api-reference-sections-inside-projects) - [Viewing Technical Entities and Related Reference Details](doc:viewing-technical-entities-and-related-reference-details) If you have not worked with project and public reference views yet, review [Reading API Reference in Project and Public Views](doc:reading-api-reference-in-project-and-public-views) first. This guide assumes you already know how to enter those views and want to focus specifically on browsing within the reference hierarchy. You do **not** need to use Atloria’s admin screens, analytics area, or security pages for this task. The only things you need are access to documentation that includes technical reference content and enough familiarity with Atloria’s navigation to move between sections, overview pages, and detailed entries.