Publishing Workflow
The smallest reliable workflow for moving a page from draft to public reader and AI artifacts.
Public visibility in Anydocs is controlled by page status. Finished content is not published content until the page reaches `published`.
Steps
- Finish the body and required metadata
- Enter review when needed
- Publish through the dedicated status action
- Re-validate the public outputs
Finish the body and required metadata
Use Studio or MCP to complete the body content plus key fields such as `title`, `description`, `slug`, and `tags`, and make sure the slug is unique within the language.
Enter review when needed
If the project requires review, move the page to `in_review` first and complete the human approval step.
Publish through the dedicated status action
After review, move the page to `published`. In Studio, use the status selector; in MCP, use `page_set_status`.
page_set_status({ projectRoot: "/path/to/project", lang: "en", pageId: "guide", status: "published" })Re-validate the public outputs
Run `preview` or `build` and confirm the page now appears in the reader, `search-index.<lang>.json`, `llms.txt`, `llms-full.txt`, and `mcp/*.json` outputs.