> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anotherwrapper.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Documentation Workflow

> How docs are organized and where different types of content belong

This repo has two documentation layers, each with a clear purpose. Here's how they work.

## Two Layers, One Repo

<CardGroup cols={2}>
  <Card title="Public Docs" icon="globe">
    **`docs/public/`** -- The Mintlify docs site your users see. Setup guides, feature docs, provider docs, and troubleshooting.
  </Card>

  <Card title="Internal Docs" icon="lock">
    **`docs/architecture/`** -- Notes for maintainers only. Implementation details, refactor plans, internal tradeoffs.
  </Card>
</CardGroup>

## What Goes Where

<Tabs>
  <Tab title="Public Docs (docs/public/)">
    Put these here:

    * Setup and getting-started guides
    * Provider configuration docs
    * Product feature documentation
    * Customer-safe architecture explanations
    * Troubleshooting and FAQ content
  </Tab>

  <Tab title="Internal Docs (docs/architecture/)">
    Put these here:

    * Implementation notes and technical decisions
    * Refactor plans and migration strategies
    * Internal tradeoffs and design reasoning
    * Maintainer-only concerns
    * Anything you wouldn't want publicly visible
  </Tab>
</Tabs>

## Navigation

<Info>
  The Mintlify site structure is controlled by `docs/public/mint.json`. If you add a new page but forget to add it there, your page will exist but won't show up in the docs navigation.
</Info>

## Writing Style

<Tip>
  When writing public docs, keep these principles in mind:

  * **Assume your reader isn't deeply technical** -- explain what something is before diving into env vars
  * **Explain the "why"**, not just the "how" -- help readers understand what matters
  * **Stay accurate to the current codebase** -- outdated docs are worse than no docs
  * **Talk to the reader directly** -- use "you" and keep it conversational
</Tip>

This matters especially for AnotherWrapper because many buyers want to understand the product before they dig into the implementation. Meet them where they are.