-
Quickstart
Boot the engine. Five minutes from extract to a running canvas.
-
Architecture
Internalise the three-container UI + Page → Block → Element hierarchy + iframe canvas boundary.
-
JSON structure
Read a saved page and recognise every node — the JSON IS the contract.
-
Theme overview
Mental model for themes before you touch one.
-
Create a sample
Author a sample inside the default theme — the lock-step copy-along that locks the mechanic.
-
Create a theme
Spin up your own theme dir.
-
Layout best practice
Lock the layout invariants that hold up across email clients.
-
Build a custom Element
Add a custom block class.
-
Wire a real backend
Wire a real Save endpoint + asset storage + auth.
-
i18n locale packs
Translate the editor for your buyers.
-
FAQ
Read the FAQ ONCE you have shipped — half the answers click in only after you have seen the problems.
Outcome A complete BuilderJS integration: theme, extension, backend, multi-language — production-ready.
Other paths
-
Path 1
Author your first theme
Ship a brand-true theme — fork the default, author a sample, lock the layout rules. Five docs, half a day, one theme dir you can ship to production.
-
Path 2
Extend the engine with custom code
Ship a custom Element, Control, and Widget — the three extension points the engine exposes. By the end, the editor is bent to YOUR domain (not the email-marketing default).
-
Path 3
Wire BuilderJS into a real backend
Move from local-only Save to a production stack — MySQL persistence, S3 uploads, session auth, multi-tenant isolation, multi-language locale packs. Three docs, one shippable SaaS shape.