Opened 5 months ago
Last modified 5 months ago
#35768 assigned New feature
Add a User Profile How-To to docs
Reported by: | Carlton Gibson | Owned by: | William S. Vincent |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Pull Requests: | How to create a pull request | ||
Description ¶
Following 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.
According to the ticket's flags, the next step(s) to move this issue forward are:
- To provide a patch by sending a pull request. Claim the ticket when you start working so that someone else doesn't duplicate effort. Before sending a pull request, review your work against the patch review checklist. Check the "Has patch" flag on the ticket after sending a pull request and include a link to the pull request in the ticket comment when making that update. The usual format is:
[https://github.com/django/django/pull/#### PR]
.
Change History (2)
comment:1 by , 5 months ago
Triage Stage: | Unreviewed → Accepted |
---|---|
Version: | 5.0 → dev |
comment:2 by , 5 months ago
Summary: | Add a Profile How-To → Add a User Profile How-To to docs |
---|
Note:
See TracTickets
for help on using tickets.
Gladly accepting this!
Also TIL (not really today but very recently) about template fragment caching. Looking forward to reading this!