Also known as blocks
A document model built from typed blocks — paragraphs, headings, lists, embeds — instead of one undifferentiated page. Canvas uses blocks so outlines, history, and skills can target real sections.
A block editor treats headings, paragraphs, lists, and embeds as typed units you can reorder, target, and version -- not as one undifferentiated page paste. That structure is why Canvas outlines, history, and future skills can aim at real sections instead of guessing from font size alone in a long file.
Canvas is in early access for Pro and Team. It is already useful for manuscripts and research binders, while some embed types are still maturing. Be honest with collaborators about fidelity: cite the changelog when a Plot embed or rich embed does not yet match your production wiki dreams for the season.
Name a save point before large outline rearrangements so structural moves stay reversible under pressure. Export paths like Markdown round-trip exist so long-form work is not trapped; verify a re-import on a draft line before you delete a source file you still need for archive. Keep that standard visible when notes arrive so the next pass stays honest.
Docs optimizes familiar continuous pages. Canvas treats headings and sections as structured blocks so version control and skills can operate on the same units you outline.
Canvas is in early access for Pro and Team. Join from the Canvas page if your plan qualifies and you want long-form structured drafting.
Not all. Early access is maturing embed types over time -- check current behavior before you depend on a complex embed as your only archive.
No. Keep series bibles in Plot next to episodes. Use Canvas for novels, research binders, and general team docs that cite scripts.
