Opened 15 years ago
Closed 14 years ago
#8944 closed (invalid)
Documentation should go further than just your first application
Reported by: | simon | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | 1.0 |
Severity: | Keywords: | djangocon | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Change History (4)
comment:1 Changed 15 years ago by
Component: | Uncategorized → Documentation |
---|
comment:2 Changed 14 years ago by
comment:3 Changed 14 years ago by
It's not clear what to do with this other than continue to write more and better docs.
comment:4 Changed 14 years ago by
Resolution: | → invalid |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
I was helping someone on the #django IRC channel today, and he/she hadn't yet understood how functionality can be divided into separate apps.
I took a look at the contents of the Django documentation and the 1st edition of the Django Book, but couldn't find anything appropriate there to suggest for reading. I also found it non-trivial to explain app layout quickly.
The specific problem of the person in IRC had to do with multiple sites using common functionality. I pointed them to the sites framework, but in addition to that they need a basic understanding of the app system.
mattmcc pointed out the blog post at http://www.b-list.org/weblog/2006/sep/10/django-tips-laying-out-application/
I suggest that app layout be explained in the documentation with examples.