-
Quickstart
Start with the canonical 5-minute boot so you have the engine running BEFORE you start swapping the storage layer. Skip if you already shipped a quickstart.
-
Wire a real backend
The full save / load / asset / auth / multi-tenant adapter map — 8 patterns, 9 code blocks, 60 minutes round-trip. Pick the patterns that match your stack.
-
i18n locale packs
Translate the editor for your buyers — three namespaces, runtime locale switcher, Intl number/date formatting, RTL languages. Ship a French build in 20 minutes.
Outcome A multi-tenant Builder posting to your auth-protected save endpoint with assets on S3.
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 4
End-to-end — read everything in shipping order
The full sequence — every doc in dependency order. Spend two to three days; you will end with a production-grade theme + extension + backend + locale pack ready to ship to your first paying buyer.