How gauravburjwal/omnifood works
Project type and purpose
• From the file tree and README, this is a purely front-end, static landing page (“Omnifood”) for a SaaS application, implemented with HTML, CSS, and vanilla JavaScript. There is no custom backend code; content is delivered as static assets.
File structure
• Top-level files:
• index.html – the single entry point
• manifest.webmanifest – PWA manifest file
• content.md – project content (documentation)
• README.md – project description
• .gitignore – VCS ignore rules
• Static-asset directories:
• css/ – style sheets (style.css plus responsive queries.css)
• js/ – client scripts (script.js)
• img/ – logo, gallery, meals, customers, app screenshots
• No server or API code, no database directories.
README for additional insights
• It confirms this is a landing page only, no dynamic server components are mentioned.
• There is a screenshot but no architectural guidance.
Details
• Parallel fetching of assets
• If there is a service worker script, illustrate the intercept → cache strategy
• Manifest as a separate asset that allows installation
• Call out responsive CSS (queries.css) as the mechanism for multi-device support