#8944: Documentation should go further than just your first application
------------------------------------+---------------------------------------
Reporter: simon | Owner: nobody
Status: new | Milestone:
Component: Documentation | Version: 1.0
Resolution: | Keywords: djangocon
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Comment (by akaihola):
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.
--
Ticket URL: <http://code.djangoproject.com/ticket/8944#comment:2>
Django <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
