Exercise 3: One Main Slot vs. Several Named Regions — Possible Solution
====================================================================

RAILS' PLAIN yield: ONE, IMPLICIT SLOT
------------------------------
    <%= yield %>

Per Rails' own documentation, this "identifies a section where content
from the view should be inserted" -- but there is only ever one of
these implicit slots per layout, standing in for "whatever the current
view's own template rendered." It has no name, because it doesn't need
one: there's nothing else it could possibly refer to.

DJANGO/JINJA2's block: SEVERAL, EXPLICITLY NAMED SLOTS
------------------------------------------------------------
    {% block header %}...{% endblock %}
    {% block sidebar %}...{% endblock %}
    {% block footer %}...{% endblock %}

Each block is independently named and independently overridable. A
child template can override header without touching sidebar or
footer at all, and each one can carry its own separate default.

RAILS' OWN SECOND MECHANISM CLOSES THE SAME GAP
------------------------------------------------------------
Rails doesn't stop at plain yield -- content_for exists specifically
because a real layout usually needs more than one region:

    <%= yield :sidebar %>          <!-- in the layout -->
    <% content_for :sidebar do %>  <!-- in the child view -->
      <p>Sidebar content.</p>
    <% end %>

This is structurally the same idea as Django/Jinja2's own named block
-- a named slot, a named override -- just split across two different
keywords (yield and content_for) instead of Django/Jinja2's one
(block) doing double duty as both the placeholder and the default.

WHY A REAL HEADER/SIDEBAR/FOOTER LAYOUT NEEDS THE NAMED KIND
------------------------------------------------------------
A page with a header, a sidebar, and a footer needs to let a child
view supply DIFFERENT content for each of those three regions
independently -- one page might override only its sidebar, another
might override its footer and header but leave the sidebar at its
layout-wide default, and so on. Rails' plain yield has no way to
express that at all: it identifies exactly one insertion point, the
overall page body, with no concept of "this content belongs in the
header specifically" versus "this content belongs in the footer."
Only the named mechanisms -- content_for on Rails' side, block on
Django/Jinja2's side -- can carry that per-region distinction, because
only they attach a real name to each individual region a child might
want to target on its own.

WHY THIS WORKS AS AN ANSWER
----------------------------
It distinguishes the real, structural difference (one implicit slot
vs. several independently named ones) rather than treating yield and
content_for as interchangeable, shows Rails' own real syntax for both,
and explains concretely why a three-region layout specifically needs
independent naming -- because different pages need to override
different regions independently, something a single unnamed slot
can't express at all.