Implementation and maintenance
Platform and tenant boundaries
Extend Boise Today within Townwell without contaminating another publication or flattening the two visual scopes.
On this page
Boundary map
| Layer | Responsibility |
|---|---|
| sites/boise | Publication branding, curated city content and Boise-specific data adapters. |
| sites/index.ts | Tenant resolution from SITE_ID / NEXT_PUBLIC_SITE_ID; capture forces boise. |
| Public routes/components | Reader navigation, stories, search, discovery and site shell. |
| Admin routes/components | Authenticated publishing, review, media and operational management. |
| Data/services | Database, provider requests, classification and integration contracts. |
| CSS scope | Public root themes with nested admin-shell/login overrides. |
Implementation rules
- Reuse the nearest source primitive before adding another interface variant.
- Keep Boise labels/configuration separate from shared platform logic.
- Do not add unfinished features to public links or sitemap solely because this guide inventories them.
- The portfolio guide does not alter the Townwell runtime or tenant behavior.
Source references
| File | Responsibility |
|---|---|
| sites/index.ts | Audited Townwell implementation; use this file when extending this interface. |
| sites/boise/config.ts | Audited Townwell implementation; use this file when extending this interface. |
| sites/types.ts | Audited Townwell implementation; use this file when extending this interface. |
| app/globals.css | Audited Townwell implementation; use this file when extending this interface. |
Reference downloads
Related topics
Source audit: 2026-10-07 · Revision ce8bc72b96da · Documentation v0.1