Guides
Guides answer “I want to do X — show me.” They assume you have read the relevant Concepts page and now want a concrete recipe.
A guide is short and runnable. It does not re-explain the underlying model — it links to Concepts when context is needed and to Reference when an exhaustive parameter list is needed.
Available guides
Section titled “Available guides”| Guide | When you reach for it |
|---|---|
| Add an entity to a feature | A second entity in a feature you already have. |
| Write a custom write handler | Default CRUD doesn’t fit; you need business rules on save. |
| Restrict a field to specific roles | A column visible to admins only, writable by everyone. |
| Expose a public, anonymous-readable endpoint | Public status pages, marketing landings, hosted reports. |
| Call the API headlessly with a Personal Access Token | CI, a script, or a customer integration needs a long-lived, scoped bearer token. |
| Add TOTP-based 2FA to login | Users should enroll an authenticator app as a second login factor. |
| React to another feature’s events | Feature A reacts when feature B writes — without imports. |
| Seed default data for new tenants | New tenant signs up; populate their workspace. |
| Apply one-shot data migrations via the event store | A role changed name, an admin needs an extra membership — run it once, tracked, ES-conform. |
| Build a read model across multiple aggregates | Aggregate events from several entities into one view. |
| Dialog and Lightbox overlays | Confirm modals vs full-size image preview; Apex screenshot zoom. |
| Make your apex/content pages SEO/AEO/GEO discoverable | You mounted seo but don’t know what to actually configure to show up in search/answer engines. |