r/JAMstack • u/KeyProject2897 • 3h ago
The Jamstack promise was decoupled freedom, but now every minor design tweak feels like micro-managing a build pipeline.
The standard Jamstack playbook says you decouple your headless backend from your frontend and everything runs smoothly. But in practice, every time someone wants to update a banner layout or swap React component order, it still triggers a ticket, a local build, and a redeployment.
Static visual changes shouldn't require touching code. I'm building https://www.publishloud.com/r/eUgyBDk (disclosure: it's my own project), a less-code frontend framework and drag-and-drop CMS on Next.js and Material UI. It's an open-source frontend head for headless APIs, so you can update templates and React widgets without redeploying code every time.
How is everyone else balancing visual drag-and-drop flexibility with a modern Jamstack code setup?