project-conventions

Separate FastAPI routing logic, business logic in the Service layer, and data access in the Repository layer, wiring them together with dependency injection and centralized constants to enforce project conventions and streamline onboarding.

Standard conventions include enforcing architecture layering, applying consistent dependency injection, centralizing constants, and establishing uniform error handling, code style, linting, and testing standards to accelerate development and improve code quality.

Enforce naming and error handling conventions by auditing your backend project to standardize architecture layering, centralize constants across modules, and apply uniform error handling and linting rules ready for CI/CD integration.

Yes, a new NGO backend can adopt these conventions to accelerate development, improve code quality, streamline CI/CD, and reduce onboarding friction by enforcing consistent architecture, testing, and documentation standards.

The best way to set up dependency injection and centralized constants is to audit your backend project and align Router, Service, and Repository layers with consistent DI wiring and centralized constants across all modules.