Skip to main content
This repo has two documentation layers, each with a clear purpose. Here’s how they work.

​
Two Layers, One Repo

Public Docs

docs/public/ — The Mintlify docs site your users see. Setup guides, feature docs, provider docs, and troubleshooting.

Internal Docs

docs/architecture/ — Notes for maintainers only. Implementation details, refactor plans, internal tradeoffs.

​
What Goes Where

Put these here:
  • Setup and getting-started guides
  • Provider configuration docs
  • Product feature documentation
  • Customer-safe architecture explanations
  • Troubleshooting and FAQ content
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.

​
Writing Style

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
This matters especially for AnotherWrapper because many buyers want to understand the product before they dig into the implementation. Meet them where they are.