For years, the default way to build a content-driven website was to install a CMS, configure a database, choose plugins and maintain that entire ecosystem. For this site I chose the opposite direction.
The new ronaldrangel.com.co is built with Astro, and the content in this section lives in Markdown files: plain text with a small metadata block at the top.
Fewer layers, more control
I do not need an administration dashboard every time I want to publish an idea. I need to write, review and publish.
Each article is a file. The repository keeps the change history, and the site rebuilds whenever content changes. That removes a significant part of the maintenance surface that usually comes with a traditional CMS.
Speed as an editorial decision
Speed is not only technical. It is part of the experience.
A page that loads quickly, does not shift while rendering and does not force the browser to execute unnecessary JavaScript lets the content reach the reader sooner.
Astro fits that idea because the site can be delivered mainly as static HTML and send JavaScript only where it actually adds value.
Content still comes first
Using Markdown does not mean giving up SEO, images, categories, dates, Open Graph, structured data or bilingual versions.
All of that is generated when the site is built.
The difference is that the editorial system stays small: one text file, one review and one deployment.
It is not the right solution for every project. For this one, it is.