When content lives inside the template, publishing becomes more expensive than it should be.
The minimal solution isn't always a CMS. Often it's enough to model the data well, version it, and generate artifacts that the app can consume clearly.
HOW I CAN HELP
Content Systems
I structure your content (blog, projects, pages) to be scalable and maintainable.
I structure your content (blog, projects, pages) to be scalable and maintainable.
Content is embedded in components and every editorial change costs too much.
Editorial sites, personal websites, and products that want to grow without relying on hardcoded HTML.
Content contracts
Versioned source of truth
Slug-based resolution
Consistent metadata and sitemap
Projects
- Markdown Editorial System
Editorial system that transforms Markdown into structured content ready for web, SEO, and scalability.
- Personal PWA Website
Personal content system where I centralize blog, projects, and services on a scalable base.
Blog
- Modeling Content Without Hardcode: A Simple Base for Blogs and Case Studies
How to move from hardcoded content to a versioned system with clear models and defined responsibilities.
- Angular 21 and Intentional Routes: Leaving the Template Without Breaking the App
How to simplify legacy routes, define canonical URLs, and prepare Angular for real content without rewriting the app.