How fabagaipo/webmart works
Project type and purpose
• WebMart is a full-stack e-commerce web application.
• The frontend/ directory holds a React/Vite single-page app (SPA) with Context-based state management and a thin API wrapper.
• The webmart_api/ directory is a Django back end exposing HTTP/GraphQL endpoints, organized into per-domain “apps” (category, product, store, order, user_profile).
File structure
• Top-level directories:
• frontend/ (React code, assets, components, contexts, API wrapper)
• webmart_api/ (Django project, apps, settings, ASGI/WSGI entrypoints)
• React uses App.jsx, various UI components under src/components, Context providers under src/context, and a client library under src/webmart-api/webmartAPI.js.
• Django side uses the traditional project structure (manage.py, settings, URLs) plus subfolders for each domain. Each domain has models/, migrations/, api/ (endpoint handlers), and schema/ (GraphQL or validation schemas).
• No separate microservices—Django is a monolith, but logically broken into modular apps.
README for additional insights
• Confirms local setup: Python 3.12, Django dev server, React dev server via npm run dev.
• No external dependencies (e.g. message brokers or cache layers) are explicitly listed; assume a single relational DB (e.g. PostgreSQL).
Don’t overthink—capture every logical component
• Break the Django monolith into its five domain apps rather than lumping them all together.
• React Context providers and the custom API client as separate pieces of the frontend.