#26028: Improve instructions for overloading Django templates
-------------------------------+--------------------------------------
     Reporter:  pydanny        |                    Owner:  nobody
         Type:  Uncategorized  |                   Status:  new
    Component:  Documentation  |                  Version:  1.9
     Severity:  Normal         |               Resolution:
     Keywords:                 |             Triage Stage:  Unreviewed
    Has patch:  0              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  0
-------------------------------+--------------------------------------

Comment (by cjrh):

 When I was researching how to customize third-party apps, I found this
 blog entry very useful for a rapid overview:

 http://blog.yourlabs.org/post/19777151073/how-to-override-a-view-from-an-
 external-django-app

 I also recently discovered this third-party app loader that allows one to
 extend templates, rather than replace them completely:

 https://pypi.python.org/pypi/django-apptemplates/

 From IRC discussions, it sounds like quite a few experienced people use
 forking for customization.  It would be good to have clear guidelines
 about how to avoid forking , as well as guidelines on how to correctly do
 forking when you really have to.

--
Ticket URL: <https://code.djangoproject.com/ticket/26028#comment:4>
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 post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.16bb5265e9946b7a0d544cc7ad86b3ef%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to