# Understand the Atloria Monorepo

This page helps you understand how the Atloria monorepo is organized and how its major areas work together. This context helps you make informed administrative decisions when reviewing technical documentation, infrastructure information, and generated documentation outputs.

## Overview

The Atloria monorepo brings multiple Atloria applications and supporting areas together in one managed workspace. Rather than treating the public website, authenticated application experience, documentation processing, code analysis, and screenshot capture as unrelated systems, the monorepo organizes them as coordinated parts of the Atloria platform.

As a technical administrator, you will most often use this understanding when you need to identify where a feature belongs, review generated technical documentation, or determine which part of the platform is responsible for a problem. For example, user-facing account access belongs with the sign-in, registration, password reset, invitation, and single sign-on experiences. Publicly shared documentation belongs with the public documentation experience, while analysis and capture activities support the documentation generation process behind the scenes.

Atloria documentation also classifies discovered material into categories that move from **FRONTEND** through **BACKEND**, **DATABASE**, **API SCHEMA**, **CONFIG**, **DOCUMENTATION**, and **INFRASTRUCTURE**. This sequence is useful when you review a technical documentation set because it presents the system from the user-facing layer through the supporting platform layers.

> 📷 _Screenshot pending: The Technical Docs area showing available documentation categories and navigation options._

## Prerequisites

Before reviewing the Atloria monorepo structure, make sure you have:

- Access to the Atloria administrator experience appropriate to your organization.
- Permission to view **Technical Docs** and, where applicable, **Infrastructure** information.
- A basic understanding of your organization’s Atloria deployment, including whether you use single sign-on, invitations, or public documentation sharing.
- Access to the documentation workspace or exported documentation provided by your Atloria implementation team.
- A clear review goal, such as validating an architecture overview, locating documentation gaps, or checking infrastructure coverage.

## Step-by-Step Instructions

1. **Open the technical documentation area.**

   From the available Atloria navigation options, select **Technical Docs**. This is the starting point for reviewing documentation that explains how the platform is arranged and how its major areas relate to each other.

   If your workspace presents an overview entry, select **Overview** or **📊 Overview** first. The overview helps you understand the breadth of the documented system before you focus on an individual area.

2. **Start with the platform structure.**

   Select **Structure** when it is available. Use this view to orient yourself around the logical areas of the monorepo rather than beginning with a single feature or issue.

   Focus first on the distinction between:
   - The user-facing Atloria experience, including authentication and public documentation access.
   - The administrative and operational experience, including enterprise analytics and operational views.
   - The supporting documentation-processing capabilities, such as analysis, orchestration, and screenshot capture.
   - The platform-level areas represented by configuration and infrastructure documentation.

   This approach matters because a feature may involve more than one area. A public documentation page, for example, can depend on both the public presentation experience and the documentation content that was generated or imported.

3. **Review documentation by category.**

   In the technical documentation content, review categories in the order in which they are presented:

   1. **FRONTEND**
   2. **BACKEND**
   3. **DATABASE**
   4. **API SCHEMA**
   5. **CONFIG**
   6. **DOCUMENTATION**
   7. **INFRASTRUCTURE**

   This order gives you a practical path for understanding a feature. Begin with what users see, then follow the supporting services and data, and finally review the configuration and infrastructure required to operate it.

   For infrastructure-specific information, select **Infrastructure** or **🔐 Infrastructure Security** where available. Use these sections when your review concerns hosting, security posture, operational dependencies, or deployment-related responsibilities.

4. **Use Atloria Stack information to connect the layers.**

   Select **Atloria Stack** when you need a cross-platform view. This helps you recognize that user actions in one area can be supported by processes elsewhere in the monorepo.

   For example, the platform includes experiences for logging in, registering, resetting passwords, completing single sign-on, and accepting invitations. It also provides public documentation views that can be opened through shared documentation links. Supporting platform areas analyze source material and capture screenshots so documentation can reflect the actual user experience.

5. **Review relationships, not only categories.**

   When technical documentation describes relationships, use it to understand how one documented item supports another. Relationship descriptions may show that a user interface component renders another component, uses a hook or context, calls an API, depends on a service, or queries a model.

   You do not need to trace implementation details to benefit from these relationships. Instead, use them to answer administrative questions such as:
   - Which areas may be affected by a change?
   - Does a user-facing screen rely on a shared platform capability?
   - Is a documentation gap limited to one category, or does it affect several layers?

6. **Save or export your reviewed structure when needed.**

   If you are arranging or confirming the documentation organization, use **Save Structure** to preserve your changes. If you need to circulate the documentation outside Atloria, select **Export Documentation**.

   If your organization already has material to bring into Atloria, use **Or import existing documentation** instead of recreating content manually. After importing or reviewing source material, **Generate Documentation →** can be used to produce documentation outputs for review.

> 📷 _Screenshot pending: The Structure or Atloria Stack view showing how user-facing, documentation, and infrastructure areas are grouped._

## Tips and Best Practices

- **Review from the user experience inward.** Start with **FRONTEND** documentation and continue through backend, data, configuration, and infrastructure. This makes technical documentation easier to connect to real user outcomes.

- **Treat public and authenticated experiences separately.** Public documentation sharing, user invitations, login, registration, password reset, and single sign-on serve different audiences and may have different administrative requirements.

- **Use relationship information for impact assessment.** A relationship such as “calls API,” “uses service,” or “depends on” signals that a change or issue may extend beyond the screen or item you are currently reviewing.

- **Keep technical documentation and user manuals distinct.** Atloria supports both technical documentation and user-facing manuals. Technical documentation explains platform structure and dependencies; user manuals explain the actions people take on screen. Review the correct document type for your audience.

- **Check documentation coverage across all categories.** A complete technical review should not stop at application behavior. Include **CONFIG**, **DOCUMENTATION**, and **INFRASTRUCTURE** so operational dependencies are visible.

## Related Pages

- [Review Technical Docs](#)
- [Use the Atloria Stack View](#)
- [Manage Infrastructure Security Documentation](#)
- [Generate Documentation](#)
- [Import Existing Documentation](#)
- [Export Documentation](#)
- [Understand User Manuals and Technical Documentation](#)

## Troubleshooting

### You cannot find the Technical Docs area

Your account may not have the required access, or your organization may not have enabled the relevant documentation workspace. Confirm that you can access **Technical Docs** and ask an Atloria administrator to verify your permissions.

### The documentation does not include an expected category

Review whether the missing information belongs under **FRONTEND**, **BACKEND**, **DATABASE**, **API SCHEMA**, **CONFIG**, **DOCUMENTATION**, or **INFRASTRUCTURE**. If it is absent across these categories, import existing material using **Or import existing documentation** or generate updated content with **Generate Documentation →**.

### You are unsure whether to use technical documentation or a user manual

Use **Technical Docs** when you need to understand platform structure, dependencies, configuration, or infrastructure. Use user manuals when you need instructions for completing a task through visible screens, fields, menus, and buttons.