# Create a Documentation Project

Create a documentation project to give Atloria a focused workspace for analyzing a repository and organizing its generated technical documentation. A project helps you keep documentation, versions, changes, screenshots, and analytics tied to the correct application.

## Overview

A project is the central container for documentation work in Atloria. From the **Projects** area, you can open a focused project workspace and access project-specific areas such as documentation, version reviews, change history, screenshots, and analytics.

Create a separate project when you need documentation for a new application, repository, service, or documentation initiative. Keeping each codebase in its own project makes it easier to search, review, and manage documentation without mixing content from unrelated work.

After you create a project, Atloria provides a project dashboard. From there, you can use **View Your Documentation →** to open the documentation experience or **Open Project Dashboard** to return to the project’s main workspace.

> 📷 _Screenshot pending: The Projects hub showing the Workspace area, project search, and options for opening or creating a project._

## Prerequisites

Before you begin, make sure you have the following:

- Access to the **Workspace** and **Projects** areas.
- Permission to create or manage projects in your organization.
- The repository or application source you want to document.
- The repository location or connection details, if your organization connects projects to a source repository.
- A clear documentation purpose, such as documenting a customer-facing application, an internal service, or a technical API.

If you are connecting a repository, prepare the correct repository source. Atloria’s project setup supports recognizable source-provider options represented by GitHub, GitLab, and Bitbucket icons.

## Step-by-Step Instructions

1. Select **Workspace** to open your organization’s shared workspace.

2. Select **Projects** to open the hub that lists the projects available to you.

3. Review the project list to confirm that a project does not already exist for the application you want to document.

4. Enter a project name in **Search projects...** if you need to look for an existing project before creating another one.

5. Start the **New Project** flow from the Projects hub.

> 📷 _Screenshot pending: The New Project entry point in the Projects hub._

6. Select the repository source option that matches where your application is hosted.

7. Provide the repository or application information requested in the project setup flow.

8. Describe the documentation purpose when the setup flow asks for project details.

   Use a purpose that identifies both the audience and the intended outcome. For example, describe whether the project is intended for user guides, technical reference material, onboarding documentation, or ongoing maintenance documentation.

9. Confirm the project details to create the project.

10. Select **Open Project Dashboard** after creation to enter the focused project workspace.

11. Select **View Your Documentation →** when you are ready to review the documentation associated with the new project.

## Tips and Best Practices

- Create one project per distinct application or repository. This keeps project versions, detected changes, screenshots, and analytics meaningful and easier to review.

- Use a specific documentation purpose. A clear purpose helps your team understand why the project exists and what type of documentation should be maintained there. For example, “Internal technical reference for the billing service” is more useful than “Documentation.”

- Check **Search projects...** before creating a new project. This can prevent duplicate projects for the same codebase.

- Use the project workspace for project-specific work. The focused project area includes documentation-related destinations for technical documentation, versions, changes, screenshots, and analytics.

- Return to the full list by selecting **← Back to Projects** when you need to switch between projects.

- Plan for the documentation scope to evolve. Atloria can organize analyzed information across categories such as frontend, backend, database, API schema, configuration, documentation, and infrastructure. A project provides one place to review these different parts of your application.

> 📷 _Screenshot pending: A focused project dashboard with options to view documentation and navigate to project-specific areas._

## Related Pages

- [Workspace Sidebar](#)
- [Project Sidebar](#)
- [Open a Project Dashboard](#)
- [View Project Documentation](#)
- [Review Project Changes](#)
- [Compare Project Versions](#)
- [Manage Project Screenshots](#)
- [Delete a Project](#)

## Troubleshooting

1. **You cannot find the option to start a new project.**  
   Select **Projects** from **Workspace** and verify that you are in the projects hub. If the option is still unavailable, ask an organization administrator to confirm that you have permission to create projects.

2. **You are unsure whether the project already exists.**  
   Use **Search projects...** before beginning the **New Project** flow. Search using the application name, repository name, or a recognizable part of the project name.

3. **You created a project but cannot find its documentation.**  
   Open the project from the **Projects** list, then select **View Your Documentation →**. If you need to return to the project list, select **← Back to Projects**.