Documentation Studio
Use a Studio to prepare documentation.
Write and publish docs for every domain
Write, design, and publish documentation for every APPNEURAL domain.
documentation.appneurox.com is the platform and its Studio: create a docs site from a template, from .md files or as a copy, edit pages in Markdown with a live preview, design it, and put it on a domain. Each domain serves its docs on docs.<domain>, one site at the root and the others under /<site>. docs.appneural.com holds the docs of every APPNEURAL catalog, regenerated from their READMEs and code.
What Docs does for you.
Use a Studio to prepare documentation.
Write content and shape its presentation.
Publish documentation on each domain’s docs address.
A suggested path for Docs. What you can do depends on your access in the app.
Start with the domain whose documentation you are preparing.
Develop and design the documentation content.
Check the documentation on the domain’s docs site.
Live host, inventory, governance, health checks, verification, dependencies and history.
documentation.appneurox.com is the platform and its Studio: create a docs site from a template, from .md files or as a copy, edit pages in Markdown with a live preview, design it, and put it on a domain. Each domain serves its docs on docs.<domain>, one site at the root and the others under /<site>. docs.appneural.com holds the docs of every APPNEURAL catalog, regenerated from their READMEs and code.
Actual guides and references belong to Docs; this reserved view tracks the systems that publish them.
8 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
documentation.appneurox.com
Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.