Back to More
Changelog

What's New on This Site

Transparency builds trust. Every update, improvement, and fix — documented here.

Releases

v1.3.0v1.2.0v1.1.0
3releases
20+features
4bugs fixed
v1.3.0Latest
June 2026
New
  • Dev Vocabulary — A-Z glossary of developer terms, one sentence each
  • Behind the Error — HTTP status codes decoded and categorized
  • Concept in 60s — Quick explainers starting with debouncing vs throttling
  • Challenge of the Week — Weekly coding challenge with solutions
  • Collab Corner — PR etiquette, Git workflows, and team collaboration tips
  • Code Roast — Bad code patterns reviewed with honest roasts and fixes
  • Batch 3 cards: CSS Magic, React Deep Dive, API Explorer, Dev Design, CLI Power, Side Project
Improved
  • More page now has 18 content cards across 3 batches
  • Navigation flow improved between content pages
Removed
  • Orphaned terminal overlay removed from easter eggs (Konami Code was the only trigger)
v1.2.0
June 2025
New
  • Added Changelog card — because transparency matters
  • Added Resource Drop section with curated dev links updated weekly
  • New Bug of the Week card is now live
  • Stack Breakdown — real product architecture deep-dives
  • Launched Framework Wars — honest head-to-head comparisons
  • GitHub Gems — underrated repos worth starring, handpicked weekly
Improved
  • More page redesigned — cleaner layout, new card categories
  • Navigation flow improved between content pages
Fixed
  • Easter egg keyboard shortcuts now case-insensitive
  • Reduced easter eggs from 21 to 12 — higher quality, less noise
v1.1.0
May 2025
New
  • Launched Dev Tips section with VS Code, Terminal, and CSS tips
  • Tips & Lifehacks card with student-focused productivity content
  • GitHub profile link added to the footer
Improved
  • Improved page load speed by lazy loading card images
  • Rewrote About section — shorter and more honest
Fixed
  • Mobile menu was not closing after clicking a link
  • Contact form was submitting without validation

What makes a good changelog

Be specific

"Improved performance" means nothing. "Reduced load from 4.2s to 1.8s" means everything.

Be honest

If something was broken and you fixed it, say so. Accountability builds trust.

Keep it regular

Even small updates deserve a log entry. Frequency signals that the project is alive.

Version it

Semantic v1.x.x or date-based June 2025. Either works — pick one and stick to it.

Update frequency

Update typeCadence
New card or sectionLog immediately
Bug fixesWeekly batch
Design changesLog immediately
Content updatesMonthly summary