search

APSL / puput

A Django blog app implemented in Wagtail
MIT License
626 stars 159 forks source link

Document how to extend the default template #110

Open marctc opened 7 years ago

marctc commented 7 years ago

As users couldn't select a template (for the moment https://github.com/APSL/puput/issues/42) it could be useful have a section in the documentation that explains how to extend the default template. This will avoid further issues like https://github.com/APSL/puput/issues/63

yarsanich commented 7 years ago

+1

MiltonLn commented 7 years ago

+1

sabueso commented 7 years ago

+1

pjmcdermott commented 6 years ago

As modifying an existing set of templates is such an involved procedure, I often think comprehensive documentation of the variables, methods, template tags that are available for a Django app would be a much better approach. Any JavaScript dependencies would also need to be noted. An unstyled skeleton template might also be useful, as an example, but all the CSS styling and anything else extraneous needs to be removed. Using Django Compressor might be useful, but it is a site-wide decision, and one for the end of the development process--including it in a Django app only confuses the initial development.

I have been dealing with this problem for Puput today, and after copying the entire Puput template structure to my project override template folder, I spent the afternoon iteratively deleting stuff until I got to a base I could work with....

Followthevu commented 2 years ago

+1