The problem with nightly registry builds
For three years, every Designali block, icon and template was rebuilt by a single cron job at 02:00 UTC. It worked until designali.com grew past 460 blocks and 4,000 icons.
The job had grown to 47 minutes. A failure meant a full rerun, and a broken registry for everyone.
Moving to incremental snapshots
We split the build into per-item snapshots that rebuild whenever a source file changes. Each snapshot is small enough to finish in seconds and cheap enough to retry.
The hard part was not the pipeline. It was agreeing on what a consistent registry means when blocks and their dependencies change out of order.
What changed for customers
The registry is now at most four minutes stale. Support emails about missing blocks dropped by 81% in the first month.
Our Vercel bill went up a little. Nobody has asked to switch back.
What we would do differently
We would have invested in a replay tool on day one. Debugging a snapshot means reconstructing the exact order of events that built it, and we did that by hand for weeks.
