How henriquecatani/weblab works
Project type and purpose
• This is a static “Web Lab” course repository containing collections of HTML pages and supporting notes.
• There is no dynamic backend or database—just static assets for teaching web fundamentals.
File structure
• Top-level files/folders:
• index.html (main landing page)
• Notas/ (author’s personal notes, not served)
• aula-20-03-25/ (sample site pages: contato.html, index.html, sobre.html, receita.html, site1/)
• mecanico/ (mecanico.html demo)
• questionario/ (index.html form example)
• weblab/ (empty placeholder)
• No build scripts, configuration files, or server-side code present.
README
• Title “weblab” with a single line: “Arquivos das aulas de Web Lab” confirming it’s a teaching repository of static HTML exercises.
Main components
a. Client (Web Browser)
b. Static Web Server or CDN (e.g., Nginx, GitHub Pages, Netlify)
c. File Storage / Git Repository
d. (Optional) Author Workstation with local clone and editors for Notas/ and HTML pages
Relationships and data flow
• Browser → HTTP request → Web Server/CDN
• Web Server/CDN → serves static HTML/CSS/JS from File Storage
• Author Workstation → commits/pushes → Git Repository → triggers CI/CD → deploys to Web Server/CDN
Architectural patterns and principles
• Static Site Hosting (no server-side logic)
• “Jamstack”-style separation: content is prebuilt or served as static assets
• Version-controlled source in Git; optionally automated deploys
Key technologies/frameworks/libraries
• HTML5 (pages under root, aula-20-03-25/, mecanico/, questionario/)
• CSS/JS (if present inline or external)
• Git for source control
• Static hosting platforms (GitHub Pages, Netlify, S3+CloudFront, etc.)
Diagramming recommendations
• Use clear labels: “Browser,” “Static Web Server/CDN,” “Git Repo,” “Author Workstation”
• Between Browser and Web Server (HTTP/HTTPS)
• Between Workstation → Repo → CI/CD → Server
• Blue rectangles for runtime components (Browser, CDN)
• Grey parallelogram for Author Workstation