The Rebode Blog — Headless CMS, Shipped Fast

Leadership wanted a blog and gave me a month — two if I stretched it. The goal: SEO, traffic to the main site, and honest answers to the questions every kitchen remodeler asks. I architected it, stood up the repo, modeled the content in Kontent.ai, and shipped on time.

My favorite part isn't the deadline. It's that the content team never needed a developer to publish an article again — that was the whole point of going headless. I built the content models, the predetermined styles and layouts, and the environment workflow, then trained the team to take it from there: write, add images, publish to the right environment.

I owned alpha, beta, and every release after, and worked with the infra team on the automation pipelines for content and deployments.

I influenced this design heavily — about 90% of what's live is mine. That took some lively conversations with creative leadership about UI/UX best practices. I made my case, they came around, and the result speaks: the blog had the fewest requested fixes of any Rebode property.

FIX REQUESTS OF ANY REBODE PROPERTY

FewestFIX REQUESTS OF ANY REBODE PROPERTY