@mjml-agent-editor/editor 0.2.0 → 0.3.0

package/README.md

@@ -9,7 +9,7 @@ on the canvas.
 | -------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------ |
 | `@mjml-agent-editor/editor`            | stores, `EditorHeader`, `ChatPanel`, `CanvasComments`, types | Safe to import anywhere                                |
 | `@mjml-agent-editor/editor/ui`         | the shadcn primitives and `cn`                               | Light; no canvas                                       |
-| `@mjml-agent-editor/editor/canvas`     | `EmailEditor`                                                | **Browser only** — GrapesJS touches `window` at import |
+| `@mjml-agent-editor/editor/canvas`     | `EmailEditor`, `blockProblems`                               | **Browser only** — GrapesJS touches `window` at import |
 | `@mjml-agent-editor/editor/styles.css` | editor chrome stylesheet                                     | Import from your Tailwind entry                        |
 
 The split is not cosmetic. With a single barrel, a layout file importing a tooltip provider
@@ -121,6 +121,37 @@ storage would otherwise be handing out a way round its own cap.
 Without a library the picker takes URLs only. The editor never inlines a file as base64:
 most mail clients block `data:` images, and every agent turn would pay for the bytes.
 
+## Your own sections
+
+`EmailEditor` takes `blocks`: sections of your own, listed in the palette after the built-in
+blocks, under `blockCategorySections`. Each is one `<mj-section>` of MJML; once dropped it is
+ordinary MJML that the agent edits like any other section, and it gets its `sec-*` id then.
+
+```tsx
+const BLOCKS = [{ id: "footer", label: "Footer", mjml: FOOTER_MJML }] satisfies SectionBlock[];
+
+<EmailEditor docId={docId} blocks={BLOCKS} /* … */ />;
+```
+
+The agent compiles the whole email strictly on every write, so a section the editor cannot
+keep would block it in every email it is dropped in. `blockProblems(mjml)` says why a block
+cannot be offered — it is not strict MJML, not exactly one section, carries a `sec-*`/`obj-*`
+id, a link whose scheme is not http, https, mailto, tel or sms, or a `data:` image, holds markup
+the editor drops, or uses a tag a section here cannot hold (`mj-table`, `mj-hero`, accordion
+and carousel, which the editor cannot edit; `mj-wrapper` and `mj-raw`). The editor leaves such
+a block out and logs why; call it in a test of your catalog to find out before your users do.
+It needs a DOM, so run that test under jsdom. Labels are plain text. `blocks` is read once,
+when the editor starts.
+
+Every tile, built-in or yours, also works from the keyboard: Tab to it, and Enter or Space
+adds it after the selected element or section (an element with nothing selected gets a
+section of its own), selects it and announces it.
+
+What an email loads from elsewhere: no built-in block carries a sample picture, but social
+icons without a `src` of their own come from `www.mailjet.com`, and text without a
+`font-family` gets MJML's default, Ubuntu from `fonts.googleapis.com`. Both reach every
+reader's mail client, so name them wherever you list who receives your users' data.
+
 ## Copy
 
 Every word the editor renders comes from a dictionary with English defaults, so a host