How imtahiriqbal/web-app-tasks works
Project type and purpose
• This is a small‐to‐medium‐scale full-stack e-commerce web application built with Python/Flask (monolith) serving a “Perfume” storefront.
• It offers user-facing pages (home, products, cart, signup/login, checkout) plus an admin dashboard.
File structure
• Top level:
• app.py – single entry point, Flask application definition, URL routes, controllers.
• static/ – CSS, JS, images served as static assets.
• templates/ – Jinja2 HTML templates: base layouts, pages (home.html, products.html, cart.html, dashboard.html, login/signup, success).
• No subfolders for “backend” or “services” → code is a single service (monolith).
• No obvious Dockerfile, CI/CD configs, or cloud infra files—focus is on core web app.
README
• Minimal contents (“# web-app-tasks”) → no extra architectural guidance.
• We infer a basic single-tenant Flask app with (likely) a relational database and optional external integrations (e.g. payment gateway).