Skip to content

💡 Idea #10: Website Changelog — Versioned Timeline

Field Detail
Priority 📌 Important
Status ✅ Complete
Category 🎬 Content / 📚 Documentation
Date added 2026-04-04
Completed 2026-04-04

The Idea

Create a versioned changelog that documents the entire evolution of the A Guide to Cloud ecosystem — from the early WordPress days through to today's Hugo + Azure Static Web Apps platform.

Why This Matters

  • Memory — As the project grows, it's easy to forget what was built and when
  • Credibility — Shows the journey from template-based hosting to a fully custom, automated platform
  • Teaching material — Great content for YouTube ("How I rebuilt my website from scratch" series)
  • Onboarding — If anyone joins the project, they can see the full history at a glance
  • Pride — Look how far we've come in just 10 days! 🎉

Implementation

Aspect Detail
Format Semantic versioning (V0 → V1.0 → V1.1 → V2.0 etc.)
Style Chronological timeline with named versions
Naming Each version gets a descriptive codename (e.g., "The Great Migration")
Content Bullet-point details under each version
Location Learning portal → Building Websites → Changelog
Data source Mined from 43 Copilot CLI sessions + idea vault docs + learning portal history

Versioning Rules

Version Meaning Example
V0.x Pre-Copilot CLI era (legacy platforms) WordPress, Wix, Squarespace
V1.0 First new system built with Copilot CLI Learning portal on MkDocs
V2.0 Major platform change Full website migration to Hugo
V3.0 Major feature addition AI News 3-tier rebuild
V_.1, V_.2 Incremental improvements SEO sprint, performance fixes

✅ What Was Built

A comprehensive changelog page at Building Websites → Changelog in the learning portal, covering:

  • 4 major versions (V0 → V3) with 14 sub-versions
  • Pre-history from WordPress through Squarespace
  • Every significant change since March 26, 2026
  • Data mined from 43 Copilot CLI sessions and all project documentation
  • Mermaid timeline diagram showing the visual evolution
  • Stats summary of the full journey

This idea was conceived and implemented in a single session on April 4, 2026.