How I created my brand using Static Web Apps with Blazor and Azure Functions
summary
Bought three domains and builds a personal blog as a small CMS using Azure Static Web Apps with Blazor + Azure Functions and Cosmos DB; posts stored as JSON but edited in Markdown via an authenticated web UI. Uses built-in auth providers (Twitter, GitHub, AAD, Google preview) and reads the client principal to enforce role-based access control (25 users). Runs in the free tier, works live, and upgrades to custom auth (Auth0) without changing app code.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:43Brand origin story
- 1:49Choosing domains
- 2:52Static Web Apps discovery
- 3:34Blazor and Cosmos DB
- 4:38Adding authentication
- 6:48Role-based access control
- 8:14Managing roles in Azure SWA
- 8:56Custom auth and scalability
- 9:37Why Static Web Apps
- 10:17Closing remarks
related talks
59mAzure Static Web Apps - From Zero to Deployed App In 60 Minutes
26mMastering Azure Statis Web Apps code, config, deploy
36mAzure Static Web Apps
24mStatic (?!?#🙀) Web Apps
45mDeploying your Static Web App with Your Favorite Framework in Minutes
30mBuild Faster, Better Apps with SSG, Headless CMS & Azure Static Web Apps
45mDeploy Your Static Web App with Your Favorite Web Framework
31mFrom Code to Scale! Build a Static Web App in Minutes
