Preview locally
docs.json, custom visuals in style.css, and content in MDX. The CLI is pinned in the lockfile.
Page standard
Each page needs a unique title and description, an accurate opening summary, useful task-oriented sections, relevant examples, clear limitations, and related links. Add troubleshooting where it helps. Write enough to answer the question; do not pad content for a word count. For API pages, distinguish supported inputs, response semantics, freshness, errors, and access requirements. For tools, explain what a result does not establish, such as an MX record not proving mailbox existence.Validation
Preserved articles
The two original CMS articles are innotes/, with original source in migration/source-articles.json. Historical third-party service claims must remain attributed rather than becoming current promises by AVRXT.

