We recently changed our architecture to include interactivity without having to pre-render all combinations. Pages are still pre-rendered with their initial con

We recently changed our architecture to include interactivity without having to pre-render all combinations. Pages are still pre-rendered with their initial content, but each Evidence app now ships with filter components and an in-browser DuckDB instance so you can build interactive apps. We call this Universal SQL - if you're interested, we wrote up our rationale for doing this here: https://evidence.dev/blog/why-we-built-usql/ https://evidence.dev/blog/why-we-built-usql/ Here's an example project with some filter components and custom styling: https://ecommerce.evidence.app/ https://ecommerce.evidence.app/ This is still a static app - the data warehouse was only hit during the app's build process