django-service-objects VS Django-Styleguide

For that "service classes" I use Service Objects that are based on django forms and because of that brings you additional input data validation level.

There are alternatives, such as HackSoft's Django style guide, but fat models, thin views is usually good enough.

I think this is a great resource. The only comment I have is on the Thin Views chapter. Instead of attaching logic to the models, I like to make a services.py file in my app that has functions that satisfy all sorts of business logic.

Here's another opinionated Django guide: https://github.com/HackSoftware/Django-Styleguide if anyone's interested

you can follow the Django Style Guide by Hacksoft. They have awesome style guide for you on github https://github.com/HackSoftware/Django-Styleguide

I would also recommend taking a look at HackSoftware's django styleguide repo. I found applicable. You don't have to follow it religiously (or at all) but still brings up some good food for thought.

I've read from Django Styleguide, Two Scoops of Django, Django for Startups, Still No Service, and a few threads even here in this subreddit (they largely reference above).

Perhaps the Django style guide is suitable? It definitely isn't a basic tutorial but perhaps it's too advanced? https://github.com/HackSoftware/Django-Styleguide

well Django encourages you to tightly couple your django code with your views but even I do not like that way of doing it. So what I had started following HackSoft's Django styleguide - https://github.com/HackSoftware/Django-Styleguide to write my Django code.

Django-Styleguide – Django styleguide used in HackSoft projects