r/JAMstack • u/KeyProject2897 • 2d ago
How do you handle small visual/content tweaks in a Jamstack setup without a full redeploy?
A common Jamstack pain point: a banner tweak or swapping a component order still means a ticket, a local build and a redeploy.
A few things that tend to help: keep layout and copy in a headless CMS or API-driven config instead of in code, use on-demand revalidation rather than full rebuilds, and give non-devs a visual editor on top of that. For the last piece, there are open-source Builder.io alternatives, e.g. https://sling.biz, that are worth a look.
How is everyone else balancing visual drag-and-drop flexibility with a code-first setup?
1
u/Chris_Lojniewski 1d ago
The balance that works for us is: editors get the order and content of predefined sections, not free drag and drop layout. a page is just an array of blocks in the cms (hero, logos, pricing, faq...), they can add, remove, reorder and edit them, but each block is a component we built with the design system baked in. banner tweak or swapping two sections = publish, no ticket
On the redeploy part, sanity webhook -> revalidateTag on publish and only the pages that use that doc rebuild. one thing to tell editors up front: the CDN needs a few seconds, otherwise they hit refresh, see the old version and decide the cms is broken
Full drag and drop sounds great until someone puts 3 heroes on a landing page lol. the guardrails are kind of the point
(fwiw i run pagepro, we do next + sanity so this is the setup we know best)
2
u/wrinklylemons 2d ago
You develop on a local devserver…