Portfolio Admin

The system is organized around a modular Express router layer, where each domain (blog, project, testimonial, achievement, etc.) has its own route file and corresponding controller. Controllers encapsulate business logic and interact with Mongoose models, ensuring a clear separation of concerns. Data ingestion begins at the HTTP layer, passes through the auth middleware for JWT validation, and then reaches the controller which performs validation, transformation, and persistence to MongoDB collections.

Execution flow starts with a request hitting server/server.js, where global middleware (CORS, body‑parser, logging) is applied. After authentication, the request is dispatched to the appropriate router (e.g., blogRoutes.js). Controllers use async/await patterns to handle database operations, returning standardized JSON responses. Errors are caught by a centralized error‑handling middleware, providing consistent error payloads.

Security guardrails include JWT‑based authentication on all mutating endpoints, role‑based checks inside controllers, and input sanitization via validation libraries. Sensitive routes such as bulk deletions and reorder operations are protected by the same auth middleware, reducing attack surface.

The build topology leverages TypeScript for type safety across the codebase, with ESLint enforcing code quality. The project is compiled using tsc and run with node in production, while development uses nodemon for hot‑reloading. Continuous integration scripts (not shown) likely run linting and unit tests before deployment.