<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Emma has a blog</title><link>https://localhostfeeds_rss.xml</link><description/><atom:link href="http://localhost/feeds/_rss.xml" rel="self"/><language>en-us</language><category>Django</category><category>My2Cents</category><category>WebDev</category><category>django</category><category>Hardware</category><category>Library</category><category>EmberJS</category><lastBuildDate>Fri, 11 Apr 2025 14:12:54 +0000</lastBuildDate><item><title>Making Django Ready for the Next 20 Years</title><link>https://localhost/articles/django-steering-council-election-statement.html</link><description>&lt;p&gt;&lt;cc-blockquote with type="info"&gt;
If you&amp;#x27;d rather watch a video instead of reading an article, you can also have a look at my recent &lt;a href="https://www.youtube.com/watch?v=Urab3PVYXio"&gt;Djangonaut Space session on YouTube&lt;/a&gt; where I talked about similar topics.
&lt;/cc-blockquote&gt;&lt;/p&gt;

&lt;p&gt;As a member of the Django community for the past 10 years, I&amp;#x27;ve had the privilege of witnessing firsthand the project&amp;#x27;s growth and evolution.&lt;/p&gt;

&lt;p&gt;Over the decade, I&amp;#x27;ve seen many exciting changes and improvements that have shaped Django into the powerful tool it is today.&lt;br&gt;However, I&amp;#x27;ve …&lt;/p&gt;</description><pubDate>Wed, 04 Dec 2024 00:00:00 +0000</pubDate><guid>https://localhost/articles/django-steering-council-election-statement.html</guid><category>django</category></item><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><item><title>My Django wishlist explained</title><link>https://localhost/articles/django-wishlist-explained.html</link><description>&lt;p&gt;&lt;cc-blockquote with title="Disclaimer" type="warning"&gt;
Most of my job revolves around building Django-based applications. A lot of the tools you use to build applications are different than the tools you need to build websites.&lt;br/&gt;&lt;br/&gt;This post is written mostly from the perspective of an application developer.
&lt;/cc-blockquote&gt;&lt;/p&gt;

&lt;p&gt;With that out of the way, let&amp;#x27;s dig into the wishlist, my wishlist is based on the choices and libraries I include in a majority of project I start.&lt;/p&gt;

&lt;h3&gt;Deployment&lt;/h3&gt;

&lt;h4&gt;Documentation&lt;/h4&gt;

&lt;p&gt;As far as deplyment …&lt;/p&gt;</description><pubDate>Fri, 11 Oct 2024 00:00:00 +0000</pubDate><guid>https://localhost/articles/django-wishlist-explained.html</guid><category>Django</category><category>My2Cents</category></item><item><title>Stability without stagnation</title><link>https://localhost/articles/stability-without-stagnation.html</link><description>&lt;p&gt;Recently several different conversations around Django, stability, conservativism and/or breaking changes have caught my eye. Having been known a while ago in certain Python circles as &amp;quot;the Ember lady&amp;quot;, I couldn&amp;#x27;t help but draw some parallels with EmberJS and the way they have been managing releases since several years.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Disclaimer&lt;/strong&gt;: this post asks a lot of questions and provides absolutely no answer. My hope is that some of those questions might foster some fruitful discussions.&lt;/p&gt;

&lt;p&gt;For those …&lt;/p&gt;</description><pubDate>Thu, 03 Oct 2024 00:00:00 +0000</pubDate><guid>https://localhost/articles/stability-without-stagnation.html</guid><category>WebDev</category><category>Django</category><category>EmberJS</category><category>My2Cents</category></item><item><title>A new-to-me laptop</title><link>https://localhost/articles/new-to-me-laptop.html</link><description>&lt;p&gt;I&amp;#x27;ve decided to start blogging again and figured this would be a great subject to start with.&lt;/p&gt;

&lt;p&gt;So, I&amp;#x27;ve recently got my hands on a used &lt;a href="https://www.acer.com/gb-en/chromebooks/acer-chromebook-514-cb514-1h-cb514-1ht"&gt;Acer 514 Chromebook&lt;/a&gt;. As far as laptops go, this is a very underpowered computer with limited (4GB) ram, a nice keyboard and a great screen!&lt;/p&gt;

&lt;p&gt;Before going any further, I should probably explain a few things... As a webdev, I&amp;#x27;ve always prefered working on somewhat limited hardware (usually CPU). This is …&lt;/p&gt;</description><pubDate>Wed, 25 Sep 2024 00:00:00 +0000</pubDate><guid>https://localhost/articles/new-to-me-laptop.html</guid><category>Hardware</category><category>WebDev</category></item></channel></rss>