> ## Documentation Index
> Fetch the complete documentation index at: https://reconco.manicule.dev/llms.txt
> Use this file to discover all available pages before exploring further.
> For every page in one file, fetch https://reconco.manicule.dev/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://reconco.manicule.dev/api/mcp.
> Every agent surface: https://reconco.manicule.dev/.well-known/llms-manifest.json

# How Reconco Works (/documentation/get-started/how-reconco-works)

<!-- agent-signals: reading_time_min: 2 · est_tokens: 572 · updated: 2026-11-22 -->
Related: [Introduction to Reconco](/documentation/get-started/introduction-to-reconco.md), [Key Concepts](/documentation/get-started/key-concepts.md), [Team Documentation Use Cases](/documentation/using-reconco/team-documentation-use-cases.md)

Evaluate Reconco’s web app against the documentation work your team needs to do. The questions below identify workflow details to confirm during evaluation; they do not describe established product capabilities or provide operating instructions.

## Evaluate authoring and organization

Start with a representative piece of your team’s documentation and establish how you would create it, change it, and place it where readers can find it. This connects the evaluation to actual work without assuming a particular editor or content structure.

Confirm these details in the web app:

* How do you create content and return to it for later edits?
* What content formats and editing controls are available?
* How can you arrange related content, and what happens when you move or rename it?
* How would a reader find the content within the resulting documentation?

Authoring controls and content organization have not been established here. Do not assume a specific editor, navigation model, or content object type.

## Check collaboration and publication behavior

Establish how a change becomes reader-visible before using the app for documentation that readers depend on. Saving an edit and making it visible may be separate actions, but that distinction needs confirmation in Reconco.

Ask whether drafts exist, who can see unfinished changes, and whether review is available or required. Confirm what action makes a change reader-visible and whether an existing published version remains visible while edits are in progress.

For teamwork, check how colleagues contribute to the same content, what happens if they edit at the same time, and whether access or publication permissions can differ between people. These are evaluation questions, not claims that Reconco provides review, concurrent editing, or permission controls.

## Confirm the browser workflow’s scope

The web app is the documented Reconco surface. Use the browser workflow as the basis for evaluation, and confirm which documentation tasks it covers before planning an integration.

Repository synchronization, local tools, APIs, and deployment behavior are unspecified. If your team requires any of them, obtain confirmation of their availability and behavior before making them part of your documentation process.
