I know that after trying both react and Next.js (on the t3 stack) I would have felt good actually publishing a webpage, but even with the second version of this website being almost built, I felt that there was still too much of a barrier to using the webpage.
I knew right then that the idea of using a Headless CMS was a major mistake, and that I needed to backtrack. Luckily I had recently heard about the astro framework, which was built to make it easy to make, publish, and maintain content websites. I had also heard about it’s numerous integrations, so I was intrigued.
After creating a new astro project, I promptly installed tailwind css. I used this in the past iteration of this project, so it would both save in the development time I had left, as well as the time taken to port over the website. While I had initially thought that I might need to use a framework integration for writing more js (I was considering exploring solid), I realized that my current needs were met with the simple astro framework feature set.
I am currently porting over all of my components from Next js and continuing to write this post, and I have learned two things.
The former is good news because it means that I am coping most of my components as-is, but shows how silly my reliance on a framework has been. The only thing that I used react features for was managing state, which is easily doable within astro.