How shaikarsalan347/omnifood works
Project type and purpose
• From the file tree and README link, this is a purely front-end, static “Omnifood” landing/site project. It delivers HTML, CSS, JS, images and a Markdown content file to the user’s browser. There is no backend/service code in this repo.
File structure
• index.html: the single entry point
• css/ (general.css, queries.css, style.css): styling, responsive rules
• js/script.js: client-side behavior, possibly fetches content.md
• content.md: raw/structured content pulled into the page
• img/: assets folder (app, customers, gallery, logos, meals)
This indicates a simple client-rendered architecture—static assets served to the browser, where JavaScript may dynamically inject content.
README for additional insights
• Only contains a link to the deployed site on Vercel.
• Implies the project is deployed as a static site on a CDN.
Detailing is key
• That CSS influences rendering and JS influences dynamic behavior.
• Deployment environment (Vercel/CDN) to illustrate where assets live.