At my company, we build software every day because our business is running a job board.
We always had kind of an impedance mismatch when it comes to creating content pages (think landing pages for marketing).
Yes, we can do this ourselves, but then software engineering resources are in conflict between shipping the next feature and creating landing pages.
So we introduced Webflow. Now marketing could create their content themselves. Did it match our corporate identity? Hopefully. Was it technically sound? Sometimes. Was it fun for software engineers to fix things in Webflow. No.
It kind of worked, but wasn’t exactly ideal.
Meanwhile, software engineering became more and more productive with the advent of AI coding agents, Cursor in our case.
So we tried another approach: giving our content creators Cursor.
But that was brittle, too: Cursor presents an overwhelming complex UI for someone who never used an IDE before, it could do a thousand things while only three are actually needed in this use case, you have to explain git on top of Cursor. It kind of worked, but only kind of.
So we sat down and built https://dx-tooling.org/sitebuilder/
It’s like a hyper-focused „Cursor light“ in the browser, so our content creators can just „chat away“ and create their content pages, with all the guardrails baked into the product. Getting tracking pixel integration etc. right just works. Matching our style guide perfectly just works.
And as a bonus, there is a whole git based storage and versioning workflow underneath, so software engineering can support and test and deploy the results with their preferred tools and methods, but none of this complexity leaks through to the content creators.
We built this ourselves in days, not months, thanks to Cursor, but it’s not vibe-coded — it’s a rock solid application that we will support and improve long-term without headaches: https://github.com/dx-tooling/sitebuilder-webapp