How yashodeep-rajput/zomato-landing-page works
Project type and purpose
• This is a purely front-end, static landing-page clone of Zomato.
• It comprises only HTML, CSS, and image assets—no backend code or dynamic functionality.
File structure
• index.html: the entry point and page markup.
• styles.css: all styling rules.
• README.md: brief description, confirms this is a single-page, client-side project.
Key insights from the README
• Confirms “Zomato landing page clone” and that this is an initial commit—no scripts, no build system, no external dependencies.
Main components
a. Client Browser (end user)
b. Hosting / CDN (static file server or S3 bucket + CloudFront, or GitHub Pages)
c. Static Assets:
• index.html
• styles.css
d. (Optional) Local Development Environment (your machine + code editor)
Relationships and interactions
• Browser issues an HTTP GET → Hosting/CDN for index.html
• index.html references styles.css and image URLs → Browser issues HTTP GETs for those.
• Browser renders the page by combining HTML, CSS, and images.
Architectural patterns & design principles
• Simple Client-Server static architecture.
• Asset caching via CDN for performance.
• Single Responsibility: HTML for structure, CSS for styling, images for media.
Relevant technologies
• HTML5, CSS3
• Static file hosting platforms (e.g., AWS S3 + CloudFront, Netlify, GitHub Pages)
• Optional: Local dev server (e.g., Live Server VSCode extension)
1. Sketch the user’s browser on the left.
2. Sketch the hosting/CDN node on the right.
3. Below or beside the CDN node, list the static assets grouped by type.
Detail without over-splitting
• You do not need to introduce unnecessary microservices or modules.
• Every asset category and each distinct flow (HTML vs CSS vs images).
• Deployment/hosting only if it matters for operations or performance.