How wahidsaidmaroc/devopssitewebhtml works
Project type and purpose
• This is a simple static HTML website (“DevOps SiteWeb HTML Simple”) consisting of a handful of HTML pages and a GitHub Actions workflow for CI/CD to Azure Static Web Apps.
• No backend services or databases live in this codebase—its sole function is to publish and host static content.
File structure
• Top-level HTML files: index.html, contact.html, mesprojets.html, MyEvent.html → these are the pages the site serves.
• .github/workflows/azure-static-web-apps-…yml → GitHub Actions pipeline definition for building/deploying to Azure Static Web Apps.
• README.md → project description: a simple DevOps workflow for a static site.
README for additional insights
• Confirms it’s a “DevOps SiteWeb HTML Simple” project.
• No mention of databases, APIs, or build processes beyond the static-site CI/CD.
a. Main components
• Developer workstation / Git client
• GitHub repository (with code + workflow YAML)
• GitHub Actions runner (CI/CD)
• Azure Static Web Apps service (hosting + global CDN)
• End users’ browsers
• (Optional) Custom domain / DNS layer
b. Relationships and interactions
1. Developer pushes commits to GitHub
2. GitHub Actions workflow is triggered
3. Runner packages static files and calls Azure Static Web Apps deployment API
4. Azure hosts files behind a CDN edge network
5. End users request pages; served from nearest CDN edge
c. Architectural patterns and design principles
• GitOps: infrastructure and deploy logic live in Git repo
• CI/CD pipeline: automated build → test (none here) → deploy
• CDN-backed static hosting: high availability, low latency, zero-backend overhead
d. Key technologies/frameworks
• HTML/CSS (static files)
• GitHub Actions (pipeline orchestration)
• Azure Static Web Apps (hosting + CDN)
• YAML (workflow configuration)