How ignaci0vidal/pp3-frontend-alternativo works
This is a static ecommerce frontend: users browse and filter products, manage a cart, submit orders, and access account and order functions. The single core file, app.js, contains both UI workflows and a shared API client that sends requests to the configured Gateway. The graph separates those responsibilities while keeping their shared implementation path. Evidence is limited to the README and excerpts of app.js; unsampled interactions, including payment and receipt flows, are not asserted.
Main entry points: app.js Gateway client
Components 10
Storefront
- Product catalog
app.js - Product rendering
app.js
Account
- Account access
app.js - Profile
app.js
Commerce
- Shopping cart
app.js - Checkout
app.js - Order management
app.js
Other components
- Shopper
- Gateway client
app.js - API Gateway
Connections 13
- Shopper → Product catalog: browses
README.md - Shopper → Account access: signs in
app.js - Shopper → Shopping cart: manages
app.js - Shopper → Checkout: submits
app.js - Shopper → Order management: views
app.js - Product catalog → Gateway client: requests products
app.js - Product catalog → Product rendering: renders results
app.js - Account access → Gateway client: sends credentials
app.js - Profile → Gateway client: requests session
app.js - Shopping cart → Gateway client: loads and saves
app.js - Checkout → Gateway client: creates or checks order
app.js - Order management → Gateway client: loads and updates
app.js - Gateway client → API Gateway: sends HTTP requests
app.js