How martromeros/r.d.a_front works
Project type and purpose
• This is a single-page, full-front-end Angular application (Angular CLI v19).
• It implements UI components for authentication (login/registration/forgot password), user roles (admin, alumno), shared layout (header, perfil), routing, and communicates with a backend via HTTP services.
File structure
• Top-level:
– angular.json, tsconfig*.json, package.json (build/config)
– src/ (application code)
– public/ or assets/ (static assets)
• src/app/:
– app.module, app.component, app.routes, app.config (root module, root component, routing, environment/global config)
– components/: feature components organized by domain (auth, admin, alumno)
– services/: singleton services (AuthService, UserService)
– shared/: shared UI (header, perfil) and modules (GeneralModule)
• Tests: *.spec.ts are unit tests.
README
• Confirms it’s an Angular CLI–generated front end
• Details how to serve, build, and test the app
Main components & their interactions
a. UI Layer (Components)
– Auth Components (login, registro, forgot-password)
– Admin Components (admin dashboard, reportes → filtros, tablas)
– Alumno Component
– Shared Components (header, perfil)
b. Services Layer
– AuthServicesService (login/logout/token management) → issues HTTP calls to Backend Auth API
– UserService (fetch user profile, alumno/admin data) → HTTP calls to Backend User API
c. Configuration
– app.config.ts holds endpoints/base URLs
d. Routing
– app.routes.ts defines route guards based on AuthService and directs to feature modules
e. Feature Modules
– GeneralModule bundles shared pipes/directives, used by feature modules
Relationships & data flows
– User action in a Component → invokes Service method (via Angular Dependency Injection)
– Service sends HTTP request → Backend API
– HTTP response → Service returns Observable → Component subscribes → updates UI
– app.routes.ts uses AuthService to guard/admin only routes
– Shared header/perfil display data from UserService
Architectural patterns & design principles
– Component-based UI (Angular Components)
– Separation of concerns (Components vs. Services vs. Modules)
– Feature modules for encapsulation (shared, general)
– Dependency Injection for services
– Single-page routing (Angular Router)
• Labels: Component names (e.g. LoginComponent), Service names (AuthService), Module names
– UI Components (blue)
– Services (green)
– Modules/Config (orange)
– External Systems (gray)
Use this structure as your canvas. Lay out the UI components on the left, services in the middle, and the backend API on the right. Encapsulate shared modules around the components they serve. This will give stakeholders and new engineers a crystal-clear picture of RDAFront’s architecture.