Route Map
ReferenceRoute inventoryLocale-first structure
User-facing routes are grouped under src/app/[locale].
This page is the quick route inventory for understanding which parts of the app are public, protected, and integration-facing.
Use this page for orientation
For the architectural explanation behind these routes, see Project Structure.
What this reference covers
Public routes
Marketing, auth, legal, and payment result routes that live under the locale-aware user-facing tree.
Protected routes
The dashboard route that depends on authenticated access and shared layout-level protection.
API routes
Server entrypoints used by auth, tRPC, and Stripe-specific integration behavior.
Current route inventory
Public routes
/(home)for the marketing site/auth/signin/auth/signup/auth/forgot-password/payment/success/payment/cancel/terms
Protected routes
/dashboard— single page with a section switcher (overview, customers, billing, settings)
API routes
/api/auth/[...nextauth]/api/trpc/[trpc]/api/stripe/checkout/api/stripe/webhook
Notes
Notes
- Locale middleware applies to user-facing routes
- dashboard protection is enforced at the layout level
- the dashboard uses a section-switcher pattern, not real subroutes
- some routes such as payment success depend on search params to display post-checkout state