Industry showcase pages (optional, data-driven)
Public /industries/:slug landing pages tuned to a vertical (lawn care, cleaning, home services, events out of the box) — each is one object in lib/content/industries.ts, so adding/removing an industry is a data edit, not code. The whole section is a config toggle (siteConfig.optionalPages.industries): off → the routes 404 and the nav link vanishes. The pattern extends to any optional feature area.
If you are building a front end
Your front end calls this over the same-origin `/api/v1` proxy — no backend code to write, no schema to design. Endpoints: none — static content.
Bring any front end — hand-written, or generated with Lovable, v0, Bolt, Claude, or Cursor. You get auth, a multi-tenant database, payments through your own Stripe, and email/SMS without writing or hosting a backend.
- How to turn it on
- siteConfig.optionalPages.industries (default true); edit/trim lib/content/industries.ts for your market.
- Who can use it
- public (PUBLIC_PATHS /industries); toggle-gated at the route via notFound().
- The API behind it
none — static content- Where it lives
- /industries/industries/:slugmarketing nav
Machine-readable
This page is generated from our published capability catalog. Point your AI assistant at /features.json (or /llms.txt) and it can read every feature, how to enable it, and the endpoints behind it — then build against them.