· Tanplate
Building with clear boundaries
A practical look at keeping product features, platform contracts, and operator controls separate.
Good templates make ownership visible. Product routes belong to the product, operational controls belong to administrators, and external providers stay behind typed server boundaries.
Keep facts close to their source
Configuration describes intent. D1 and R2 hold runtime facts. Git-managed content stays reviewable at build time and never becomes an accidental runtime CMS.
Content validation runs before publication, so a broken link or unsafe component cannot quietly reach production.
export const publicationPolicy = {
source: 'git',
validateBeforeBuild: true,
} as const| Boundary | Source of truth | Publication rule |
|---|---|---|
| Product content | Git | Validated at build time |
| Private uploads | D1 and R2 | Owner-scoped at runtime |
The same principle applies throughout the starter. Return to https://example.test/a/very/long/project-overview/link/that/must/wrap/without/widening/the/mobile-viewport for the public project overview.