How isaacojeda/devtoposts works
Overall structure
• Realize that the repository is not a single application but a collection of independent projects/samples.
Main components
• For full‑stack demos, clearly distinguish the client (typically Angular/Blazor code in directories like “ClientApp”, “Components” or “Pages”) from the server (API, SignalR hubs, Controllers, Program.cs, etc.). For instance, in AngularJwtBFF or SignalRExample, show the separation between the Angular (or Blazor) client and the corresponding .NET back‑end.
• For API or authentication examples, highlight the API endpoints, middleware components, database access layers (Persistence, Migrations, DbContext) and any authentication handlers (e.g. ApiKeySchemeHandler, Token/Authorization controllers).
Interactions and dependencies
• For multitenancy projects (MultiTenantApi and MultiTenantSingleDatabase), show how requests are routed via a tenant resolution strategy, with a shared database layer and the separation of tenant and admin contexts.
Architectural patterns and technology choices
• Areas where design principles or patterns are used: for example, the DecoratorPattern project clearly demonstrates layering (a basic WeatherService decorated with caching and logging).
• That many projects employ the .NET “minimal API” style (e.g., MinimalAPIFluentValidation, MinimalApiScrutor, MinimalApis) with dependency injection, middleware, and configuration layers.
– Rounded rectangles for back‑end components (Controllers, Services, Workers)