Markdown makes the article itself portable. It can be reviewed in a pull request, edited in a familiar text editor, and transformed into HTML during the build without a database connection.
Keep metadata predictable
Frontmatter provides the small amount of structure the website needs:
title: 'An article'
description: 'A short summary'
pubDate: 2026-08-18
author: 'Author name'
tags:
- 'topic'The body remains flexible, while the fields used by the index page stay typed and consistent.
What this workflow does well
- version history is built in;
- drafts can be kept beside published articles;
- the output is fast and cacheable;
- content changes are easy to review;
- there is no editor account to maintain.
| Need | Markdown workflow |
|---|---|
| Long-form writing | Excellent |
| Structured metadata | Strong with a schema |
| Real-time collaboration | Limited |
| Complex permissions | Better handled by a CMS |
Choose the right boundary
Markdown is not a replacement for every publishing system. It is a good fit when the repository is already the source of truth and the team values transparent, reviewable changes.
The best content system is the one whose workflow people can follow without inventing a second workflow around it.