About / Specs
What powers Stratatouille
A living inventory of what Stratatouille is built on: open-source libraries, AI services used to build and run it, and external data sources. Expect this to fill in as the app grows.
Foundation
- SSR-friendly React app shell and file-based routing
- MITUI runtime
- MITBuild tool and dev server
- Apache-2.0Type safety across the codebase
- Styling via semantic tokens in src/styles.css
- Server-state cache and loaders
- Accessible component building blocks
- Form state and schema validation
- OFL-1.1 (fonts) + MIT (packaging)Self-hosted web fonts — no third-party font requests
Backend & infrastructure
- Apache-2.0 + hostedDatabase, email/password auth, row-level security, and Edge Functions (e.g. the server-side welcome email)
- Cloudflare Workers runtimecommercialServerless edge runtime for SSR and server functions
- MITPackage manager and JavaScript runtime
- commercialTransactional email from a verified stratatouille.com sending domain — the welcome email is sent server-side by a database trigger and Supabase Edge Function on email confirmation, and Supabase’s auth emails (confirmation, password reset, magic link, and the rest) go via custom SMTP
- commercialPrivacy-friendly, aggregate visitor analytics — page views, referrers, device type, and approximate country. No advertising, no cross-site tracking, and no personal data collected. Served first-party; see the Privacy Policy for what it does and doesn’t capture.
External data sources
- CC0Structured historical context — preset lanes plus live import of people and office-holder series (SPARQL / wbsearchentities). Imported lanes link back to their Wikidata source.
AI services
- commercialAI-assisted product development environment
- commercialArchitecture, code review, and planning alongside Lovable
Quality & tooling
- MPL-2.0Automated accessibility (WCAG) scanning of our pages
- MITUnit tests for the pure, load-bearing logic — the date parser, timeline scale, and Wikidata transform
- Apache-2.0Whole-codebase typecheck
Tools we run to verify quality — they don't ship in the app. Today we run these as a manual pre-push gate; automated CI is planned.
Accessibility
We build to WCAG 2.1 AA: semantic HTML, full keyboard operability, and labelled form controls. The comparison view never relies on colour alone — every lane pairs a hue with a shape marker — and offers a text-table equivalent of the visual. We're partially conformant with known gaps; read the full Accessibility Statement.