Django templates directory location

Note that we added the custom H1 tag with some text as well. If we try to render this template via a view function it will not yet work, and we would see an error like this one. In order to use our templates, we must register them in Django. To register templates in Django, we can open the settings. The out-of-box settings are shown here. Using this variable, we can now configure DIRS as shows below to make Django aware of the templates directory in our goals app. The use case for a template is for the HTML of that template to be sent back to the user when a particular view function triggers.

To do this, the template needs to be converted to an HTML string which can be sent back with the response to the user. About the best location, Django looking for template like this : DIRS defines a list of directories where the engine should look for template source files, in search order. Each backend defines a conventional name for the subdirectory inside applications where its templates should be stored.

Wilfried Wilfried 1, 1 1 gold badge 10 10 silver badges 18 18 bronze badges. Previous solution didn't work in my case. Look my answer. TonyM TonyM 1 1 silver badge 7 7 bronze badges. When would this be a good idea?

Isn't it slower to load templates from the DB? Dont you become dependent on db if you store templates in db plus will you make your db a part of git commits? How will you coordinate between the changes made by different users in the templates? This was written way before I became aware of git. Not even sure I was using svn at the time.

I'd recommend using version control systems now. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science.

Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Linked 6. Note that this example uses pathlib , loaded by default for Django 3. If you are using a settings. Within the new static folder, create subfolders for each type of static file such as css , js , and img. On the command line, these can be added using the mkdir command:. Now you can add all your static assets.

So the base. If you run the local webserver at this point-- python manage. And that is because static assets must be explicitly loaded into the templates.

Let's assume you are using a base. Making both updates would look as follows:. If you save and reload the web page, you'll see the changes. Adding links for either images in an img folder or JavaScript in a js folder would look as follows:. Therefore, Django comes with the built-in collectstatic command that compiles all static files into a single directory suitable for deployment into production.

By default, it is implicitly set to django. The end result is that there are four configurations required for static files and the python manage. A new staticfiles directory will be created which has folders for admin the built-in admin has its own static files , staticfiles.