Django Checklists | Development Standards

New View

Building any Django view — auth, permissions, form validation, business logic placement, response handling

Template

Building any Django HTML template — 3-folder structure, inheritance, no inline styles/scripts, data-* pattern

Model

Creating or modifying a Django model — field types, relationships, on_delete, null/blank, constraints, indexes, Meta class, migrations

Form / Serializer

Building a Django Form or DRF Serializer — field definitions, validation timing, field-level vs cross-field validation, read_only/write_only

DRF API View

Building a DRF API view — view type selection, permission classes, serializer wiring, service delegation, response format, pagination

Quick Reference — Core Django Rules

Business logic in services.py — not in views, templates, or models
Every protected view uses @login_required or LoginRequiredMixin
All user input validated through Django Form or Serializer, not raw request.POST
No <style> blocks in templates — CSS in static/css/
No <script> blocks with logic in templates — JS in static/js/
Every template extends base.html
Repeated HTML sections use {% include %}, not copy-pasted
Django data passed to JS via data-* attributes — never string interpolation in <script>
Role/permissions read from database — never from request payload or session

Related Standards

Backend-First Logic Standard Django Template Standards Code Reusability Standards