How undo-happy/webhost_versatify works
Project type and purpose
• This is a front-end–only Azure Static Web App project.
• The file tree shows only HTML, CSS, and JS under a “frontend” folder and a GitHub Actions workflow that deploys to Azure Static Web Apps.
• There is no custom back-end code in this repo (no server or function code beside an empty host.json).
File structure
• Top level
• .github/workflows/azure-static-web-apps-…yml – CI/CD pipeline for deploying the site
• README.md – project overview (currently minimal)
• host.json – Azure Functions host configuration (present but no function code in this repo)
• frontend/
• index.html, admin.html – entry points for the public and admin UI
• app.js, admin.js – application scripts
• style.css, admin.css – application styles
README
• The README currently just contains a placeholder greeting.
• We infer from the workflow filename and host.json that the intended deployment target is Azure Static Web Apps.
a. Main components
• End User’s Browser (loads HTML/CSS/JS)
• Azure Static Web Apps Service (CDN + static-file hosting)
• GitHub Actions CI/CD (workflow that builds and pushes to Azure)
• (Optional future) Azure Functions or external APIs
b. Relationships and interactions
• Browser ←→ Azure Static Web Apps (serves assets via CDN)
• GitHub Actions → Azure Static Web Apps (pushes artifacts on commit)
• Browser → Azure Functions / External API endpoints (if implemented later)
c. Architectural patterns and principles
• Static-site hosting with CDN for global performance
• GitOps / CI-driven deployments using GitHub Actions
• All UI logic is client-side JavaScript; no dedicated server code in this repo
d. Relevant technologies
• Azure Static Web Apps
• GitHub Actions for CI/CD
• HTML, CSS, JavaScript (vanilla)
Summary
• Break the project into: User, CDN host, CI/CD, and optional API.
• Data flow (asset requests, deployments, API calls).
• Technologies and file-structure hints (e.g., host.json → Azure Functions).