A Document is reusable rich content that can stand alone in the editor, be embedded in a visual Component, or be attached to a Document Page route tree.
Property: Identity · Current behavior: files below documents/
Property: Creation · Current behavior: ordinary Document files/folders under Documents
Property: Workspace · Current behavior: rich-text block editor
Property: Blocks · Current behavior: text, headings, lists, quote, code, divider, image, YouTube, Component
Property: Route · Current behavior: none until attached to a Document Page
Property: MCP · Current behavior: whole-document and targeted block operations
Inline formatting includes bold, italic, strike, underline, code, URL links, and internal page links. Media/Component blocks support widths and UI presentation options. Blocks can be selected, dragged, turned into another type, or deleted. Headings can drive summary navigation in embedding/Preview contexts.
Use write-document to replace or append HTML-derived blocks, edit-document for insertion/replacement/deletion by stable block ID, and dedicated operations for image, video, and Component blocks. Read current file data before a surgical edit.
Some block border/padding presentation remains easier or only available in the UI; report unsupported settings instead of approximating them.
A Document becomes public route content only through a Document Page attachment. Component blocks and internal links must resolve to current compatible identities. Older stored shapes use a compatibility renderer.
Rich edits persist/synchronize through document rows and collaborative updates. Whole-file replacement is broader than a targeted block edit; inspect the complete content before and after recovery.