How gustavoguanabara/html-css works
Project type and purpose
• This is a static educational website (HTML5/CSS3 course materials).
• Purpose: host PDFs, code samples (HTML/CSS exercises), and challenges for learners.
• Hosted via GitHub Pages, no dynamic backend.
File structure
• Top‐level:
• _config.yml indicates a Jekyll/GitHub Pages build.
• aulas-pdf: PDFs of lectures.
• exercicios: folders of HTML/CSS exercises.
• desafios: PDF challenges and supporting files.
• imagens: site images (e.g., mascote.png).
• README.md describes site content and links.
• .gitignore, LICENSE—standard repo files.
Extract insights from README
• Static site with direct links to PDFs and live HTML demos.
• Uses GitHub Pages URL structure (gustavoguanabara.github.io/html-css).
Main components
a. Content authoring environment
– Developer’s local machine (editor, Git CLI).
b. Source code repository
– GitHub repo (branches, commits).
c. Build pipeline
– Jekyll (reads _config.yml, converts any markdown to HTML).
d. Hosting platform
– GitHub Pages (serves static assets over HTTPS/CDN).
e. End user
– Learner’s web browser (requests HTML/CSS/PDF files).
Relationships and data flow
• Author edits files → commits to Git → push to GitHub.
• GitHub triggers Pages build via Jekyll → outputs static site.
• GitHub Pages CDN serves content → browser requests/receives assets.
• Browser renders HTML/CSS; PDFs open via built‐in viewer or download.
Architectural patterns/design principles
• Static site generator (Jekyll) pattern.
• Content‐pipeline separation: raw assets (PDFs), templates, final output.
• Infrastructure as code: configuration (_config.yml) controls build.
Technologies/frameworks/libraries
• Git/GitHub for version control and hosting.
• Jekyll (built into GitHub Pages) for static site generation.
• HTML5/CSS3 for front‐end.
• PDF assets as binary resources.