How euandr/projetosweb-html- works
Project type and purpose
• This is a collection of static web–learning projects (HTML, CSS, minimal JavaScript) organized in folders. There’s no backend or database—each folder under “Aprendendo-Básico” and the “projeto-Einstein” directory contains standalone HTML/CSS exercises.
File structure
• Top level:
• “Aprendendo-Básico/” – multiple subfolders (“seção1_intro-html”, “seção2_intro-css”) each holding static HTML/CSS files for tutorials and challenges.
• “projeto-Einstein/” – a simple site with index.html and a CSS file.
• README.md – describes the repo as a collection of web-learning projects.
• No server-side code, build scripts, or configuration files—pure static assets.
Key insights from README
• HTML, CSS, and JavaScript fundamentals.
• No mention of bundlers, frameworks, or deployment pipelines—suggests manual hosting or GitHub Pages.
a. Developer environment (local filesystem + editor)
b. Version control (GitHub repository)
c. Static asset folders (“Aprendendo-Básico”, “projeto-Einstein”)
d. Static file host (e.g., GitHub Pages or simple web server)
e. end-user browser
Relationships and data flow
• Developer edits files → commits to Git → push to GitHub → hosted as static site → client browser fetches HTML/CSS/JS → renders pages.
• Optionally, local dev server can serve files during development.
Architectural patterns & principles
• Static-site architecture (no runtime backend).
• Content organized by modules (each tutorial in its own folder).
• Separation of concerns: HTML for structure, CSS for styling, JS for behavior.
Technologies & libraries
• HTML5
• CSS3
• (Optional) JavaScript for interactivity
• Git/GitHub for versioning & hosting
• (Optional) Live-reload dev server
Detail guidance
• “projeto-Einstein” as a separate static site component.
• That there is no database or API—only static file serving.