# Docs hosting

Your guides live as Markdown in your repository. CI pushes the folder as one archive with a project key, and the site is built once, at push: every page rendered, every link checked, the search index and the agent files written. Readers then get stored pages, so nothing is rendered per visit.

A site is served at `https://latitude10.tech/docs/<workspace>/<project>` once an owner or admin publishes it, with the project's reference as a section of its own once that's published too. On Pro and up it can also be served on your own domain.

Every site comes with `llms.txt`, `llms-full.txt`, a Markdown copy of each page, `skill.md` and a docs MCP server, with nothing to set up.

## In this section

- [The docs folder](bundle): its layout, `latitude10.docs.json`, front matter, page addresses and what's refused.
- [Markdown in guides](markdown): what a page may use, and how to work within it.
- [Push your docs](push): production, versions and previews.
- [Files for agents](agent-files): `llms.txt`, Markdown pages and the docs MCP server.
- [Custom domains](custom-domains): your own subdomain, with one CNAME.
- [Docs traffic](traffic): who reads the site, people and agents.

## Where this comes from

- `app/docs/_lib/bundle.ts`
- `app/docs/_lib/build.ts`
- `app/docs/_lib/site.ts`
- `app/api/registry/v1/docs/route.ts`
- `app/workspace/docs-actions.ts`