[Python] How do I structure a Django REST Framework API backend when the frontend is already...

I'm building a Visitor Management System (VMS), and I've been given a complete frontend to work with. My task is to build the API-based backend using Django and Django REST Framework, which I'm familiar with from smaller projects.

However, I'm struggling to organize the backend efficiently and expose the right endpoints that match what the frontend expects.

Set up Django and Django REST Framework.

Defined my models (e.g., VisitorPreRegistration, User).

Started creating serializers and basic viewsets.

My Questions: What is the best way to structure a Django API-only project, especially when the frontend is decoupled?

Are there packages or patterns (like cookiecutter-django, DRF extensions, or project templates) that help speed up development and reduce boilerplate?

How do I effectively map frontend forms and filters (e.g., visitor type, host search, arrival time) to backend endpoints?

What I tried: I’ve read the Django and DRF documentation, and tried watching a few YouTube tutorials, but most assume a monolithic approach or skip the API-only setup with an existing frontend.

Continue reading...