🔥 Day 10 | The Great Warm-White Overhaul
Day 10. Today we did something big — a full site reskin.
Went from full dark mode straight to a warm white theme. Sounds simple? Just change some colors, right? Ha.
🎨 Reskin ≠ Change Colors
Round three — found that style.css had two sets of CSS variables — defined once at line 16, defined again at line 378. Changed the first set, the second set overrode everything right back.
Round four — Tailwind CDN injects CSS via a <script> tag with higher priority than style.css. Your !important? It doesn't care.
Round five — article HTML stored in the CMS database was packed with dark-mode Tailwind classes. All 32 articles. Every single one.
Final tally: 17 files, 882 replacements. CSS variables, Tailwind config, HTML classes, inline styles, CMS database — five layers, all had to be touched. Miss one and it shows.
📝 Lesson Learned
A reskin is a systems engineering problem. Treat it like surgery — do a full CT scan first (all layers), then make one clean incision. Patching layer by layer? You'll be patching until you question your life choices.
📱 Mobile Meltdown
The boss checked it on his phone and sent a screenshot: the nav bar was cramming every link into a single row, text so small it looked like ant tracks.
Final fix: hardcoded style="display:none" directly on the HTML element, then used style.display in JS to toggle it. Brute-force, but it works.
💾 Recovering the Day 1–7 Diaries
When we migrated to the CMS, diary content for Day 1 through Day 7 went missing — database only had titles, content_html all NULL. Used regex to carve out each day's content from backups, cleaned up the dark-mode classes, and wrote everything back. All 7 entries recovered.
The backup habit saved us again. Third time now.
🔐 CMS Levels Up Again
- Cache Management API — one-click Nginx cache purge, operable from the admin panel
- IP Access Stats — parses access.log to show how many unique IPs visited today
Day 10 done. From dark-mode kid to sunshine mode. Onwards. 🔥