How isabellimrqs/marquesaesthetic works
Project Type and Purpose
• This is a front-end‐only, static e-commerce website ("MarquesAesthetic") built with plain HTML, CSS, and JavaScript.
• It serves as a semester integrator project demonstrating product listings (jewels, accessories, presents, etc.), a shopping cart, user account page, and admin interface mockup.
File‐Structure Analysis
• Top-level HTML pages: account.html, adm.html, cart.html, various category pages (feminine.html, masculine.html, etc.), and produto1.html for product detail.
• “js/” directory: individual page controllers (about.js, feminine.js, products.js, etc.) plus shared modules (funcoes.js, carrinho.js, slider.js).
• “styles/”: CSS styling (account.css, style.css).
• “image/”: static assets (product and UI images).
• “node_modules/”: development dependencies (likely for build tooling, bundlers, polyfills).
Key Insights from README
• No backend code present—this is purely client-side.
• Intended user flows: browse categories → view product → add to cart → view cart → (mock) checkout.
• Admin page likely simulates management features (e.g., order review).
Diagramming the Architecture
a. Main Components
• Browser (Client)
• Static Web Server (or CDN)
• HTML Pages (Routes)
• CSS Stylesheet(s)
• JavaScript Modules:
– Page Controllers (one per HTML page)
– Shared Utility Modules (cart management, DOM helpers, slider)
• Static Assets (images, fonts)
• (Optional) External Services—e.g., Payment Gateway API stub or Analytics
b. Relationships & Interactions
• Browser requests an HTML page from the Web Server.
• HTML page imports CSS and JS bundles.
• JS controller for that page loads:
– Reads product data (hard-coded or JSON in js/products.js).
– Implements UI interactions (slider, add‐to‐cart).
– Interacts with localStorage or in-memory “cart” module.
• User actions trigger updates to the cart module, which updates the DOM.
• When “Checkout” is clicked, the cart controller may call an external payment API stub.
c. Architectural Patterns & Principles
• Single‐Page‐Enhancement: Each HTML page has its own controller instead of a full SPA.
• Modular JavaScript: Separation between page-specific logic and shared utilities.
• Static Asset Layering: Images, CSS, and JS served separately for cache and CDN optimization.
d. Technologies & Frameworks
• Vanilla JavaScript (ES6 modules if used)
• CSS (no preprocessor)
• Static server (could be GitHub Pages, Nginx)
• Node tooling (bundler or local dev server, implied by node_modules)