Architecture Map
Help teams understand boilerplate boundaries and extension points before they start coding.
Recommended approach
Map the template into four areas:
- frontend app modules
- backend domain modules
- shared workspace packages
- delivery/tooling layer (CI, lint, tests, proxy)
Implementation checklist
- Document package ownership and boundaries.
- Identify where new domain modules should be added.
- Keep architectural map in sync with template releases.