This is nice. I've been wanting to dabble a bit in Django, but I find it a bit hard to find basic information like this, for example, how to decide when creating a separate app inside a project is better than putting everything in a single app.
It definitely helps to have conventions to follow while you're learning, until you become proficient enough to break those conventions.
Comments
This is nice. I've been wanting to dabble a bit in Django, but I find it a bit hard to find basic information like this, for example, how to decide when creating a separate app inside a project is better than putting everything in a single app.
It definitely helps to have conventions to follow while you're learning, until you become proficient enough to break those conventions.
You might find James Bennett's book "Practical Django Projects" helpful:
http://www.apress.com/open-source/python/9781430219385
https://bitbucket.org/ubernostrum/practical-django-projects/...
It talks about Django's apps focus and tries to get one out of the habit of "dumping it all in one app in the project".
Eric Holscher wrote an article about Reusable App conventions:
http://ericholscher.com/projects/django-conventions/app/