Anydocs Documents
Using Studio

Edit a Page

Edit page body, metadata, status, and discoverability in Studio.

Editing a page is not just writing body content. You also decide the slug, description, tags, state, and whether navigation should reference it.

Steps

  1. Select the target page in the correct language
  2. Edit the body
  3. Fill in metadata
  4. Choose the publication state
  5. Decide whether navigation should reference it

Select the target page in the correct language

Confirm the current language first, then pick the target page from the page list. In bilingual projects, do not assume another language page will update automatically.

Edit the body

Use the central editor with the currently supported document blocks, such as headings, paragraphs, lists, code, callouts, tables, images, links, and Mermaid. Use the `/` menu to insert blocks and block drag handles to reorder them.

Fill in metadata

Complete `title`, `description`, `slug`, and `tags` in the right-hand panel. The `slug` becomes part of the reader URL and must remain unique within the same language.

Choose the publication state

Keep the page in `draft`, move it to `in_review`, or set it to `published`. Only `published` pages enter the public reader, search indexes, `llms.txt`, and `mcp/` artifacts.

Decide whether navigation should reference it

If readers should discover the page through the site structure, add it to the navigation tree. Navigation affects discoverability; publication state affects whether the page enters public artifacts. Treat those as separate decisions.

Save behavior: When you edit through Studio, the page content and metadata are written back to the matching page file under `pages/<lang>/`.
Not in navigation does not mean not published: A page can still be reachable by direct URL while published even if it is not linked from navigation. The real public boundary is page status, not whether navigation references it.