Attempting a Visual Upgrade
Today, I set out to make some visual improvements to my project. The first idea was simple: swap out the plain background for a watercolor-style image to give the site a bit more personality. But once I applied it, it just didn’t look as good as I had imagined. Not a huge setback, I decided to shelve that idea and revisit the visual direction later with fresher eyes.
The Mysterious Font Reversion
Then I noticed something unexpected: the font had suddenly reverted to the tailwind css default, instead of the one I had originally specified. I thought this would be an easy fix, but it turned into quite the rabbit hole. I tried updating layout.tsx, global.css, and page.tsx with the font settings again, but somehow that broke my CSS altogether.
The Cost of Not Committing
Here’s the embarrassing part: I hadn’t been using Git commits properly up until this point. That meant I had no easy way to roll things back. So I spent a lot of time manually undoing changes in each .css and .tsx file until I finally got the CSS working again. If this had been a client project, I can only imagine how panicked I would've been.
A Small Win, but Not Quite Done
Eventually, I managed to get the site back to its previous visual state, but the font issue still isn’t resolved. It’s still displaying the default font, and I’m not sure why. I decided to finally commit my code (lesson learned!), and call it a day.
Plan for Tomorrow
Tomorrow, I’ll start by focusing on other visual improvements first. Once those are in place, I’ll return to the font issue with a clearer head.
Date: June 18, 2025
tags: portfolio, webdev, copywriting, ux, learning
Top comments (0)