#35768: Add a Profile How-To
-------------------------------------+-------------------------------------
Reporter: Carlton | Owner: William S. Vincent
Gibson |
Type: New | Status: assigned
feature |
Component: | Version: 5.0
Documentation |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Following [https://forum.djangoproject.com/t/what-does-the-community-
think-to-carltons-take-on-auth-user/34672 the forum discussion here], add
a ''Profile How-To'' showing best practices for a profile model related to
the User model.
* Show a best-practice model — with decent name fields.
* Be clear to tell folks that the existing `first_name`/`last_name` fields
are outdated (at best) and say it’s OK to just ignore them.
* Show creating the profile instance — with a signal, inline, or using
get_or_create()
* Give an introduction to template fragment caching.
--
Ticket URL: <https://code.djangoproject.com/ticket/35768>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070191fba3871c-8beeb80c-c697-4374-a98c-1a792007eef7-000000%40eu-central-1.amazonses.com.
