How hannahcrowell/proyecto_integrador_primer_departamental works
Project type and purpose
• This is a “Proyecto Integrador” that aggregates multiple small front-end/mini back-end web apps (games like the Chrome Dino clone, memorama, landing page, weather app, etc.).
• Each mini-project lives in its own directory, contains HTML/CSS/JS, and some include a simple server.js (Node/Express) to serve static files or provide minimal API endpoints.
File structure
• Top-level directories:
• CSS (global styles?)
• Juego_Dino, Juego_html, Juego_memorama, Practica, Practica3_…, Practica5_…, PrimeraPractica, SegundaPractica – each a standalone mini-app
• Common patterns:
• index.html or <Name>.html + script.js + style.css
• Some include server.js and a node_modules folder → lightweight Express servers
• No centralized database; external public APIs used (e.g., weather/geolocation)
README
• Very concise: “Proyecto Integrador” that collects all first-term practices and the Dino-style game.
• No deeper architectural notes given.
a. Main components
• User’s Browser
• Static Asset Hosts (Nginx/Apache or Express servers per mini-app)
• Node.js/Express server instances (for apps with server.js)
• External Third-Party APIs (Weather API, Geolocation API)
b. Relationships & interactions
• Browser ↔ Static Server: serves HTML/CSS/JS for pure front-end apps
• Browser ↔ Node.js/Express: serves static files + minimal dynamic routes (e.g., API proxy)
• Node.js/Express ↔ External API: fetch weather/geolocation data on behalf of client
c. Architectural patterns & principles
• Micro-frontend style: each practice is a self-contained module
• Separation of concerns: UI assets vs. back-end servers
• Reuse of common static-serving pattern (Express)
d. Key technologies
• HTML5, CSS3, vanilla JavaScript
• Node.js, Express (in server.js)
• External REST APIs (e.g., OpenWeatherMap, Geolocation)
Detailed steps for the engineer
1. A “User Browser” node at the left.
a. Static Hosting: list all pure-frontend practices (e.g., Juego_html, PrimeraPractica, SegundaPractica, etc.).
b. Dynamic Hosting: list practices with server.js (Practica, Juego_memorama, Practica3_…, Practica5_…).
6. Callouts for shared assets (e.g., CSS, Multimedia folders).