Skip to content

Paths

Pick a path. Read in order. Ship.

Track-ordered prev/next is mechanical. A path tells you the WHY of the order — same docs, different framing per scenario. Pick the one that matches what you are shipping; the rest of the docs stay reachable from /docs/ when you need them.

Path 1 ~half a day

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.

Outcome: A new theme dir + sample registered with the picker, light + dark verified.

5 docs · ~117 min reading Walk this path
Path 2 ~one to two days

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).

Outcome: A custom block class with a custom Settings panel rendering inside your Builder.

4 docs · ~146 min reading Walk this path
Path 3 ~one day

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.

Outcome: A multi-tenant Builder posting to your auth-protected save endpoint with assets on S3.

3 docs · ~85 min reading Walk this path
Path 4 ~two to three days

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.

Outcome: A complete BuilderJS integration: theme, extension, backend, multi-language — production-ready.

11 docs · ~283 min reading Walk this path

Don't see your scenario? Browse all 15 docs and pick what you need.