← Back

Site Log

  1. The Genesis: Launched the initial site with a minimalist header and core posts functionality. Achieved perfect 100 scores in Lighthouse for both PageSpeed Performance and Accessibility. (Enjoy it while it lasts; a single tracking pixel is already planning its revenge.)
  2. The Animation Tax: Perfect desktop score regressed. Experienced a 2% performance hit after implementing the header button animation. This serves as a clear reminder of how even a subtle motion effect can measurably impact site performance. Apparently, the browser thinks my buttons are doing too much cardio.
  3. The Miracle: Score back to 100 after some changes: the mystery of Lighthouse O_o. I didn’t actually fix anything. I just stared at the code until it felt intimidated.
  4. Typography: Integrated Tailwind CSS Typography (prose) to ensure consistent styling for lists and complex formatting within post details. Now the text looks so professional I’m almost afraid to read it.
  5. Hydration Issues: Added some funky animations to the headline just for fun. Performance is still at 100, but some browser hydration errors are showing after deployment. (Vercel needs to drink more water? :P). My React components and my DOM are currently having a "who are you?" argument.
  6. The Ghost in the Machine: Errors are gone from Vercel logs but still showing in the browser, confirmed on both Chrome and Firefox. Will need to investigate further. It’s not a bug, it’s an undocumented "surprise feature."
  7. The Free Tier Curse: I changed the animations to be hardcoded in the context file instead of Sanity (since they need to be specified in the CSS anyway), but the browser error is still present and nothing at all in my local. I swear Vercel is punishing me for being cheap and using the free tier. I guess you get what you pay for→or in this case, what you don't pay for O_o.
  8. The Debugger Paradox: Tried using the Vercel debugging toolbar, but it’s currently busy generating more errors of its own than the ones I’m actually trying to fix. It’s like hiring a plumber who accidentally floods the basement while looking for a leaky faucet. Giving up on that specific error for now, as it appears to be a "them" problem (Vercel deployment environment) rather than a "me" problem (my actual code).