Resource
Tooling, agents, and why discovery assets matter
A practical note on why `robots.txt`, `sitemap.xml`, `feed.xml`, and `llms.txt` belong to the product surface for an AI-oriented docs site.
Available locales
Agent-facing surface area
The blueprint treats agent discovery as part of the product, not as SEO housekeeping. That changes the minimum web implementation: the site needs machine-readable entry points in addition to human-readable pages.
What the web app emits
The app emits `robots.txt`, `sitemap.xml`, `feed.xml`, and `llms.txt` directly from the route tree and the runtime resource loader.
That means the discovery surface stays aligned with the actual localized pages and editorial entries rather than drifting into a manually maintained side file.
Source anchors