A Document Page turns a nested tree of Documents and supported Components into website routes with metadata, SEO, and chosen layout Components.
Property: Identity · Current behavior: stored metadata type document-page
Property: UI label · Current behavior: Document Page
Property: Internal/MCP name · Current behavior: Blog / blog-* for historical compatibility
Property: Workspace · Current behavior: nested document tree and route settings
Property: Result · Current behavior: nested generated document-site routes
Property: MCP · Current behavior: read/add/update/reorder/delete tree items, layout Components, SEO
Tree items can be inserted before, after, or inside one another; renamed, nested, reordered, expanded/collapsed, attached/replaced, or deleted. An item can attach a Document or supported page Component, store custom metadata, and define route SEO. The file selects page, item, and summary-item Components for generated output.
Names become lowercase route segments with spaces replaced by hyphens. An unattached grouping node can organize children; an unattached leaf emits no route. The root currently re-exports the first Document and is not repeated in the SEO Page list.
Use get-blog, document-tree mutation operations, set-blog-components, and set-document-seo. IDs survive a move, preserving identity for internal links.
Verify every emitted route, attachment, metadata field, SEO value, and layout Component in the actual generated website. Deleting a route-tree item is different from deleting its attached Document file.
Tree/attachment/metadata edits are persisted transactions. Website publishing is external and not reversed by file Undo.