Hi! I'm Anca,
a superkitty majordomo, herbalist in training,
full-stack dev with an interest in DocOps, and other things.
This is my digital garden. Enjoy your stay.
To Shiki or not to Shiki, that is the question. The latest Shiki update broke my setup and I had the perfect excuse to try out Expressive Code. But it doesn't come with support for Markdoc. It's custom-component time!
In an effort to simplify my life and workflow, and reduce some costs, I'm moving my blog & domain from Netlify & Namecheap to Cloudflare Pages and the Cloudflare registrar.
The Astro Markdoc integration will not work for me as long as it doesn't use the `.md` extension. The Astro experience with plain ol' Markdown and my Obsidian is so good I can't imagine sacrificing it for anything less capable.
Astro Markdoc doesn't have feature parity with Markdown yet. Here are my Astro Markdoc solutions for linked headings, table of contents, external links in the Markdoc body, Shiki code blocks with a custom theme, and more.
Converting the blog to Astro was a more significant win than initially expected. A bit more time with the documentation of Astro, Obsidian, and Markdoc, and things went 100% green. On all counts.
On each tag page, you can find a link to that tag's RSS feed so you only get the content you want.
