<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blogging on Matt Langford</title><link>https://mattlangford.com/tags/blogging/</link><description>Recent content in Blogging on Matt Langford</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 17 Jun 2026 13:35:52 -0500</lastBuildDate><atom:link href="https://mattlangford.com/tags/blogging/index.xml" rel="self" type="application/rss+xml"/><item><title>The Ever Evolving Blog</title><link>https://mattlangford.com/posts/the-ever-evolving-blog/</link><pubDate>Tue, 21 Oct 2025 00:00:00 -0500</pubDate><guid>https://mattlangford.com/posts/the-ever-evolving-blog/</guid><description>&lt;p&gt;I almost titled this post something along the lines of &lt;strong&gt;Rethinking the Rethinking of the Rethinking of My Blog&lt;/strong&gt;. Fortunately, common sense won out and that didn&amp;rsquo;t make the cut. But essentially that&amp;rsquo;s what this is. Let&amp;rsquo;s recap:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;I decided to move my personal blog &lt;a href="https://mattlangford.com/posts/making-my-blog-fully-my-own/"&gt;away from Micro.blog&lt;/a&gt;
.&lt;/li&gt;
&lt;li&gt;I chose Jekyll/Netlify as the destination.&lt;/li&gt;
&lt;li&gt;I made some &lt;a href="https://mattlangford.com/posts/rethinking-webmentions/"&gt;further tweaks&lt;/a&gt;
 to that setup.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;And now, I scrapped all of that and ended up on Bear.&lt;/p&gt;</description></item><item><title>Rethinking Webmentions</title><link>https://mattlangford.com/posts/rethinking-webmentions/</link><pubDate>Tue, 14 Oct 2025 00:00:00 -0500</pubDate><guid>https://mattlangford.com/posts/rethinking-webmentions/</guid><description>&lt;p&gt;In the transition to a new personal blog, I initially &lt;a href="https://mattlangford.com/posts/making-my-blog-fully-my-own/"&gt;wanted to fully incorporate webmentions&lt;/a&gt;
. I even designed and coded a &lt;em&gt;mostly&lt;/em&gt; custom setup that included a beautifully formatted facepile, replies list, and on and on.&lt;/p&gt;</description></item><item><title>Making My Blog Fully My Own</title><link>https://mattlangford.com/posts/making-my-blog-fully-my-own/</link><pubDate>Sun, 12 Oct 2025 00:00:00 -0500</pubDate><guid>https://mattlangford.com/posts/making-my-blog-fully-my-own/</guid><description>&lt;p&gt;Let me be clear from the start: I&amp;rsquo;m not leaving &lt;a href="https://micro.blog/mtt" rel="noopener noreferrer"&gt;Micro.blog&lt;/a&gt;
. In fact, I currently have more sites hosted on Micro.blog than not, including all my &lt;a href="https://mattlangford.com/posts/introducing-mythos-theme/"&gt;custom themes&lt;/a&gt;
 and documentation sites. Micro.blog is an excellent platform, and I continue to recommend it to anyone looking for a simple, community-focused blogging experience.&lt;/p&gt;
&lt;p&gt;But for my personal blog, I wanted something different. I wanted to dive deeper into the &lt;a href="https://indieweb.org" rel="noopener noreferrer"&gt;IndieWeb&lt;/a&gt;
 rabbit hole, gain more granular control over security implementations, and have the flexibility to experiment with web technologies in ways that a hosted platform doesn&amp;rsquo;t easily allow. This post details that transition, the reasoning behind it, the decisions I made, and the technical implementations that shaped this site.&lt;/p&gt;</description></item></channel></rss>