How juanpunilibre/laboratorio_4 works
Project type and purpose
• This is a static, single-page website:
• index.html for structure
• styles.css for presentation
• Scripts.js for client-side functionality
• No backend, database, or build pipeline—just a set of files served to browsers.
Main components
a. Client (Web Browser)
b. Web Server / Hosting (e.g., Apache/Nginx, GitHub Pages, Netlify)
c. Static Assets:
• index.html
• styles.css
• Scripts.js
Relationships and data flow
• Browser → HTTP GET → Server/index.html
• index.html includes references to styles.css and Scripts.js
• Browser → HTTP GET → Server/styles.css
• Browser → HTTP GET → Server/Scripts.js
• Browser renders HTML + applies CSS + executes JS
Architectural patterns and design principles
• Separation of concerns: structure (HTML), style (CSS), behavior (JS)
• Cacheable static assets: all files are cacheable via CDN or HTTP headers
• Resource dependency graph: index.html is the entry point that pulls in other assets
Technologies & frameworks
• Core Web Standards: HTML5, CSS3, ES6 JavaScript
• (If used) Any CSS resets, polyfills, or JS libraries—highlight them as separate subcomponents
Essential elements to capture
Example Layout:
[Browser] →(GET /index.html)→ [Web Server / Hosting]
[Web Server] →(200 OK, index.html)→ [Browser]