Content Drive
I lead it: I plan it with product, split and delegate the work, build it, test what I delegated, and answer for how it turns out. Product brought the vision and the design; I make it real, and push back when something can be better.
Why it exists
Managing content is the heart of a CMS, so it has to feel excellent. In dotCMS it was split across two tools, the Site Browser and Content Search, and both felt clunky.
Content Drive brings both into one modern place, and goes further: you edit, move, copy and delete content, and organize it in folders, without switching tools.
Key decisions
-
Saying no, close to a deadline
While every team was rushing for a deadline, I said no to extra work. It wasn't easy, because it affected other teams, and there's no black and white in those moments, only trade-offs. Scoping it that way kept the project on course.
-
Challenging the design to make it better
Product owns the vision, and I build it. When something could work better for the people using it, I said so, and we changed it together.
-
The details are the job
I'm a UX-minded developer and I watch the details closely. In a CMS, managing content is the product, so every interaction has to feel right.
See it work
The hard part
The hardest part was communication. The project grew until it reached into other people's projects, for good, but that took coordination across teams, and keeping track of its blast radius got hard. Once we saw it, we managed it much better.
It's also the first project I lead on my own. Organizing myself was hard at first; I caught up, and gained the confidence to handle it. It made me grow a lot.
Where it is now
Almost there: we're building the last features and polishing it for release. So far it has been really well received.