Configuration

Handlet keeps product behavior in typed configuration files rather than scattering path strings and feature switches through components.

Important files

apps/web/config/
├── paths.config.ts
├── feature-flags.config.ts
├── pricing.constants.ts
├── personal-account-navigation.config.tsx
├── team-account-navigation.config.tsx
└── legal-links.config.ts

Paths

paths.config.ts is the canonical source for marketing, auth, and app route strings. Use it when linking between product surfaces so route changes stay centralized.

Navigation

Personal and team workspace navigation are separate because team URLs use the workspace slug in /home/[account]. Do not use organization IDs in routes or database columns unless the tenancy model is deliberately changed.

Feature flags

Feature flags gate surfaces that are still staged or operationally controlled. When a flag changes what a user can see or do, update QA flow documentation.

Content

Marketing docs, help content, blog posts, and changelog entries are MDOC content loaded through the CMS client. Content changes should keep frontmatter status, order, and publish date accurate.