How danielgarciacha/diseno-y-desarrollo works
Project type and purpose
• This is a monolithic, full‐stack web application.
• The Python script (app.py) acts as the single backend server (likely using Flask or a similar microframework).
• The directories css/, html/, js/, img/ hold the static front‐end assets that the server delivers to the browser.
File structure
• Top‐level:
• app.py – the backend application entry point
• index.html – the main landing page
• css/ – all stylesheet files (Bootstrap + custom)
• html/ – secondary pages served either statically or via routes in app.py
• js/ – front‐end logic (form handling, charting, session management)
• img/ – static images referenced by HTML/CSS
• No separate “templates” folder is present; HTML files may be served directly or via static routing.
README
• The README only contains the project name.
• No further architectural notes are provided, so infer from file layout.
Diagramming the system
a. Main components
1. Client (Web Browser)
2. Web Server (app.py Python process)
3. Static File Store (css/, js/, html/, img/)
b. Relationships & interactions
• Browser → HTTP GET index.html (or other html/*.html)
• Browser → HTTP GET .css, .js, .avif from static file handler in app.py
• Browser → AJAX/Fetch to dynamic endpoints in app.py (e.g., for login, form submission, chart data)
• app.py → (Optional) Database for CRUD operations
c. Architectural patterns
• Monolithic MVC-style:
• Views = HTML files + JS code
• Controller = route handlers in app.py
• Model = data layer inside app.py (or external DB)
• Frontend/Backend separation: static vs. dynamic.
d. Key technologies
• Python (Flask or similar) for backend
• HTML5, CSS3 + Bootstrap for layout/styles
• Vanilla JavaScript for client logic and data visualization (e.g., Graficos.js)
• Static assets served directly by the Python web server