# Start a Project Source Analysis

You can start a source analysis from a project workspace to prepare a connected codebase for documentation work. The analysis organizes the project’s source information so you can review relevant application areas before creating or updating documentation.

## Overview

Source analysis helps Atloria examine the connected project source and identify the parts that are useful for documentation. This can include user-interface areas, backend services, data-related elements, API definitions, configuration, documentation files, and infrastructure-related content.

Use this process when you have added a project and want Atloria to build context from its source before you work on technical documentation, user manuals, version reviews, or change documentation. Starting from the project workspace keeps the analysis associated with the correct project.

As analysis progresses, Atloria may process source content by category. Categories can include **FRONTEND**, **BACKEND**, **DATABASE**, **API SCHEMA**, **CONFIG**, **DOCUMENTATION**, and **INFRASTRUCTURE**. A completed analysis can finish successfully with no errors, or it can complete with warnings that you should review before relying on the results.

> 📷 _Screenshot pending: The Projects hub showing the project search field and available projects._

## Prerequisites

Before you start, make sure you have the following:

- Access to Atloria and permission to open the relevant project.
- A project that is already available in the **Projects** area.
- A connected project source or codebase associated with that project.
- The correct project selected, especially if you manage multiple projects.
- Time for source processing to complete before you begin documentation work.
- Access to the project’s **Source** area from the project sidebar.

## Step-by-Step Instructions

1. Open **Projects** from the Atloria application.

2. Use the **Search projects...** field if you need to locate a specific project.

3. Select the project whose source you want to analyze.

4. Confirm that you are in the focused project workspace rather than the all-projects hub.

5. Select **Source** in the project sidebar.

> 📷 _Screenshot pending: A focused project workspace with the Source item visible in the project sidebar._

6. Review the source information displayed for the connected project.

7. Start the available source analysis action in the **Source** area.

8. Wait while Atloria processes the project source.

9. Review the displayed processing status when the analysis finishes.

10. Continue to the project’s documentation area after the analysis reports completion.

If you need to leave the project workspace, select **← Back to Projects** to return to the project list. You can then select another project and repeat the process for its connected source.

## Tips and Best Practices

- Analyze one project at a time. This helps ensure that the documentation context you review belongs to the correct source and product area.

- Start analysis before generating or reviewing technical documentation. Source context is most useful when it is prepared before you open the project’s documentation workspace.

- Use the project sidebar to stay within the same project. After selecting **Source**, you can move to related project areas—such as analytics, versions, changes, or technical documentation—without switching projects.

- Allow the analysis to finish before treating its results as complete. A successful result indicates that processing completed with no errors. A completed result with warnings means the analysis finished, but some source details may need attention.

- Review the analysis broadly. Atloria can organize information across frontend, backend, database, API schema, configuration, documentation, and infrastructure categories. Do not assume that documentation-relevant behavior exists only in the frontend.

- Use source analysis as preparation, not as a substitute for review. When documenting a user workflow, confirm the visible labels, screens, and lifecycle behavior in the relevant project information before publishing documentation.

- If your project is hosted through a supported source provider, make sure the project connection is current before starting. Atloria presents supported source-provider options during project connection, including GitHub, GitLab, and Bitbucket.

## Related Pages

- [Manage Projects](#)
- [Connect a Project Source](#)
- [Use the Project Sidebar](#)
- [Review Project Changes](#)
- [Review Project Versions](#)
- [Create Technical Documentation](#)
- [View Project Analytics](#)

## Troubleshooting

### The project does not appear in Projects

1. Open **Projects**.

2. Enter part of the project name in **Search projects...**.

3. Confirm that you have access to the project.

4. If the project still does not appear, verify that the project has been added to Atloria and that you are using the correct account or workspace.

### You cannot find the Source area

1. Open the relevant project from **Projects**.

2. Confirm that you are in the focused project workspace.

3. Look for **Source** in the project sidebar.

4. If **Source** is unavailable, confirm that the project has a connected source and that your access level permits you to view it.

### The analysis completes with warnings

1. Wait until the displayed status shows that processing has completed.

2. Review the warning information available in the project’s source results.

3. Check that the connected source is complete and current.

4. Use the completed analysis carefully, and verify affected documentation details before publishing them.