How alanmvar/ceti-webpage works
Project type and purpose
• From the file tree and README, this is a purely static, front-end only website for the CETI Colomos school. It consists of HTML pages, CSS stylesheets, and an images folder. There is no backend, database, or runtime logic beyond the browser rendering static assets.
File structure
• Top-level files:
• .vscode (editor settings)
• README.md (project description)
• Multiple HTML pages (aspirantes.html, calendario.html, etc.)
• CSS files (styles.css, estilotabla.css)
• imgs/ (static images)
• No “src” or “backend” directories—this confirms a client-only architecture.
• No build scripts, no server config files—assets are served as-is.
README for additional insights
• It’s an academic project originally created in 2024 and later hosted on GitHub Pages (or similar) in 2025.
• No special dependencies or frameworks mentioned—likely plain HTML/CSS.
a. Main components
• Developer workstation (local files + Git commit)
• Version control (GitHub repo)
• Static hosting platform (e.g., GitHub Pages, Netlify, S3+CloudFront)
• End users’ web browsers
• Static assets: HTML pages, CSS stylesheets, image directory
b. Relationships and interactions
1. Developer edits files in VSCode → commits/pushes to GitHub.
2. Hosting platform pulls from GitHub → deploys static assets.
3. End user browser issues HTTP GET → hosting platform/CDN serves HTML, CSS, images.
4. Browser parses HTML → CSS & images are fetched → page renders.
c. Architectural patterns/design principles
– Static site architecture (client-server, CDN acceleration).
– Separation of concerns: HTML for structure, CSS for presentation, img folder for media.
d. Relevant technologies
– Git/GitHub for version control & CI/CD trigger.
– GitHub Pages (or Netlify/S3) as static host + CDN
– Standard web stack: HTML5, CSS3