How codewithsadee/grilli works
Project Type and Purpose
• This is a static, single‐page restaurant website (“Grilli”) built purely with HTML, CSS, and JavaScript and deployed (e.g., via GitHub Pages).
• There is no backend application or database—just client‐side code and assets.
Key Architectural Components
a. Client (Web Browser)
b. CDN or Static Web Server (e.g., GitHub Pages)
c. Static Assets:
• HTML (index.html)
• CSS (assets/css/style.css, style-guide.md)
• JavaScript (assets/js/script.js)
• Images (assets/images/*, readme-images/*)
Relationships and Data Flow
• User’s browser sends an HTTP GET to the Static Web Server for index.html.
• The server responds with index.html, which references CSS and JS assets.
• The browser then fetches style.css and script.js (and any images), processes them, and renders the page.
Architectural Patterns and Design Principles
• Client‐Side Rendering: All layout and interactivity occur in the browser.
• Separation of Concerns:
• HTML for structure (index.html)
• CSS for styling (assets/css/style.css)
• JS for behavior (assets/js/script.js)
• Responsive Design: Style guide ensures mobile-first, fluid layouts.