I did it. I added a projects section to the blog. You know, like every other developer with a personal site who thinks their half-finished weekend experiments deserve a dedicated page with screenshots and status badges. I am no different. I have seen the beam in my own eye and it says “active”.
Behold: the /projects page
Cards. Grid layout. Thumbnails. Status pills that say active (delusional), completed (rare), or archived (the natural state of all software). Each card has little icon links to the live demo and the GitHub repo where the README still says “coming soon” from 2024.
Some projects are featured on the homepage, which is a very generous way of saying “the ones I’m least embarrassed by”. It’s like a highlight reel except the highlights are just things that compile.
What happens when you click
You get taken to a full detail page. Big screenshot. Description I clearly wrote in 30 seconds. Tech stack tags that are basically my way of saying “yes, I too have used Tailwind”. Share buttons are there so you can aggressively send my projects to people who will open the link, nod politely, and close the tab within 4 seconds.
There’s even prev/next navigation between projects, as if you’re going to sit here and browse through them like it’s a catalog. You’re not. Nobody is. But I built it anyway because pagination is a disease and I am patient zero.
Search too, apparently
The search page now lets you filter by Posts or Projects. This is the part where I pretend anyone is going to use that filter intentionally instead of just typing “astro” and hoping for the best.
The honest truth
I built this feature because I kept mentioning side projects in blog posts with nowhere to send people. It was like name-dropping a restaurant that doesn’t have an address. Embarrassing. So now I have a place. Whether the projects themselves are worth visiting is between you and your standards.
Anyway, the projects page exists now. Come look. Or don’t. The archived ones weren’t going anywhere anyway.