Customization Guide
This guide defines where the starter kit is expected to change when a buyer adapts it into a real product.
The point is to make customization predictable. Product rules, branding, auth choices, billing behavior, and workflow changes should land in known places instead of spreading through the repo without a boundary.
Customization Areas
- branding and theme tokens
- marketing copy and imagery
- route-level product flows
- auth, billing, and policy decisions
- domain workflows inside org, portal, and platform surfaces
- integrations and notifications
Documentation Rules
- document the owning file path or system for each customization area
- separate stable platform behavior from store-specific overrides
- keep one canonical place for each configurable concern
Good Follow-Up Docs
- brand and content model
- auth provider decision guide
- billing and subscription customization
- email and notification customization
- domain-model extension guide