Aspire

Migrating from Microsoft Learn to aspire.dev

Productivity exemplified: How I planned, prompted, and tamed AI to migrate aspire.dev.

David Pine

8 minute read

...

When my team (the Aspire team) decided to migrate all Aspire content from Microsoft Learn to the shiny new aspire.dev site, we knew we’d signed up for a marathon. You may have noticed banners atop both Microsoft Learn: Aspire and aspire.dev announcing the migration…

Microsoft Learn: Aspire

Banner on Microsoft Learn announcing the migration of .NET Aspire documentation to aspire.dev, featuring yellow and blue gradient background with informational text about the transition

Deploying aspire.dev with aspire deploy

A journey of rebranding, replatforming, dogfooding, and mild existential crises

David Pine

7 minute read

...

In this post, I’ll walk you through the journey of how https://aspire.dev came to be—from the initial spark of rebranding to the technical challenges of deploying it with our own tools. It’s a story of design iterations, platform decisions, and the kind of dogfooding that makes you question your life choices… Spoiler: we made it work, and learned a lot along the way.

🕓 A bit of history

The first commit of dotnet/docs-aspire was November 10, 2023, but we were building out content for this well before then. Spawning itself into existence from an evolving extensions ecosystem (code named “R9”), Astra was the original name, before later becoming Aspire! The name still isn’t something I like, it’s too ambiguous, but it’s what we have now.