Migrating my website from Gatsby to Astro

1

Tailwind CSS

Instead of some UI framework/styling solution which was specifically tailored for React, I went with Tailwind CSS. It is hugely popular, has good support for almost all the frameworks, is a 1st party plugin from Astro and was great to get started with. For my posts I chose MDX and for components in MDX I chose React.

#Developer Tools #Design Tools #Website Design 868 social mentions

2

Swup

Like Gatsby or Next, Astro does not have any client side navigation. So each link click triggers a full page reload. Astro recommends to use Swup as mentioned here. Turbo is also another option though the team does not recommend it. I'm currently using Swup which I'll probably switch from or completely remove it as I have added TOC to MDX and clicking on a title is not redirecting the page to that particular section.

#Design Tools #Placeholder Images #Developer Tools 12 social mentions

3

React

The year was 2019 and I wanted to build a website using React. I had some experience in it, having done a project during my 3rd year of engineering but I wanted my site to be SEO friendly, fast, have client side navigation and good DX.

#Javascript UI Libraries #JS Library #JavaScript Framework 775 social mentions

4

Next.js

So after researching, I found two frameworks which fit my bill perfectly: Gatsby and Next.js. I wasn't going to call any APIs and my content was all going to be static so I did not need any SSR solution. And since Gatsby had excellent plugin support I decided to go with it.

#Developer Tools #Web Frameworks #JavaScript Framework 923 social mentions

5

BlurHash

No blurhash for images like Next or Gatsby.

#Placeholder Images #Design Tools #Web Development Tools 8 social mentions