I published my first-ever blog post on July 29, 2006 (17 years ago!). Since then, I have continuously revamped my site and blog.
After several years, I have once again revamped my site, this time with a completely new tech stack using Astro framework. Previously, it was built with Next.js. I thought I would write to share why I chose Astro for building my site, including the blog.
For those closely following front-end technologies, it’s apparent that the lifespan of frameworks (including UI frameworks, meta frameworks, etc.) and platforms (like WordPress, Medium, etc.) is quite volatile. As years pass, your site can become outdated. Adding a new feature or touching the site’s codebase often forces an upgrade or migration to a newer version. Switching to a new tech stack can be challenging, especially if the chosen framework is highly opinionated, making migration costly.
My criteria for selecting a tech stack for my site were:
I’ve purposefully avoided using framework-specific semantics, prioritizing features provided by the web platform itself. This approach reduces the learning curve and concerns about potential deprecation of framework APIs.
I’m hoping this site remains evergreen (fingers crossed). You can view the source code of this site at abhiomkar/abhiomkar-astro.