Using Project Home to Coordinate Documentation Work

Opening a project and reading the project home status

Open your project from the main Projects area in Atloria, then select the project name to enter the project itself. When you first arrive, use the main project screen as your coordination point instead of jumping straight into a document, version, analytics page, or technical reference area. This project home view keeps the full project context visible so you can quickly understand where work stands before you open a specific workspace.

At the top of the page, look for the project header. This is where Atloria shows the project name and the main project identity for the workspace you are viewing. Around that header, you will typically use the surrounding summary area to understand overall project status at a glance. This is the best place to confirm that you opened the correct project before reviewing activity or assigning follow-up work.

Below the header, review the project home cards or summary panels. These panels are useful because they bring together project-wide signals in one place instead of making you open each workspace one by one. Focus on items such as:

• linked workspaces connected to the project
• recent activity across the project
• progress indicators that reflect project-wide documentation work

Project home is different from a single workspace because it is designed for coordination, not deep editing. A content workspace is where you write and organize documentation. A version workspace is where you review release progress and version status. An analytics workspace is where you review usage and performance information. A technical documentation workspace is where you browse generated technical reference material. Project home sits above all of these and helps you decide where to go next based on current status.

If you need a refresher on finding projects from the broader project list, see Managing Project Portfolio and Operational Oversight.

Moving between project home tabs to find the right work area

Inside project home, use the tab navigation to move between the main project views without leaving the current project. This is one of the most useful parts of working in Atloria because you can compare several kinds of project information while staying anchored to the same project record. Instead of reopening the project each time, you switch tabs and keep the same project scope throughout your review.

1. Open the project from Projects.
2. Stay on the main project area and look for the tabs near the top of the page.
3. Click a tab to switch views inside the same project.
4. Review the information on that tab, then move to another tab as needed.

Different tabs support different coordination tasks. In practice, you will use them to review project details, check linked workspaces, look at recent activity, and move into reporting-oriented views when you need a broader picture of progress. The exact tab names may vary by project setup, but the purpose stays the same: each tab helps you inspect one part of the project without losing the overall project context.

This matters when several teams are working at once. For example, a documentation manager may compare activity and workspace status across tabs before deciding whether to open the content workspace or the version workspace. A project administrator may stay in project home longer to review status across areas before making changes elsewhere.

Stay in project home when you need to:

• compare progress across multiple work areas
• review recent updates before assigning follow-up work
• confirm which linked workspace needs attention

Open a linked workspace when you need to:

• edit documentation content
• review or manage versions
• inspect analytics in detail
• browse technical documentation pages

Using tabs this way keeps your review efficient and avoids losing track of which project you are working in.

Tracking linked workspaces from one project context

One of the main jobs of project home is helping you track every workspace connected to the current project. Look for the linked workspaces section, card list, or panel on the project home screen. This area shows the workspaces that support the project and gives you a quick way to move between them without going back to the main navigation.

As you review the list, identify the type of work each linked workspace supports. In Atloria, documentation teams commonly coordinate across these workspace types:

Use the linked workspace list to confirm that the project has the work areas you expect. This is especially helpful when you manage several projects and need to verify whether a project already has the right documentation spaces connected.

Pay attention to any status or health signals shown beside each workspace. These indicators help you spot where work may be incomplete, delayed, or waiting for review. For example, if one workspace looks less active than the others, that may be the area to inspect next. If a workspace appears connected but shows limited progress, open it and confirm whether work is still in progress or simply not reflected in the summary yet.

To move between areas, click the linked workspace name from project home. After reviewing or updating that workspace, return to the project home area to continue your cross-project check. This back-and-forth pattern is useful because it lets you make a targeted update without losing sight of the overall project.

Coordinating content, versions, analytics, and technical documentation work

Project home is most useful when you need to coordinate several kinds of documentation work at the same time. Instead of treating content, versions, analytics, and technical documentation as separate streams, use the project home screen to compare them side by side and decide what needs attention first.

A practical workflow in Atloria looks like this:

1. Open the project and review the project home status.
2. Check the summary panels and linked workspaces to see which area needs follow-up.
3. Open the relevant workspace directly from project home.
4. Make the needed update in that workspace.
5. Return to project home and confirm whether the overall project picture now looks aligned.

This approach works well because project home gives you a shared starting point. A documentation manager can review whether content work is moving forward, whether version work is ready for review, whether analytics suggest a documentation gap, and whether technical documentation needs attention. A project administrator can use the same project context to coordinate across teams without managing each area in isolation.

For example, if recent activity shows content updates but version progress still appears behind, open the version workspace next. If analytics suggest readers are relying heavily on a certain area, you may decide to open the content workspace or technical documentation workspace to improve that material. If technical reference pages need review before a release, project home helps you move there quickly without losing track of the broader release picture.

This coordination style is especially helpful when deadlines shift. Technical writers can start from project-level status, identify the exact workspace that is blocking progress, and move directly into that area. For deeper guidance on the individual work areas themselves, use the related guides such as Creating and Editing Documentation Pages, Managing Documentation Versions Across the Release Cycle, and Exploring Technical Documentation Inside a Project.

