Cloudflare Docs ↗
A frozen documentation corpus, strict output audits, and a transparent comparison of Nift and Astro build workflows.
Read the experiment →Nift Labs / Collection 01
Experiments using substantial public content corpora to explore build performance, implementation choices, and the experience of working with Nift.
The collection
Independent designs. Shared curiosity.A frozen documentation corpus, strict output audits, and a transparent comparison of Nift and Astro build workflows.
Read the experiment →An agentic reconstruction of a production-shaped website. Build speed, dependency footprint, and developer experience under the microscope.
Read the experiment →One production site, two migration philosophies. Faithful MDX authoring and an agent-maintained HTML reconstruction, compared with the original Astro build.
Read the experiment →A real Hugo documentation migration. Preserved Markdown and maintained HTML, with publication parity, profiled builds and explicit maintenance tradeoffs.
Read the experiment →Authoritative Markdown or maintained HTML: a faithful production publication, profiled source derivation and measured everyday iteration loops.
Read the experiment →Three production workflows, retained React islands and two source models. Faithful publication, profiled builds, memory and coordinated maintenance.
Read the experiment →962 routes and retained React islands. Authored and rendered source, production iteration, fresh-state costs and qualified memory evidence.
Read the experiment →Migration and rewrite closed as unsuccessful: retained runtime costs versus an expensive generated corpus pipeline. Two distinct findings, preserved parity and qualified measurements.
Read the experiment →Public-output reconstruction, scoped visual/playback parity, and two Nift source models. No private SpaceX build benchmark.
Read the experiment →A 2,003-page documentation publication retaining TanStack Start and React, with lower observed build time and memory and dependency-aware incremental work through Nift.
Read the experiment →A note on method
We use real public content corpora and explicitly labelled generated fixtures to investigate build-system performance and implementation characteristics. Unless a report explicitly says otherwise, these are independent interpretations rather than pixel-perfect migrations.
Exact upstream commits are recorded where available so each result can be tied to a specific corpus. Each report describes its measurement boundaries, evidence, and limitations.