How santimvillarreal/f1-cuyana works
Project type and purpose
• This is a static, frontend-only website (“F1 Cuyana”) built as the final project for a frontend programming course.
• Its purpose is to present Formula 1 information: news, race calendar, regulations, and history to new fans in an easy, practical, and engaging way.
File structure
• Top-level files:
• index.html – the entry point/homepage
• README.md – project description
• Public directory:
• css/styles.css – global stylesheet
• img/… – organized asset directories (calendario, historia, reglamento, contacto)
• pages/… – secondary HTML pages (calendario.html, historia.html, noticias.html, reglamento.html, contacto.html)
• No backend code, APIs, server logic, or database layers—this is purely static content.
README for additional insights
• Confirms it’s a static site for F1 content, aimed at new fans.
• No mention of build tools (webpack, rollup), frameworks (React, Vue), or server-side rendering.
Main components
a. End-user’s Web Browser
b. CDN or Web Server (e.g., GitHub Pages, Netlify, AWS S3 + CloudFront)
c. Static Assets:
• HTML files (index.html, pages/*.html)
• CSS (styles.css)
• Images (Public/img/…)
d. (Optional) DNS / Custom Domain and SSL certificate
e. (Optional) Version Control System (e.g., GitHub) as the source repository
Relationships and interactions
• The user’s browser sends an HTTP(S) request to the DNS-resolved domain.
• The request hits the CDN/Web Server.
• The server returns the requested static HTML page.
• The HTML references CSS (styles.css) and image assets, prompting additional HTTP requests.
• The CDN/Web Server serves those assets back to the browser.
• The browser renders the page and applies styles and images.
Architectural patterns and principles
• Single Page Entry with multiple static page routes.
• Content Delivery Network for performance and global distribution.
• Separation of concerns:
• HTML for structure & content
• CSS for styling
• Image assets for media
• Cache-first strategy (set appropriate cache headers on the CDN).
Relevant technologies
• HTML5, CSS3
• Static hosting (GitHub Pages / Netlify / AWS S3 + CloudFront)
• Optional DNS (Route 53, Cloudflare) & SSL/TLS
• Version control (Git)