Markdown-driven Reads

Markdown keeps writing close to the code that presents it. Each post is a plain file in the repository, with frontmatter for structured metadata and body content for the article itself.

That means Reads entries can be edited in Decap CMS, reviewed in Git, and exported as static pages without adding a database or server runtime.

This section uses the same filesystem content approach as the rest of the portfolio, so new posts only need a Markdown file in content/reads.