1---2name: plan-browser-editing3description: >-4 Which browser surfaces are directly editable and which patch op each one5 autosaves through — inline prose, local plan folders, review annotation mode,6 canvas/design elements, and branding. Use when changing plan prose, styles, or7 wireframe/prototype HTML.8metadata:9 source: https://skillmd.com/skills/builderio/plan-browser-editing10---1112# Browser Editing1314- Prose in `rich-text` blocks is edited inline with the shared15 `RichMarkdownEditor`, autosaved through `update-visual-plan` with16 `contentPatches: [{ op: "update-rich-text", blockId, markdown }]`.17- The single-document editor saves the whole block list with `replace-blocks`18 and `expectedUpdatedAt`, plus `allowDestructive`, because a block removed there19 is the person's own edit. The live Yjs document `plan:<planId>` is the source of20 truth for text: autosave sends pending Yjs updates first (`flushUpdates`), then21 reads the blocks from the document, not from the last keystroke. A22 `save_conflict` carries the newest saved content, so the save three-way merges23 those blocks onto it by block id (core's `saveWithMerge`) and retries. Only24 overlapping edits ask the person, with the shared prompt, and the version they25 choose goes into the live document. The editor takes in `content` only when26 `contentUpdatedAt` changes: an optimistic copy, or the saved copy a refetch27 brings back over it, is nothing new. `seed-plan-collab` seeds the empty live28 document once, so two editors opening together cannot duplicate the content.29- Local `/local-plans/:slug` folders opened from `PLAN_LOCAL_DIR` or a30 repo-relative `?path=...` use the same Notion-style browser editor, but31 autosave through `update-local-plan-folder` so changes are written to32 `plan.mdx`, `canvas.mdx`, and `prototype.mdx` without touching the Plan33 database.34- Review annotation mode makes prose temporarily read-only so clicks can pin35 feedback. Leaving review mode restores inline prose editing.36- Canvas, artboard, wireframe, diagram, and custom visual edits remain driven by37 comments, source patches, or structured content patches rather than direct38 rich-text editing.39- Design-mode artboards can be element-edited with `update-visual-plan`40 `contentPatches: [{ op: "update-design-element-style", frameId, blockId,41elementId, styles }]`. Elements must have `data-design-id` or42 `data-plan-design-id`; use `patch-wireframe-html` / `patch-prototype-html` for43 structural or text changes.4445## Branding4647- The sidebar brand header has a `Customize branding` popover. Treat it as a48 source-code request, not plan data: local Code mode edits `templates/plan`49 source directly, while hosted/live surfaces route people to Desktop or50 Builder for code customization.5152## Related Skills5354- **plan-comments-and-feedback** — the review/annotation side of these surfaces.55- **plan-source-sync** — the MDX files local folder autosave writes to.56- **plan-hosted-writes** — verification required after each hosted write.