How marcos934/portfolio-marcos-vinicius-mulinari works
Project Type and Purpose
• This is a single-page application (SPA) portfolio built entirely in Angular 18.
• It’s a purely front-end, static site (deployed via GitHub Pages or any static host) showcasing work experience, skills and multi-language support (PT/EN).
High-Level Architecture Components
a. User Browser (Client)
• Hosts the Angular SPA.
b. Static Web Server / CDN
• Serves the compiled Angular assets (index.html, JS bundles, CSS, assets).
c. Angular Runtime & Modules
– AppModule (bootstrap)
– AppComponent (root)
– RouterModule (defined in app.routes.ts)
d. Presentation Layer (Components & Templates)
– LanguageSelectorComponent
– LatestUpdatesComponent (+ its service & interface)
– ProjectsComponent (+ its service & interface)
e. Business-Logic Layer (Services & Pipes)
– TranslationService & DataTranslationService (i18n logic reading XLF files)
– LatestUpdatesService (e.g., fetches release data from GitHub API)
– ProjectsService (fetches projects data, possibly from local JSON or API)
– TranslatePipe (transforms keys into localized strings)
f. Data Layer (Static Assets & External Services)
– src/locale/messages.xlf (translation catalogs)
– public/assets/images, CSS assets, Tailwind styles
– External API endpoints (e.g., GitHub REST API)
Relationships & Data Flow
1. On page load, the Static Web Server delivers index.html + Angular bundles → Angular bootstraps in the browser.
2. RouterModule reads the URL → loads corresponding Component (e.g., “/projects” → ProjectsComponent).
3. Component calls its Service (ProjectsService) → either reads local JSON or calls an external REST API.
4. Service returns data → Component renders list of projects via its template & CSS.
5. LanguageSelectorComponent invokes TranslationService → loads appropriate XLF file → TranslatePipe dynamically transforms template keys.
6. LatestUpdatesComponent uses LatestUpdatesService → fetches GitHub release info → renders update feed.
Key Architectural Patterns & Principles
– Separation of Concerns:
• Components for UI + template + styles
• Services for data retrieval & business logic
• Pipes for presentation transformation (i18n)
– Module-based organization (AppModule)
– Declarative routing (AppRoutes)
– Configuration driven (app.config.ts for environment settings)
Detailed Checklist
– [ ] AppModule → Router → AppComponent flow
– [ ] Static data sources (messages.xlf, images) and external API endpoints
This layout ensures you capture every essential architectural element—presentation, routing, business logic, data sources—and clearly conveys how your personal portfolio SPA is structured and interacts at runtime.