How germann-ux/acc-complex works
Project type and purpose
• From the file tree and minimal README (“ACC‐Complex”), it’s clear this is a full-stack .NET solution for an educational platform (“ACC”) that includes a Blazor-based frontend, a RESTful API, data persistence via EF Core, shared DTOs/services, external integrations (e.g., a compile service), identity management, and tests.
• Key features: interactive C compiler page, course content navigation, classroom views (students/teachers), library, progress tracking, notifications, and user/account management.
File structure
• Top-level solution projects:
• ACC.WebApp & ACC.WebApp.Client – Blazor Server/Client Web UI and static asset hosting, plus authentication components.
• src/ACC.API – ASP.NET Core Web API with Controllers → Services → Interfaces layered structure.
• src/ACC.Data – EF Core DbContext + Entities + Migrations for a SQL database.
• src/ACC.Shared – Shared DTOs, interfaces, core services (e.g., CompileService, ServiceResult).
• src/ACC.ExternalClients – clients/integrations for external services (e.g., external compilers, SMS, email).
• src/ACC.AppHost – generic host project (likely used to wire up/run the API in some environments).
• ACC.ServiceDefaults – shared default configuration and extension helpers.
• tests/ACC.Tests – unit tests for services (e.g., NavegacionContenidoServiceTests).
README for architecture hints
• The README only names the project “ACC-Complex,” so we rely on code structure to infer architecture: a layered, modular design with clear separation of concerns and dependency-injected services.
Essential details to capture
• Authentication flow: Browser → Identity components in ACC.WebApp → Protected API endpoints.
• Compile flow: Compiler page → CompilerController → CompileService → External compile engine.
• Expose the Shared DTO boundary between client and server.
• Migrations updating the database schema.
• Unit tests as a separate validation overlay against service implementations.