If you're curious about how to set up a modern JS frontend on top of Django, I wrote up a tutorial recently.
It might be helpful if you're debating between trying a Single Page App approach or some other design: <a href="https://medium.com/@theSquashSH/reconciling-djangos-mvc-templates-with-react-components-3aa986cf510a" rel="nofollow">https://medium.com/@theSquashSH/reconciling-djangos-mvc-temp...</a>
I had used Django back in version 1.3 and was just thinking today of how I need to brush up, as it has been a few years.<p>The timing of this article couldn't have been better. Now I've got my weekend cut out :)
Django is such an important building block of the web, it completely deserves this tutorial on MDN.<p>As someone who came to Django quite late, I cannot stress enough how coding in Django is refreshing. Yes it's not about microservices nor it bring all the trendy technologies that we all hear about.<p>And that's just fine, you get things done with it and at the end of the day this is what matters.
Dumb question, why does the guide suggest that you create an empty folder and then initialize the project from there? (django_test/mytestsite, locallibrary/locallibrary)<p>As far as I can tell, no file, hidden or otherwise, is left in the outer folder.
It has been years since I have used Django - do they still expect everything in the model to go in a single file or can you put each model in it's own file now?
Oh man, this is far superior to the official Django tutorial I think. MDN really does a good job at holding your hand through the process.<p>There are moments when going through docs where way too many assumptions are made about what I know. This is where prerequisites and objectives really help out. I know what I am getting into before grokking.