I wanted comments/feedbacks/insights from fellow hackers.

Is it worth the effort?

One reason i want to do it is because it will make the project look more organized and easy for someone to read the code and understand. The design guidelines are not my own and have been taken from authentic sources(listed at the end of the post)

One reason i doubt doing it is, people might have different requirements and people should be free to do things their own way. These are only few generic stuff and an experienced programmer will himself take care of it, as per the needs. Besides i am relatively inexperienced and it will take me some considerable amount of time to code.

Please let me know your thoughts.

Following would be my requirement list:

Templates:

There should be one base.html at the project level, and one base.html at each of the app levels. The app level base.html should extend the project level base.html; {{ foo }} not {{foo}};

Settings File: Use relative path in settings.py; Sensitive things as database password API keys in localsettings; Custom Middlewares and Context Processors should have try catch;

Urls: Each of the urls should have a name, corresponding to the view name There should be one urls.py at the project level, and one urls.py at each app level. The project level urls.py should include each of the urls.py under a prefix. Do not use primary key in urls.

Models:

Field naming Convention: first_name not FirstName; Use Model Forms instead of Forms; There should be a __unicode__ method and use of permalink; Instead of get_absolute_url; The model of inner classes should be as follows: db fields managers meta class db fields managers unicode str save absolute_url

Following are the sources i went through to make the above list:

1.http://lincolnloop.com/django-best-practices/

2.http://www.sparklewise.com/django-settings-for-production-and-development-best-practices/

3.https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/coding-style/

4.http://assets.en.oreilly.com/1/event/27/Django%20in%20the%20Real%20World%20Presentation.pdf