How toti-br/aulas_2020-2 works
Main Components
• Repository Root: Label it “aulas_2020-2 – Materiais de Aula.”
• Module Directories: Show major branches for each technology or topic. For example:
– Angular (contains multiple Angular lessons and projects)
– HTML (contains static examples, multimedia, etc.)
– CSS (if present)
– JavaScript (or Lógica de Programação, containing various JS examples)
• At the top, put the overall repository. From there, branch out to each major module (Angular, HTML, Lógica de Programação, etc.).
• Within the Angular branch:
• For each Angular project, illustrate typical components:
▪ “src/app” (containing components, modules, and sometimes routing and services)
▪ “src/assets” (static assets)
▪ Configuration files (angular.json, package.json, tsconfig.json, etc.)
• Communication or data flows between components (for instance, services providing data to components, routing directing view changes, etc.).
• For HTML and programming logic lessons:
• That each of these directories comprises examples organized by lesson number (e.g., HTML/aula_3 with PDFs, HTML/aula_4 demo examples).
• That these examples are standalone static pages or JavaScript files that demonstrate specific topics (e.g., conditional expressions, interactivity).
Relationships and Data Flow
• That assets (images, styles, etc.) and environment configuration files feed into the runtime behavior of the projects.
Architectural Patterns and Technologies
• Mention the use of Angular CLI for Angular projects. Note that each Angular sample naturally follows an MVC-like (Component-Based) pattern – components handle views while services do data processing or state management.
• Common configuration files (angular.json, tsconfig.json, package.json) that indicate build and development processes.
• For HTML examples, note that the files are static examples, sometimes incorporating multimedia (images, audio, or video) as found in the HTML folders.
Detail Level
• Do not shy away from including as many components as possible. The goal is to capture the full scope of an educational repository where each lesson folder represents a mini-project.