# Introduction

> What Stipple is and how the pieces fit together.

Stipple turns the markdown in your repository into a fast, searchable documentation site. You write Markdown and MDX next to your code, and every push rebuilds the site, the search index, the sitemap, and the llms.txt that AI agents read.

## Why Stipple

Most docs stacks make you choose between a hosted editor that drifts from your code and a static-site generator you have to maintain yourself. Stipple collapses that into one product:

- **Git-first.** Your repo is the source of truth. Docs are reviewed in pull requests and versioned with the product.
- **Agent-native.** Every build emits `llms.txt` and `llms-full.txt`, so Claude, Cursor, and ChatGPT answer from your docs instead of guessing.
- **Zero build tooling.** No generator to configure, no search service to babysit, no deploy scripts.

> **Note:** Stipple sites are fully static at serve time. There is no server rendering your pages on demand — which is why they are fast everywhere, all the time.

## How it works

1. You connect a repository in the **console** and point Stipple at your docs folder.
2. Every push to your default branch triggers a build.
3. The build is uploaded to edge storage and served globally at `yourdocs.stipple.wiki` — or your own custom domain.

Continue with the [quickstart](/quickstart) to get a site live.