The idea here isn't to add a CMS too soon. It's to separate content and presentation, keep everything versioned, and be able to generate listings, details, and sitemaps from a single source of truth.
WHAT I'M BUILDING
Markdown Editorial System
Editorial system that transforms Markdown into structured content ready for web, SEO, and scalability.
Editorial system that transforms Markdown into structured content ready for web, SEO, and scalability.
Editorial system for blog, projects, and services within the same repo, without adding a CMS too early.
Current status
building
Main stack
Node.js, Markdown, Angular
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.
Services
- Content Systems
I structure your content (blog, projects, pages) to be scalable and maintainable.
- Product Implementation
I deliver real improvements to your product without breaking what already works.
Other projects
Personal PWA Website
Personal content system where I centralize blog, projects, and services on a scalable base.
AI Automation Laboratory
Automation system with agents to execute real code, review, and content workflows.