<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title/><link>http://localhostblog/feed/library.xml</link><description>Library</description><atom:link href="http://localhost/blog/feed/library.xml" rel="self"/><language>en-us</language><category>Library</category><category>Django</category><lastBuildDate>Fri, 11 Apr 2025 14:12:54 +0000</lastBuildDate><item><title>Django TemplateYaks</title><link>https://localhost/articles/django-template-yaks.html</link><description>&lt;p&gt;{% verbatim %}Lately I&amp;#x27;ve been writing more Django template tags than usual and last Thursday morning, I spotted a &lt;a href="https://social.joshthomas.dev/@josh/113320955214591905"&gt;Mastodon Thread 🧵&lt;/a&gt; about Django templates and composability.&lt;/p&gt;

&lt;p&gt;As part of this thread, I mentioned the fact that &amp;quot;complex&amp;quot; (or advanced) templatetags were a pain to write and that one thing that was missing for Django templates to be composable was a version of &lt;code&gt;{% include %}&lt;/code&gt; that supports &amp;quot;blocks&amp;quot; (ie: something like &lt;code&gt;{% includeblock %}...{% endincludeblock %}&lt;/code&gt;).&lt;/p&gt;

&lt;p&gt;&lt;blockquote class="mastodon-embed" data-embed-url="https://mastodon.social/@EmmaDelescolle/113321127804748474/embed" style="background: #FCF8FF; border-radius: 8px; border: 1px solid #C9C4DA; margin: 0; max-width: 540px; min-width: 270px; overflow: hidden; padding: 0;"&gt; …&lt;/blockquote&gt;&lt;/p&gt;</description><pubDate>Tue, 22 Oct 2024 00:00:00 +0000</pubDate><guid>https://localhost/articles/django-template-yaks.html</guid><category>Django</category><category>Library</category></item></channel></rss>