Qwik primer
Qwik is a resumable frontend framework that ships near-zero JavaScript by default. Meridian uses Qwik for the public marketing site and interactive demos where instant LCP matters.
Why Qwik
Unlike hydration-based frameworks, Qwik serializes application state into HTML and resumes execution on the client only when the user interacts. This eliminates the hydration tax entirely.
Component model
Qwik components look like React but use the component$ suffix. The dollar sign marks a lazy-loadable boundary — the optimizer splits code at every $.
Signals and state
Qwik uses fine-grained reactivity via useSignal and useStore. Signals hold primitives; stores hold deeply reactive objects. Both serialize into the HTML payload automatically.
Meridian integration
The Qwik site lives in a separate Vite-built project deployed to Cloudflare Pages. It calls Meridian APIs for license validation and downloads. No shared runtime — just REST boundaries.
Next step: Read the full Qwik documentation at qwik.dev for component patterns, routing, and the optimizer deep-dive.