Why templates separate presentation in Django - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why do Django templates separate presentation from logic?

In Django, templates are used to separate the presentation layer from the business logic. What is the main benefit of this separation?

A It prevents any changes to the website layout once the code is written.

B It forces all data processing to happen in templates, improving performance.

C It combines HTML and Python code in one file for faster development.

D It allows designers to work on HTML without touching Python code, making collaboration easier.

💡 Hint

Think about who works on design and who works on code in a team.

Separating templates from logic lets designers focus on HTML and CSS, while developers handle Python code. This clear division improves teamwork and maintainability.

❓ component_behavior

intermediate

What happens if you put complex logic inside a Django template?

Consider a Django template that contains complex data processing logic instead of just displaying data. What is the likely outcome?

A The template becomes hard to read and maintain, making debugging difficult.

B The template runs faster because it handles all logic internally.

C The Django framework automatically moves logic to views for you.

D The template will ignore the logic and only show static content.

💡 Hint

Think about code clarity and who should handle logic.

Templates are meant for presentation. Complex logic in templates makes them messy and hard to maintain. Logic should stay in views or models.

📝 Syntax

advanced

Identify the correct way to pass data to a Django template

Which of the following Django view snippets correctly passes a list of items to a template named 'list.html'?

Django

def item_list(request):
    items = ['apple', 'banana', 'cherry']
    # Fill in the correct return statement below

A return render(request, 'list.html', {'items': items})

B return render('list.html', request, {'items': items})

C return render(request, {'items': items}, 'list.html')

D return render(request, 'list.html', items)

💡 Hint

Check the order of arguments in the render function.

The render function takes the request, template name, then context dictionary. Only option A follows this order correctly.

❓ state_output

advanced

What will the Django template output?

Given the context {'user': {'name': 'Anna', 'age': 30}}, what will this Django template output?

Django

{% if user.age > 18 %}
  <p>Welcome, {{ user.name }}!</p>
{% else %}
  <p>Access denied.</p>
{% endif %}

A <p>Welcome, {{ user.name }}!</p>

B <p>Access denied.</p>

C <p>Welcome, Anna!</p>

D Template error due to invalid syntax

💡 Hint

Check the age condition and how variables are displayed.

The user's age is 30, which is greater than 18, so the first block runs and shows the welcome message with the user's name.

🔧 Debug

expert

Why does this Django template raise an error?

Consider this Django template snippet:

{% for item in items %}
  
{{ item.name }}
{% endfor %}

The view passes {'items': ['apple', 'banana']} as context. Why does this cause an error?

A Because the for loop syntax is incorrect and missing a colon.

B Because strings do not have a 'name' attribute, causing a runtime error.

C Because the template variable 'items' is not defined in the context.

D Because Django templates cannot loop over lists.

💡 Hint

Think about the type of each item in the list and what the template tries to access.

The context 'items' is a list of strings. Strings do not have a 'name' attribute, so {{ item.name }} causes an error.

Practice

1. Why do Django templates separate presentation from business logic?

easy

A. To make the server run faster

B. To speed up the database queries

C. To reduce the size of the HTML files

D. To make the website easier to build and maintain

Solution

1. Step 1: Understand the role of templates

   Django templates handle how the page looks, separate from how data is processed.

2. Step 2: Recognize benefits of separation

   This separation makes it easier to build, change, and maintain the website without mixing code and design.

3. Final Answer:

   To make the website easier to build and maintain -> Option D

4. Quick Check:

   Separation of concerns = easier maintenance [OK]

Hint: Templates separate look and logic for easier updates [OK]

Common Mistakes:

• Thinking templates speed up database queries
• Believing templates reduce HTML file size
• Assuming templates make server faster

2. Which of the following is the correct way to extend a base template in Django?

easy

A. {% include 'base.html' %}

B. {% extends 'base.html' %}

C. {% import 'base.html' %}

D. {% load 'base.html' %}

Solution

1. Step 1: Identify the template inheritance tag

   Django uses the {% extends %} tag to inherit from a base template.

2. Step 2: Confirm correct syntax

   The syntax is {% extends 'base.html' %}, which tells Django to use the base template as a parent.

3. Final Answer:

   {% extends 'base.html' %} -> Option B

4. Quick Check:

   Template inheritance uses extends [OK]

Hint: Use {% extends %} to inherit templates [OK]

Common Mistakes:

• Using include instead of extends for inheritance
• Confusing load or import with extends
• Wrong syntax with missing quotes

3. Given this base template snippet:

{% block content %}Base Content{% endblock %}

And this child template snippet:

{% extends 'base.html' %}{% block content %}Child Content{% endblock %}

What will be displayed when rendering the child template?

medium

A. Base Content

B. Base ContentChild Content

C. Child Content

D. Error: block content redefined

Solution

1. Step 1: Understand block overriding in templates

   The child template overrides the 'content' block defined in the base template.

2. Step 2: Determine rendered output

   Because the child block replaces the base block, only 'Child Content' is shown.

3. Final Answer:

   Child Content -> Option C

4. Quick Check:

   Child block overrides base block [OK]

Hint: Child blocks replace base blocks in templates [OK]

Common Mistakes:

• Thinking base and child content combine
• Expecting an error on block redefinition
• Assuming base content shows instead

4. What is wrong with this Django template code?

{% extends 'base.html' %}{% block content %}Hello{% endblock %}{% endblock %}

medium

A. There is an extra {% endblock %} tag

B. The extends tag is missing quotes

C. The block name is invalid

D. The template is missing a load tag

Solution

1. Step 1: Check block tags pairing

   There is one {% block content %} but two {% endblock %} tags, causing mismatch.

2. Step 2: Identify syntax error

   Extra {% endblock %} causes a template syntax error.

3. Final Answer:

   There is an extra {% endblock %} tag -> Option A

4. Quick Check:

   Block tags must match exactly [OK]

Hint: Count block and endblock tags carefully [OK]

Common Mistakes:

• Ignoring extra endblock tag
• Thinking quotes are missing in extends
• Assuming block name is wrong

5. You want to reuse a header and footer on multiple pages in Django. Which approach best uses templates to separate presentation?

hard

A. Use template inheritance with a base template containing header and footer blocks

B. Write header and footer HTML inside each view function

C. Copy header and footer HTML into every page template

D. Load header and footer HTML using JavaScript after page loads

Solution

1. Step 1: Identify best reuse method in Django templates

   Template inheritance allows common parts like header and footer to be defined once in a base template.

2. Step 2: Understand separation of concerns

   This keeps presentation consistent and easy to update without repeating code in every page.

3. Final Answer:

   Use template inheritance with a base template containing header and footer blocks -> Option A

4. Quick Check:

   Template inheritance enables reuse [OK]

Hint: Use base template for common page parts [OK]

Common Mistakes:

• Copy-pasting header/footer in every template
• Mixing HTML into view functions
• Relying on JavaScript for static page parts