Today I reached Stage 4 of the Cloud Resume Challenge — getting my resume website hosted on Azure Blob Storage as a static site. This is the stage where all the work from earlier (HTML, CSS, responsive design, and content integration) finally comes alive on the internet.
🎯 Goal
The main goal of this stage was to:
- Upload my HTML/CSS resume website to Azure Storage.
- Enable static website hosting.
- Make sure my page can be accessed over the internet using the Azure-provided endpoint.
This is the first real step where my resume left my local machine and became available online.
✅ What I Did
- Created a Storage Account in Azure
- Storage name:
myresumejic - Region: West Europe (you can choose nearest region incase you get an error just change location).
- Performance: Standard, Redundancy: LRS.
- Enabled Static Website Hosting
- In the Azure Portal, click on Data Management then click on Static Website under my storage account.
- Enabled the feature.
- Set
index.htmlas the main document and404.htmlas the error document.
- Uploaded My Files
- Uploaded
index.html,style.css, and404.htmlinto the$webcontainer.
📸 Screenshot: $web container showing index.html, style.css, and 404.html
- Tested the Endpoint
- Azure generated a public URL: 👉 https://myresumejic.z19.web.core.windows.net/
* When I visited it in the browser, I saw my resume live for the first time! 🎉
How I Achieved It
- Followed the official Microsoft docs on Static Website Hosting in Azure Storage.
- Used the Azure Portal upload for simplicity (later I’ll automate with Azure CLI / GitHub Actions).
- Ensured consistent naming since Azure is case-sensitive.
⚡ Challenges & Solutions
- Case Sensitivity
-
Problem: CSS didn’t load at first because of mismatched file names (
Style.cssvsstyle.css). - Solution: Renamed everything consistently to lowercase.
- Browser Caching
- Problem: After re-uploading, my browser showed old content.
- Solution: Cleared cache. Later, Azure CDN (Stage 5) will solve this properly.
- File Paths
- Problem: At first, index.html didn’t find my CSS.
-
Solution: Used relative paths (
href="style.css") since Azure serves files directly.
📌 Next Steps
- Stage 5 → Add HTTPS support with Azure CDN.
- Configure a custom domain.
- Start building the Azure Function (Python) for the visitor counter.
🌟 Reflection
This stage was exciting because it’s the first time my resume was truly online on Azure. For now, it’s basic (no HTTPS, no custom domain), but it’s a major milestone. From here, I’ll improve the site with security, custom branding, and a dynamic backend.
Top comments (0)