How robertocolman/trabajo-final-integrador-grupo-63 works
Project type and purpose
• From the file tree and README, this is a static full‐frontend website for “Clínica IDW S.A.”. There is no separate backend service or database—everything is HTML, CSS, JS, images, and a small config folder for initial data (medicosInicial.js and DommyUsers.json).
File structure
• Top‐level HTML pages: index.html, login.html, medicos.html, reserva.html, contacto.html, plus several “alta…” and “admin_…” pages for CRUD‐style admin UIs.
• Static assets:
• /css/style.css
• /img (all images)
• /js/*.js (page‐specific scripts, navigation, data loading, form handlers)
• Config folder holds JSON/JS files used by client‐side scripts to seed or manage data.
• There are no server-script or API directories, so the site is likely hosted on a basic static file server (e.g., Apache, Nginx, GitHub Pages).
Key insights from the README
• Target audience: clinic staff and patients.
• Sections: “Quiénes somos”, “Misión y Visión”, “Médicos especialistas”, “Contacto”, plus admin screens for managing users, reservas, médicos, etc.
• Tech stack: HTML5, CSS3 (Bootstrap 5), vanilla JavaScript.
Main components and their interactions
a. Frontend (Browser)
• HTML pages rendered by the browser.
• CSS + Bootstrap for styling.
• JS modules handle navigation, form submission, data loading/manipulation.
b. Static File Server
• Serves HTML, CSS, JS, images, and config JSON.
c. Data store (static JSON/JS config)
• DommyUsers.json – mock user data.
• config/medicosInicial.js – initial doctor listings.
d. No external services (all logic is client‐side).
Interaction flow:
1. User opens a page in the browser → browser issues HTTP GET to the static server.
2. Server returns HTML + CSS + JS.
3. JS code fetches or imports config JSON/JS to populate tables/forms.
4. User actions (login, reserva, alta…) are handled entirely on the client—no API calls to a backend.
Architectural patterns and design principles
• Client‐side MVC/MVVM flavor: each JS file corresponds to a “view” (page) and manipulates the DOM.
• Separation of concerns: static assets are organized by type (css, js, img).
• Config/Data injection via static JSON/JS instead of a database.