How 1asi0729-2510-4307-g2-influmatch/influmatch-webapplication works
Project type and purpose
• This is an Angular single‐page application (SPA) named “InfluMatchWebApplication” that connects brands and influencers via a dashboard.
• It is purely a front‐end client delivered as a static site (deployed via Azure Static Web Apps) that communicates with back‐end REST APIs for auth, profile and dashboard data.
File structure
• Top‐level directories:
• src/app/core – app‐wide services, guards, interceptors
• src/app/shared – shared modules, utilities, validators
• src/app/domain – entities, value‐objects, repository interfaces (clean architecture core)
• src/app/application – use‐cases that orchestrate business rules
• src/app/infrastructure – HTTP API adapters, DTOs, assemblers, repository implementations
• src/app/features – feature modules (auth, dashboard) each with presentation, domain, application, infrastructure sub‐folders
• Config/deployment: .github/workflows (CI→Azure), angular.json, vite.config.ts
README
• Standard Angular CLI project. No custom architecture docs—must infer layers from code organization.