SEO + AI-searchable foundation
Per-page metadata (lib/seo), schema.org JSON-LD (organization, website, FAQ, BlogPosting via lib/jsonld + XSS-safe JsonLd component), a full sitemap.xml (marketing + blog + industries, toggle-aware), robots.txt, and /llms.txt — the emerging AI-crawler descriptor (llmstxt.org) generated live from config + content so answer engines (ChatGPT, Perplexity, Claude) can understand and cite the site. Content sources expose clean getX() functions explicitly designed to swap static→CMS/API with no page changes.
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 today; CMS-swap-ready).
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
- Always on; fill site.config + content files.
- Who can use it
- public.
- The API behind it
none (static content today; CMS-swap-ready)- Where it lives
- /sitemap.xml/robots.txt/llms.txtevery marketing page (metadata + JSON-LD)
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.