Astro + Markdown: Thoughts & Experiments
Exploring the best practices for content-driven sites
Today I tried combining Content Collections with custom layouts. Turns out, you can really sculpt Astro like clay.
I explored how Markdown-based content can be dynamically routed and rendered using Astro’s layout system — without relying on the deprecated layout
key. Instead, using entry.render()
allows full control at the page level and makes it easier to wrap content in custom containers or themes.
Things I tried:
- ✅ Structuring content with Astro’s
src/content
+content.config.ts
- 🎨 Matching Markdown to global styles using
.markdown-body
- 🧱 Abstracting layouts for both projects and devlogs using Astro components
More experiments coming soon — this clay still feels fresh!