Documentation is now part of the product
The public site now publishes task-oriented documentation for setup, authorization, integration, API behavior, operations, troubleshooting and contribution. Each route is statically rendered with its own title, description, canonical URL and structured data.
The content lives with the implementation instead of in a separate marketing system. A change to a tool, error or operational procedure can therefore update the product and its public explanation in the same review.
Search and machine-readable discovery
The control plane generates robots.txt, sitemap.xml, an RSS feed and concise llms.txt resources from the same route catalog. Article metadata includes publication dates and Article JSON-LD; documentation uses TechArticle markup.
These files make the site understandable to crawlers, but they do not buy trust or guarantee ranking. A stable production hostname, useful references from other sites and continued technically accurate publishing remain operational work.
Hosted analytics without a self-hosted beacon
Official hosting can opt into privacy-focused page and onboarding measurements. The browser loads that integration only after checking Global Privacy Control and Do Not Track, and only known route names and a fixed event catalog are accepted.
Source builds and self-hosted installations contain no analytics endpoint or site identifier by default. They send nothing to the ADC project unless their own operator explicitly configures both values.
What this foundation is for
The goal is not a larger page count. It is a durable public record of what ADC does, what it does not do, how operators verify it and where contributors can improve it. Release notes will stay tied to shipped behavior and guides will be tested against the current CLI.