Anydocs Documents
Using Studio

Manage Navigation

Maintain navigation based on the real Studio behavior, not as a page-file manager.

The goal of navigation maintenance is to keep reader structure, page status, and language variants aligned. In the current Studio, navigation is best understood as a per-language, publication-oriented tree: page nodes reference pages, group nodes organize structure, and link nodes point outward. Do not treat navigation edits as the same thing as publishing edits.

Steps

  1. Confirm which language navigation you are editing
  2. Add pages, groups, or external links under a section or group
  3. Use Move Up / Move Down to control order
  4. Separate removing a nav reference from unpublishing a page

Confirm which language navigation you are editing

Navigation is stored per language. Before editing, confirm whether you are working on `zh` or `en`, because writes go to `navigation/zh.json` and `navigation/en.json` separately. A group or link added in one language does not automatically appear in the other language navigation.

The current Studio supports three common add actions: add page, add group, and add external link. Adding a page creates the page first, then inserts its reference into the current group. Adding a group creates a `folder` that can hold children. Adding a link requires a display title and URL. Page nodes display the page title; they are not edited through a separate navigation-title editor by default.

Use Move Up / Move Down to control order

Current navigation maintenance is primarily order-based, not freeform drag-and-drop. Node order directly affects the reader sidebar. Group nodes can contain child nodes; page and link nodes cannot contain children.

Separate removing a nav reference from unpublishing a page

Deleting a navigation node only removes it from the current language navigation. It does not delete the page file. If you need a page to disappear from the public reader, search, and AI artifacts, also change its page status back to `draft` or `in_review`, or delete the page itself. Conversely, even if a page is still referenced in navigation, it will not appear publicly unless it is `published`.

Node kinds: The navigation contract supports `section`, `folder`, `page`, and `link`. In Studio, `folder` is often presented as a group.
Page nodes are references: A page node in navigation is only a reference to a `pageId`, not a copy of the page content. Changing navigation does not rewrite body content, and editing body content does not automatically reorganize navigation.