NextBlock™ CMS | We ditched hardcoded schemas to let users (and AI) build custom CMS blocks on the fly.

If you've ever managed a CMS for a client, you know the dreaded request: "Can we get a custom block that looks exactly like this?" Usually, this means opening up your codebase, defining a new schema, mapping it to your frontend components, and waiting for the Vercel pipeline to redeploy. It's a massive friction point.

For the NextBlock Beta, we wanted to give users total control to build, duplicate, and edit their own blocks directly from the dashboard.

To do this, we had to rethink how blocks are stored. We built a Dynamic Schema Engine where custom blocks aren't hardcoded files; they are strict PostgreSQL JSONB data definitions. They inject at runtime directly into our Tiptap editor and Next.js 16 pipelines. No redeploys. No HTML sanitization tax. Just instant UI generation.

But here is where it gets really fun.
Because the entire block architecture is now just pure data (JSONB) instead of hardcoded React/TypeScript, you don't even have to build the widgets yourself. We fully integrated this with our Cortex AI. You can simply describe the layout you need—for example, "Build a Testimonial block with an R2 image avatar, a rich-text quote, and a 5-star rating toggle"—and Cortex AI will autonomously generate the schema, build the custom widget, and make it instantly available in your slash-command menu.

Zero code. Zero redeploys. Instant custom blocks.

Jump into our ephemeral sandbox and let me know what you think of the DevX (try getting the AI to build something crazy): https://nextblock.dev