Django - Tutorial 035. Different templates for rendering different types of content in the search results

Django, template, content, Search

Constant visitors of the site who use the search on the site, probably noticed that the display of articles differs from displaying comments in the search engine issue of the site. This was achieved by the fact that each content type has its own template for rendering, which is substituted for the rendering of the page, depending on what content was found in the search.

Let's look at the example of issuance.

You see, here the presentation of the comment differs from the article, but they are output in the framework of one search issue, as was done in the previous article.

But this is done much more elegantly than selecting via if else . Honestly, I myself really like this decision.

For each data model, you need to define a field that stores the path to the template to display the object of that model. In each model, this field must have the same name. It is very important.

For example, we do this

class Article(models.Model):
    TEMPLATE_PREVIEW = 'home/article_preview.html'

class Comment(models.Model):
    TEMPLATE_PREVIEW = 'home/comment_preview.html'

class Topic(models.Model):
    TEMPLATE_PREVIEW = 'home/topict_preview.html'

class Post(models.Model):
    TEMPLATE_PREVIEW = 'home/post_preview.html'

In each of these templates, we can prescribe our own display of content, which is required. For example, for an article

<div>
    <a href="{{ object.get_absolute_url }}"><h2>{{ object.itle }}</h2></a>
    {{ object.content|safe }}
    <p><a class="btn btn-default btn-sm" href="{{ object.get_absolute_url }}">Читать далее</a></p>
</div>

And for all the other templates, we can write something else. The main thing is that all methods and fields, as well as the name of a single object, be the same in all templates.

And the pattern of search results may look like this

{% load tz %}
{% load trans from i18n %}
{% load bootstrap_pagination from bootstrap4 %}
<div id="object-list">
    {% for object in object_list %}
        {% include object.TEMPLATE_PREVIEW %}
    {% empty %}
        <div class="card card-body mb-3">{% trans 'Nothing found' %}</div>
    {% endfor %}
    {% bootstrap_pagination object_list pages_to_show="10" url=last_question %}
</div>

The nuance is that we are used to passing the string name of the template to the include tag, for example so

{% include 'home/article_preview.html' %}

But no one said that we can only do so, and also no one said that we can not take the path to the template directly from the object, the content of which we want to render. That is, you can safely write so

{% include object.TEMPLATE_PREVIEW %}

And if you consider that each object has its own TEMPLATE_PREVIEW , then the files there will be connected different, and that means each kind of content will have its own style of rendering.

For Django I recommend VDS-hosting TIMEWEB