How angular-vietnam/100-days-of-angular works
This project is not a traditional full-stack application or service but rather an educational content repository that organizes 100 days of Angular tutorials. The repository holds a series of markdown files (one per day/tutorial) that walk through various Angular concepts. In addition, there are folders for assets (such as video files for each lesson), translations (supporting multiple languages), and configuration files (like GitHub settings and licensing). The README further reinforces that this is an instructional series on Angular, complete with links to related projects and sponsorship information.
Main Components
• Tutorial Content Module – Representing each markdown file (Day001-Installation.md, Day002-AngularApp.md, etc.) which makes up the core educational lessons.
• Assets/Media Module – This holds multi-media materials (like videos in the assets folder) that support or complement the markdown tutorials.
• Metadata & Configuration Module – This includes ancillary but essential elements such as the README, LICENSE file, and .github configurations.
• External References and Links – Include links that point outside (like YouTube playlists, external sponsor links, and references to sample Angular projects). While these aren’t “internal” components, they form part of the overall ecosystem or ecosystem boundaries that the content refers to (for example, linking to the Spotify or Jira Clone projects).
Relationships and Interactions
• The Tutorial Content Module is the central “body” of the repository, driving the educational narrative.
• A connection from the Content Module to the Localization Module shows that each core lesson may have alternative language versions. This underscores the separation between the “original” content and its translations.
• The Metadata & Configuration Module sits on the periphery but ensures project governance, styling (such as sponsor information), and community interactions.
• External links can be included as part of a boundary component that interacts with the Content Module, showing relationships such as “view on YouTube” or “sponsor link.”
Architectural Patterns and Design Principles
• Separation of Concerns – Each folder represents a different concern: content delivery (markdown files), supporting assets (assets folder), internationalization (translations), and project metadata/configuration.
• Modularity – The structure of having day-by-day markdown files, along with independent assets and translations, is modular and allows for easy update or replacement of individual components.
Relevant Technologies
• Mention that some of the content references or even leverages external Angular projects (such as examples built with Nx, ng-zorro, TailwindCSS, or Akita) to ground the learning in practical examples.
• Every component should be explicitly labeled.
• Related files together (for example, gather all DayXX files under one “Tutorial Module” and show a separate area for assets and translations).