Using project home to monitor progress and recent activity

Use project home as your regular check-in screen when you need to understand what changed across the project most recently. The progress indicators and activity summaries on this page are designed to help you review project movement without opening every workspace one at a time. For weekly reviews, handoffs, and status meetings, this is often the fastest place to start.

Begin with the project-wide progress area. This part of the page helps you judge whether work is moving evenly across the project or whether one area is falling behind. Then review the recent activity section to see which workspace had updates and what kind of work changed. Even a short activity list can tell you a lot when you are coordinating multiple contributors.

When reading recent activity, look for signals such as:

• which linked workspace was updated
• whether the update relates to documentation work, version work, analytics review, or technical documentation
• whether activity appears recent enough to match the team’s expected progress

Project home is especially useful during handoffs. A documentation manager can open the project home screen during a meeting and quickly point to recent updates, then decide whether the next conversation should happen in the content workspace, version workspace, analytics area, or technical documentation view. This keeps status discussions tied to visible project information instead of relying on separate notes.

Some signals mean you should go deeper into a linked workspace:

• progress looks uneven across work areas
• recent activity appears in one workspace but not another related area
• a workspace shows little or no movement when work should already be underway
• a summary panel suggests incomplete or stalled work

When that happens, use project home as the launch point for a closer review. It gives you enough context to know where to investigate next without forcing you to search through the project from scratch.

Common issues when coordinating work from project home

If project home does not show what you expect, start by checking whether you are in the correct project and whether you are still on the main project area rather than inside a specific workspace. Many coordination problems come from opening the right project but the wrong view, especially when local workspace navigation looks similar to project-level navigation.

A common issue is a missing linked workspace. If you do not see the workspace you expected, first confirm that you opened the correct project record from Projects. Then review the linked workspaces area again. If the workspace is still missing, the current project may not have that workspace connected, or your access may not allow you to open it.

Another issue is project status that looks incomplete or outdated. In that case, refresh the project home page and compare the summary panels with the most recent work you know was completed. Sometimes updates were made inside a linked workspace, but the project home summary does not yet match what you expected to see. Refreshing the view is the quickest first step before escalating the issue.

If you can open project home but not the workspace you need, check whether your role includes access for the work you are trying to open. In Atloria, documentation managers, technical writers, and project administrators may have different levels of access depending on the project setup. If a workspace opens for a teammate but not for you, this usually points to a permission difference.

If the tabs do not show the information you expected:

• confirm you are on the main project home screen
• check whether you accidentally opened a linked workspace with its own navigation
• return to the project’s main page and use the project home tabs again

For more on access and admin-level setup, see Managing User Access and Administrative Permissions.

Overview

Use project home in Atloria as the central coordination screen for a documentation project. It brings together the project name, project-level status, linked workspaces, and recent activity so you can understand the current state of work before opening a specific area. This is especially useful when several teams are contributing to the same project and you need one place to compare progress.

The most important parts of project home are:

• the project header, which confirms which project you are viewing
• the tab navigation, which lets you switch between project-level views
• the linked workspaces area, which shows the connected spaces for content, versions, analytics, and technical documentation
• the recent activity and progress summaries, which help you spot changes and delays quickly

Project home is not meant to replace the detailed workspaces. Instead, it helps you decide where to go next. Use it when you need to review overall status, compare work across areas, prepare for a handoff, or guide a status discussion. Then open the linked workspace that needs action and return to project home when you want to confirm the broader project picture again.

This guide focuses on using project home as a coordination layer. If you need detailed instructions for project lists, dashboards, or broader portfolio oversight, refer back to Managing Project Portfolio and Operational Oversight. From there, this guide picks up at the project level and shows how to manage work once you are already inside a specific project context.

The next step is Navigating Project Workspaces and Linked Tools, which goes deeper into moving through the connected work areas after you leave project home.

Prerequisites

Before using project home to coordinate documentation work, make sure you have the basics in place so the project-level information in Atloria is meaningful and actionable.

You should have:

• access to Atloria with permission to open projects
• at least one project visible in the Projects area
• a project that already includes one or more linked workspaces
• the appropriate role for the work you need to review, such as documentation manager, technical writer, or project administrator access
• familiarity with opening projects from the project list

It also helps if the project already has active work underway. Project home is most useful when there is recent activity to review, linked workspaces to compare, and progress signals that help you decide what to do next. If a project is brand new, the project home screen may have less information to coordinate.

Before relying on project home for status reviews, make sure you can:

• open the project from Projects
• recognize the project’s main home area
• switch between project-level tabs
• open and return from a linked workspace

If you are still getting familiar with project navigation, start with Working with Project Lists and Dashboards and Understanding Project Navigation and Linked Workspaces. Those guides explain how to find projects and recognize the difference between project-level navigation and workspace-level navigation, which makes this coordination workflow much easier to follow.