## Opening the Code Parsing Workspace and Understanding the Session Layout In Atloria, the Code Parsing Workspace is organized around a single working session. A session is the place where you collect the code you want to analyze, run parsing, and review the structured results without losing your progress. If you already uploaded code in the previous step, continue from [Uploading and Parsing Code in the Workspace](doc:uploading-and-parsing-code-in-the-workspace) and open that same workspace entry from your recent project activity or session list. When you open the workspace, look for these main areas: - **Upload panel** for adding code files - **Snippet input area** for pasting smaller pieces of code - **Parse** or **Start Parsing** action controls - **Results pane** where parsed structure appears - **Session list** or **recent workspace entries** for reopening earlier work A workspace session usually includes: - Uploaded source files - Pasted code snippets - Parsing results tied to each item - Structured output you can use while planning documentation coverage [SCREENSHOT: Code Parsing Workspace showing upload panel, snippet area, parse button, results pane, and session list] Different team members often use different parts of the same screen: - **Technical Writers** usually spend most of their time in the **results pane**, reviewing the structure of files and snippets to understand what should be documented. - **Documentation Managers** often move between the **session list** and **results pane** to compare sessions and check whether related source material has been parsed consistently. - **Project Administrators** are more likely to review **recent workspace entries** and existing sessions to see what has already been processed and what still needs attention. To begin fresh, open the workspace and start a **new session** by adding files or a snippet. To continue earlier work, select an existing session from the **session list** or from **recent workspace** entries. Reopening a session brings back its attached inputs and any results already generated, which is useful when documentation work spans multiple reviews. ## Adding Source Material to a Workspace Session A workspace session only becomes useful after you add the code you want Atloria to parse. In the Code Parsing Workspace, you can add source material in two main ways: upload files or paste a snippet. Use file upload when you want to review complete source files, and use the snippet area when you only need to inspect a smaller section. 1. In the **upload panel**, click the file picker to choose one or more code files from your device, or drag files into the drop area if that option is shown. 2. Wait for the files to appear in the **session contents list**. 3. If you only need to analyze a small section, click into the **snippet input area** and paste the code directly there. 4. Add the snippet to the current session so it appears alongside uploaded files. 5. Review the **session queue** or **input summary** before you start parsing. Atloria separates uploaded files from pasted snippets in the session so you can tell them apart quickly. In the session contents area, look for details such as: - **File names** for uploaded items - **Snippet labels** or a snippet entry name for pasted content - A **source type indicator** showing whether the item came from a file upload or the snippet editor This distinction matters when you return to a session later. A full file usually gives you broader structure, while a snippet may only show the portion you pasted. Before clicking **Parse** or **Start Parsing**, confirm that the correct items are attached to the current session. Check the selected files, review any snippet entries, and make sure the session queue matches the documentation task you are working on. If you are comparing related code areas, keep them in the same session. If you are working on a separate feature or release topic, create a different session so the results stay easier to review. [SCREENSHOT: Session contents list showing uploaded files and a pasted snippet with different source labels] ## Starting Parsing and Monitoring Session Progress Once your files or snippets are attached to the session, start the analysis from the workspace controls. In most cases, you will use the **Parse** or **Start Parsing** button shown near the session inputs or above the results area. Atloria then begins processing the items currently included in that session. 1. Review the selected files and snippets in the **session queue** or **input summary**. 2. Click **Parse** or **Start Parsing**. 3. Watch the status shown beside each item or in the **results header**. 4. Wait until the item status changes to a finished state before opening the result. 5. If one item does not complete, return to that specific entry in the session list and review its status separately. During processing, Atloria may show visible states such as: - **Queued** when an item is waiting to begin - **Parsing** while Atloria is actively analyzing it - **Completed** when results are ready - **Failed** if Atloria could not finish that item These status labels help you tell whether parsing covered everything in the session or only part of it. If all attached items show a finished state, the session ran for the full set. If only one file or snippet shows a completed result while others remain queued or failed, you know the session needs more review before you use it for documentation work. The **results pane** usually starts filling in automatically as items finish. You do not need to create a separate review record first. The session remains saved so you can leave the workspace and come back later without losing the uploaded files, pasted snippets, or completed results. [SCREENSHOT: Parsing in progress with item-level statuses such as queued, parsing, completed, and failed] This saved-session behavior is especially useful when multiple people review the same material over time. A writer can start parsing, a manager can reopen the session later, and both can refer to the same structured output when planning documentation coverage. ## Reviewing Parsed Results for Documentation Work After parsing finishes, use the **results pane** to inspect the structure Atloria found in each file or snippet. This is where the workspace becomes useful for documentation planning. Instead of reading raw code line by line, you can review a structured view of the important parts Atloria detected. The results view may show items such as: - **Modules** - **Classes** - **Functions** - **Methods** - Other code elements identified from the uploaded file or pasted snippet [SCREENSHOT: Parsed results pane showing structured code elements for one selected input] If your session contains more than one source item, switch between them using the **session list**, **contents list**, or the selected item area in the workspace. Choose one file or snippet at a time to load its specific result. This makes it easier to compare a full file with a smaller pasted snippet, or to review related files side by side within the same session. For **Technical Writers**, the parsed structure helps answer practical documentation questions: - Which parts of this feature need their own headings? - Which items look like API components or reference topics? - Which code areas suggest user-facing behavior that should be explained in a guide? For **Documentation Managers**, the same results support consistency checks across related files. If one file shows a rich structure and a related file produces only limited output, that may signal a gap in what has been uploaded, selected, or reviewed. Managers can use the session to verify whether source coverage is broad enough before assigning writing work. Use the parsed output as a map, not as finished documentation. It helps you identify what exists, how pieces are grouped, and where you may need deeper review. If you need broader coverage decisions after this step, continue to [Using Code Parsing to Support Technical Documentation](doc:using-code-parsing-to-support-technical-documentation). ## Using Workspace Sessions to Support Documentation Tasks A code parsing session in Atloria works best when you treat it as a research space for a specific documentation goal. Instead of mixing every file into one long-running session, organize sessions around the work you are actually doing. That makes the results easier to revisit, compare, and share with the rest of your team. You can keep separate sessions for different documentation efforts, such as: - **Feature-level analysis** when you need to understand one product area before writing a user guide - **API reference preparation** when you want to review structured code elements that may become reference topics - **Release documentation review** when you are checking what changed across a set of source files In practice, the workflow usually looks like this: 1. Add the files or snippets related to one documentation objective. 2. Run parsing for that focused set of inputs. 3. Review the structured results in the **results pane**. 4. Use the output to decide what needs coverage in guides, inventories, or reference pages. 5. Return to the same session later if the writing or review work continues. For **Technical Writers**, this helps move from raw source material to a clearer list of components, behaviors, or reference items that should appear in documentation. For **Documentation Managers**, saved sessions make it easier to check whether teams are reviewing the right source material before drafting or approving content. For **Project Administrators**, retained sessions provide a repeatable record of what was parsed and when, which can support internal review habits and more consistent documentation workflows. Common deliverables supported by these sessions include: - Feature guides - Component inventories - Technical reference pages - Release review notes based on parsed source structure Because sessions stay available for later review, they also help teams avoid repeating the same upload and parsing work every time a documentation task resumes. ## Common Issues and How to Fix Them Most workspace problems in Atloria come from the current session not containing the expected input, or from reviewing the wrong item after parsing finishes. Start by checking the **session contents list**, **selected item**, and **results pane** before repeating the whole process. If an **uploaded file does not appear** in the session contents list: - Return to the **upload panel** and confirm the upload finished - Make sure the file was added to the **current workspace session**, not a different one - Refresh your view by reopening the session from the **session list** or **recent workspace entries** - Check whether the file name appears lower in the contents list if multiple items were added If the **Parse** action is unavailable or nothing starts when you click it: - Confirm that at least one **file** or **snippet** is present in the workspace - Check that the item is included in the current **input summary** or **session queue** - Make sure you are still inside the active session you intended to use - Reopen the session and verify the source material is still attached If the **results pane is empty after parsing**: - Look at the item-level status and confirm the file or snippet actually finished processing - Open the specific file or snippet from the **session list** instead of relying on the default selection - Check whether another item in the session is currently selected - Reopen the session if needed and load the result again If a **snippet parses differently from an uploaded file**: - Compare the exact code pasted into the **snippet input area** with the version contained in the uploaded file - Check whether the snippet includes only part of the code while the uploaded file includes surrounding structure - Review each result separately so you do not assume both inputs should produce the same structure These checks usually resolve session-level issues without needing to rebuild the workspace from scratch. ## Overview This page focuses on how to manage ongoing work inside Atloria’s Code Parsing Workspace after you begin using it. A workspace session is the container for everything related to one parsing task: the files you upload, the snippets you paste, the parsing run itself, and the structured results you review afterward. Managing sessions well makes it easier to return to earlier work, compare related inputs, and keep documentation research organized. This guide is most useful when you already know how to add code to the workspace and trigger an initial parsing run. If you need that setup first, use [Uploading and Parsing Code in the Workspace](doc:uploading-and-parsing-code-in-the-workspace). Here, the focus is on session layout, adding and confirming inputs, monitoring progress, reopening saved sessions, and using results for documentation planning. You will work with these parts of the workspace throughout the guide: - **Upload panel** for source files - **Snippet input area** for pasted code - **Parse** or **Start Parsing** controls - **Results pane** for structured output - **Session list** or **recent workspace entries** for reopening saved work This guide also explains how different roles use the same workspace in different ways. **Technical Writers** typically review parsed structure to decide what to document. **Documentation Managers** use sessions to check completeness and consistency across related files. **Project Administrators** may use saved sessions to keep team workflows organized and easier to revisit. If your goal is to turn parsed results into actual documentation decisions and coverage plans, the next step after this page is [Using Code Parsing to Support Technical Documentation](doc:using-code-parsing-to-support-technical-documentation). ## Prerequisites Before you manage workspace sessions in Atloria, make sure you already have access to the project area where the Code Parsing Workspace is available and that you can open the workspace successfully. This guide assumes you are past the initial sign-in and project navigation steps and are ready to work inside an existing documentation workflow. You should already be comfortable with: - Opening the relevant project workspace in Atloria - Accessing the **Code Parsing Workspace** - Uploading code files or pasting a snippet at least once - Running an initial parse and recognizing where results appear If you have not done those steps yet, start with [Uploading and Parsing Code in the Workspace](doc:uploading-and-parsing-code-in-the-workspace). That guide covers the first-time flow. This page builds on it by showing how to continue, reopen, and organize that work across multiple sessions. It also helps to have one of the following ready before you begin: - A set of source files for a feature you need to document - A smaller code snippet you want to inspect on its own - A clear documentation goal, such as reviewing a feature area, preparing reference content, or checking release-related source material This guide is especially relevant for: - **Technical Writers** reviewing parsed structure before drafting content - **Documentation Managers** checking consistency across related source material - **Project Administrators** overseeing repeatable workspace usage across a team You do not need to prepare publishing settings, approval steps, or public documentation pages before using workspace sessions. The only requirement is that you have source material ready and can open the parsing workspace where those files or snippets can be added and reviewed.