Here's a set of default templates I wrote. I respect the reasoning for not providing them, but implementing 15 templates to get started out of the box is a bit onerous.
https://github.com/yourcelf/django-registration-defaults
The main developer James Bennett has discussed his reasons several times on multiple venues, but the FAQ in the Read the Docs for django-registration gives details in "Does django-registration come with any sample templates I can use right away?"
1 "Providing default templates with an application is generally hard to impossible" not true since the introducton of app template loader
2 "A number of things in django-registration depend on the specific registration backend" 99 % uses standard db/user built in backend. If you use social-auth or similar you (almost ) do not need registration
I second 'yourcelf' comment below.. I always use his template as a starting point.
May be a management commas that generate those default templates? ( not a big fan of template generation anyway)
I've used Django Registration on at least 5 projects, and despite having built a good set of templates with the first project, haven't ever been able to reuse them completely.
Registration is (or at least, probably ought to be) a very personal set of decisions for any app/project. I agree that there could be some easily packaged, cookie-cutter defaults, but having experienced all the reasons James Bennett cited for not packaging any templates, I have to say that he's not crazy for their omission.
yourcelf|12 years ago
huxley|12 years ago
https://django-registration.readthedocs.org/en/latest/faq.ht...
Other people have provided good baselines to work from, the Djen of Django provides explanations with their samples:
http://agiliq.com/books/djenofdjango/chapter5.html#reusable-...
(note I haven't upgraded to 1.0 so not sure if there are any incompatibilities)
sammy_rulez|12 years ago
1 "Providing default templates with an application is generally hard to impossible" not true since the introducton of app template loader
2 "A number of things in django-registration depend on the specific registration backend" 99 % uses standard db/user built in backend. If you use social-auth or similar you (almost ) do not need registration
I second 'yourcelf' comment below.. I always use his template as a starting point.
May be a management commas that generate those default templates? ( not a big fan of template generation anyway)
zalew|12 years ago
bmelton|12 years ago
Registration is (or at least, probably ought to be) a very personal set of decisions for any app/project. I agree that there could be some easily packaged, cookie-cutter defaults, but having experienced all the reasons James Bennett cited for not packaging any templates, I have to say that he's not crazy for their omission.