Why I shifted to mkdocs and it just works!¶
I have been shifting quite a lot between different options for sharing written content online. It should cater to all of these needs
- Regular blogs
- Walkthroughs (e.g. creating a guide for Actuarial Exams)
- Highly customizable
- (yet) Easy to maintain
I started by copying Lee Rob's portfolio website (that also helped me learn Next.js). But to add a new feature, add a new blog post was a big headache.
Then, I started using Quartz (since I was using a lot of Obsidian, and it was a no-brainer. That's when I also realized that the system that should be used, should be extremely frictionless and content-focused). However it was not customizable and I found it a bit weird and templatey.
Then I tried making two websites on Svelte, taking inspiration of a design from Dribble. But I eventually realized that I was going back to step 1. It was just too hard to maintain.
So, I needed a readymade solution. Since, I was already motivated to learn Svelte Kit, I tried looking up someone else's blog example implemented in sveltekit and stumbled upon urara.dev. But it was just someone's implementation and was buggy.
I realized that I didn't need something that was too flashy. But something that just works and works very well for all my requirements.
That's when I found out about Material theme for mkdocs (which is the website you are reading this blog on). And it was a one-time effort to set it up. After that, all I needed to do was focus on my content. That's all!