How jmgalvis12/proyecto_alkosto works
Project type and purpose
• This is a full-stack e-commerce web application.
• Backend: a Django “modular monolith” with separate apps for accounts, products, cart, orders, and analytics.
• Frontend: a React single-page application (bootstrapped with Create React App), plus supporting JS MVC code under src/ for controllers, models, and views.
File structure
• Top level
• .gitignore, README.md – repo metadata
• backend/ – Django project root (manage.py, requirements.txt)
• frontend/ – React CRA scaffold (src/, public/, package.json)
• public/ & root src/ – additional static+MVC assets (likely part of a legacy or alternative frontend)
• backend/config/ – Django settings, URL routing, ASGI/WSGI entry points
• backend/apps/… – five domain apps, each with models, views, migrations, admin & tests
• frontend/src/ – React components (views), API helper (api.js), CSS, HTML shell
• Root src/controllers, src/models, src/views – lightweight JS MVC layer interacting with src/data/categories.json
README for additional insights
• The README is the standard Create React App boilerplate, confirming that the React SPA is the intended production UI.
• Deployment and build scripts are managed by npm; the backend likely runs separately on Django’s runserver or deployed via WSGI/ASGI.