Qwik development: static docs and sites
Qwik is not our default, and that is the point: the Valibot and Formisch docs were already written in it, so that is what we worked in. Both sites now produce every page once at build time and serve it from a CDN cache.
What we do with Qwik
Pre-rendering off the request path
A documentation site shows the same pages to everyone, yet most are rendered on every visit. We moved 1,100 of them to the build without losing the single-page navigation.
The part that was actually hard
The pages were the easy half. Restoring each reader's chosen theme before the first paint took most of the work, and the write-up explains why.
Working in what you already run
We changed nothing about the project's framework choice and fitted into it instead. The hosting decision went back to the maintainers.
Qwik in our client work
Published projects that list Qwik in their stack.
Articles
Blog posts tagged Qwik.
Curious about what's next?
View all postsOpen source and docs
Our own packages and guides where Qwik does the work.
Other technologies
The rest of the stack, each with its own services and projects.
Maintaining a Qwik project?
Message usTell us what is slow or hard to maintain, and we will say whether we can help and how.
Can't keep up with changes in AI world?
Let us do the heavy lifting. Every week we distill the most important AI developments into a focused 5-minute briefing - so you stay ahead without the noise.
Find out more