django-conventions

Django conventions codify and enforce best practices for project layout, app organization, models, views, forms, templates, security, and performance. Use this reference during development and code reviews to ensure consistent structure, prevent anti-patterns, and maintain code quality across your entire Django ecosystem.

Django model conventions recommend using TextChoices for choice fields, explicit on_delete and related_name on foreign keys, indexes and constraints in Meta, custom managers and QuerySets, and proper timestamp fields. These practices prevent silent data loss, improve query performance, and ensure database integrity.

Best practices cover choosing between class-based and function-based views, organizing DRF serializers, implementing proper permissions, and handling templates. Following these conventions improves code reusability, security, and maintainability while keeping your view layer consistent and testable.

Django security conventions enforce CSRF protection, HTTPS, XSS prevention, SQL injection avoidance through ORM, and keeping secrets out of code. Applying these defaults from project start reduces vulnerability surface and prevents common security misconfigurations.

Yes. This reference provides a prioritized checklist for code reviews, helping teams identify deviations from Django standards, anti-patterns, and maintainability issues. Use it during reviews to verify adherence to conventions and deliver consistent feedback.

Django conventions recommend clear separation between project configuration and apps, environment-specific settings files, and structured app organization. This approach prevents configuration conflicts, simplifies deployment, and keeps projects maintainable as they scale.