I am developing firedating.me using Django. It is a community of FIRE (Financial Independence / Early Retirement) enthusiasts looking for friends and a partner. Unfortunately the FIRE community is very dispersed and one can feel very lonely. So I made this site to help people build meaningful connections.
I am actually a huge fan of Django. It boosts my productivity a lot. The only minor issue I experience is that the way POST forms and templates work biases how I make UI. I.e. all UIs tend to be very page oriented - 1 page = 1 form - and some logic is leaking into templates. As a result, my UIs feel too coupled with the backend and this makes them harder to support. I am considering writing a separate frontend treating the backend as a blackbox instead. Wondering whether anyone experienced something similar.
Your site looks awesome, will be sure to add it to builtwithdjango.com.
Regarding your issue, you could try adding a for to an existing "View" via get_context_data. Then in the HTML add action tag to your form that with the actial Form View endpoint. This should allow you to have more that one form on a page. I agree that was a little annoying for me at first too. Maybe I'll write a post on how to do this.
Otherwise splitting the frontend from the backend can be a solution too. This will probably take a little more time.
I am actually a huge fan of Django. It boosts my productivity a lot. The only minor issue I experience is that the way POST forms and templates work biases how I make UI. I.e. all UIs tend to be very page oriented - 1 page = 1 form - and some logic is leaking into templates. As a result, my UIs feel too coupled with the backend and this makes them harder to support. I am considering writing a separate frontend treating the backend as a blackbox instead. Wondering whether anyone experienced something similar.