Why we built DragDrop
Every CMS forces a trade-off between editor UX and developer control. We don't think that trade-off is necessary.
Most CMS platforms force a fundamental trade-off: either give your editors a great experience (and lose developer control) or give developers control (and force editors into a YAML-shaped hole).
When we started DragDrop, we wanted both. Editors should drag blocks visually. Developers should author those blocks in real TypeScript, with type-safety, IntelliSense, and the ability to test locally.
The answer was letting every block open as real code, right in the studio, with a friendly schema-driven editor for everyone else. Same blocks, two doors in.
A few years in, this bet has paid off: editors and developers actually use the same tool, which has never been our experience with traditional CMSs.
There's more we want to do. Custom data models. AI-assisted block authoring. Live collaboration. We're just getting started.