How ichi075/zapchef works
Project type and purpose
• ZapChef is a purely static, front-end web application. It consists of a single HTML file (index.html), static assets (images, CSS, JS if any), and is deployed via GitHub Pages. There is no backend, database, or dynamic API layer.
Main components
a. User’s Web Browser (Client)
b. GitHub Pages Hosting (Static File Server / CDN)
c. GitHub Repository (Source of truth / Deployment repository)
d. Optional: Local Development Environment (Developer machine)
Relationships and data flow
• The User’s Browser issues an HTTPS GET request for index.html (and any linked CSS, JS, or image files) to the GitHub Pages CDN.
• GitHub Pages serves the static assets directly from the repository.
• (Optional) Developer pushes commits to the GitHub repo → GitHub Pages automatically builds and publishes the updated static files.
Architectural patterns and design principles
• JAMstack-style static site: pre-built markup served over CDN, no server-side rendering at runtime.
• Separation of concerns: repository stores source (HTML + assets), hosting layer only serves static content, client handles all UI logic.
Technologies, frameworks, and libraries
• HTML5 (index.html)
• CSS and/or JS if included in index.html
• GitHub Pages for static hosting (backed by a CDN)
• Git for source control and automated deployment