How oviyashree-cj/e-commerce_grocery works
Project type and purpose
• This is a static, front-end only website (“Farmazy – Grocery Store”) built with plain HTML, CSS, JavaScript, and Bootstrap.
• Its purpose is to serve a responsive UI for browsing and “purchasing” grocery items (educational demo).
File structure
• Top-level HTML pages: index.html, about.html, cart.html, contact.html, faq.html, login.html, products.html
• Assets: style.css, script.js, images/ (contains curd.avif)
• No backend code or server-side directories—static site only.
• No build tools, config files, or microservices—simple file/asset organization.
README
• Confirms static, Bootstrap-based responsive design.
• External dependencies: Bootstrap CSS/JS (via CDN), Google Fonts.
• Usage: clone and open index.html in browser.
a. Main components
• User’s Web Browser (client)
• Static Web Server (could be GitHub Pages, Netlify, S3) serving HTML/CSS/JS and images
• External CDNs (Bootstrap, Google Fonts)
b. Relationships & data flow
1. Browser GET → index.html (and subsequent HTML pages) from Static Server
2. Browser GET → style.css and script.js
3. Browser GET → images/curd.avif
4. Browser GET → Bootstrap CSS/JS and Google Fonts from CDN
5. Browser renders HTML + CSS, executes script.js
c. Architectural patterns
• Static-site architecture (no backend)
• Client-driven rendering of UI
• CDN-backed style/script delivery
d. Key technologies
• HTML5 pages
• CSS + Bootstrap 5
• JavaScript (script.js)
• Google Fonts (Poppins)
• Hosting: any static web server