note to self: never push while half asleep

Signed-off-by: wl <zayd@disroot.org>

_zola/config.toml

@@ -19,6 +19,7 @@ title = "wanderlost"
 # Whether to do syntax highlighting
 # Theme can be customised by setting the `highlight_theme` variable to a theme supported by Zola
 highlight_code = true
+highlight_theme = "one-dark"
 
 [link_checker]
 skip_prefixes = []

_zola/content/2025-04-13-xhtml-is-good-actually.md

@@ -0,0 +1,53 @@
++++
+title = "XHTML is good, actually"
+date = 2025-04-13
+description = "In defense of a needlessly controversial document standard"
++++
+About a month or two ago, I finally converted everything I run and currently maintain to XHTML 1.1.
+I had been considering it for months and finally decided it was the right decision, and came to the
+conclusion that XHTML is far better than HTML.
+
+# An open web needs real standards
+Unlike the SGML-based HTML, documents in XHTML must be valid. Browsers will let you get away with
+some mild errors, but it's far less lenient than normal HTML. While this is one of the most common
+things people criticize XHTML for, it's a good thing. Had everyone used XHTML and followed its
+standards when it first came out, maybe we wouldn't have the browser monopoly we have today, or at
+least not to such a severe extent. The web needs well-formed XML documents, not the sloppily thrown
+together garbage HTML allows and borderline encourages. At the start, XHTML was designed with the
+intention of fixing this, but many people kept clinging onto their shitty documents. Now so many
+pages are still so annoying to parse that only a couple companies actually do it. XHTML could've
+helped fix this.
+
+XHTML tags must be properly closed, so it will not let you use `<br>` instead of `<br />`. XHTML
+will not let you uppercase your elements and attributes, so you can't `<IMG SRC=`. XHTML will not
+let you mess up nesting (even though some browsers will), so you can't (or at least shouldn't) do
+the following:
+```xhtml
+<p>
+	Here's a list of some things
+	<ul>
+		<li>Item</li>
+		<li>Item</li>
+	</ul>
+</p>
+```
+
+As much as people like to make fun of this, it's a positive to have well formed documents be
+enforced.
+
+# Your own sanity
+XHTML forcing documents to be well formed isn't only good for maintaining a true standard, it also
+helps you, the author. By requiring everything be valid, it strongly discourages poor formatting,
+leaving it easier for you to maintain your site and edit in the future. Using XHTML puts you in
+better habits for writing sites and it's yet another reason why its strictness is a good thing.
+
+# Negatives
+As XHTML is an older standard (the oldest full release being the second edition of XHTML 1.1
+in late 2010), it misses out on some newer features HTML5 and others brought in. It doesn't have
+`<summary>` or `<details>`, it doesn't have semantic elements like `<main>` (though I don't
+really think this matters as much), and it doesn't have inline SVG. I don't think any of these
+are really an absolute necessity, but the `<summary>`/`<details`> tags would be pretty nice.
+
+# Further reading
+This will be expanded if/when I find more relevant articles.
+- [https://web.archive.org/web/20250405011146/https://www.nuegia.net/articles/open%20letter%20to%20webmasters.xhtml](https://web.archive.org/web/20250405011146/https://www.nuegia.net/articles/open%20letter%20to%20webmasters.xhtml)

_zola/templates/page.html

@@ -8,7 +8,8 @@
 <div class="post">
 	<h1 class="post-title">{{ page.title }}</h1>
 	<h2 class="post-date">{{ page.date | date(format="%Y-%m-%d") }}</h2>
-	{{ page.content | replace(from="%5B", to="[") | replace(from="%5D", to="]") | safe }}
+	<!-- if Zola just generated compliant XHTML on its own that would be great, but looks like this will have to do -->
+	{{ page.content | replace(from="%5B", to="[") | replace(from="%5D", to="]") | replace(from=' data-lang="xhtml"', to="") | safe }}
 </div>
 
 {% endblock content %}

_zola/theme.toml

@@ -3,6 +3,6 @@ description = "man I just want a custom theme"
 
 tags = []						# wtf is this for
 license = "GPLv3"
-homepage = "https://goatse.cx"
+homepage = "https://none.null"
 min_version = "0.4.0"
 demo = ""

assets/css/main.css

@@ -120,3 +120,8 @@ a:hover {
     color: white;
 	font-size: 15px;
 }
+
+code {
+	font-family: FiraCode;
+	color: #8470ff;
+}

blog/2025-01-24-new-blog/index.xhtml

@@ -35,6 +35,7 @@
 <div class="post">
 	<h1 class="post-title">Zaydsite now</h1>
 	<h2 class="post-date">2025-01-24</h2>
+	<!-- if Zola just generated compliant XHTML on its own that would be great, but looks like this will have to do -->
 	<p>Recently got everything working on the new site, hopefully it doesn't look too boring. I plan to
 actually use this thing and not leave it to rot, so subscribe to the Atom feed if you want to get
 updates on the shit I say.</p>

blog/2025-02-04-servers-up/index.xhtml

@@ -35,6 +35,7 @@
 <div class="post">
 	<h1 class="post-title">Server up</h1>
 	<h2 class="post-date">2025-02-04</h2>
+	<!-- if Zola just generated compliant XHTML on its own that would be great, but looks like this will have to do -->
 	<p>After waiting way too long, I finally have a server online. Nothing big, just a RPi 5 running
 Alpine to provide some services for myself and other. I'm trying to focus on hosting sites
 built to be minimal, without the bloat much of the modern web has. It also exclusively serves

blog/2025-03-24-the-internet-sucks/index.xhtml

@@ -35,6 +35,7 @@
 <div class="post">
 	<h1 class="post-title">The Internet Sucks</h1>
 	<h2 class="post-date">2025-03-24</h2>
+	<!-- if Zola just generated compliant XHTML on its own that would be great, but looks like this will have to do -->
 	<p>Over the past few years, I have noticed that the internet is in a state of decay. If you've found my
 site, there's a fair chance you think the same too, or have at least heard people say this. The
 amount of fun one can really have online is rapidly decreasing. Everything has pretty much been

blog/2025-04-13-xhtml-is-good-actually/index.xhtml

@@ -0,0 +1,88 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
+		  "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+	<head>
+		<meta http-equiv="X-UA-Compatible" content="IE=edge" />
+		<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+		<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1, viewport-fit=cover" />
+		
+<title>wanderlost - XHTML is good, actually</title>
+
+		<link rel="stylesheet" href="/assets/css/main.css" />
+
+		
+        <link rel="alternate"
+			  type="application/rss+xml"
+			  title="Atom"
+			  href="/blog/atom.xml" />
+        <link rel="alternate"
+			  type="application/rss+xml"
+			  title="RSS"
+			  href="/blog/rss.xml" />
+		
+	</head>
+	<body>
+		<div class="navbar">
+			<h1 class="title"><a href="/">wanderlost</a></h1>
+			<a href="/blog/">index</a>
+			<a href="/blog/atom.xml">atom</a>
+			<a href="/blog/rss.xml">rss</a>
+		</div>
+		<div class="main">
+			<hr />
+			
+<div class="post">
+	<h1 class="post-title">XHTML is good, actually</h1>
+	<h2 class="post-date">2025-04-13</h2>
+	<!-- if Zola just generated compliant XHTML on its own that would be great, but looks like this will have to do -->
+	<p>About a month or two ago, I finally converted everything I run and currently maintain to XHTML 1.1.
+I had been considering it for months and finally decided it was the right decision, and came to the
+conclusion that XHTML is far better than HTML.</p>
+<h1 id="an-open-web-needs-real-standards">An open web needs real standards</h1>
+<p>Unlike the SGML-based HTML, documents in XHTML must be valid. Browsers will let you get away with
+some mild errors, but it's far less lenient than normal HTML. While this is one of the most common
+things people criticize XHTML for, it's a good thing. Had everyone used XHTML and followed its
+standards when it first came out, maybe we wouldn't have the browser monopoly we have today, or at
+least not to such a severe extent. The web needs well-formed XML documents, not the sloppily thrown
+together garbage HTML allows and borderline encourages. At the start, XHTML was designed with the
+intention of fixing this, but many people kept clinging onto their shitty documents. Now so many
+pages are still so annoying to parse that only a couple companies actually do it. XHTML could've
+helped fix this.</p>
+<p>XHTML tags must be properly closed, so it will not let you use <code>&lt;br&gt;</code> instead of <code>&lt;br /&gt;</code>. XHTML
+will not let you uppercase your elements and attributes, so you can't <code>&lt;IMG SRC=</code>. XHTML will not
+let you mess up nesting (even though some browsers will), so you can't (or at least shouldn't) do
+the following:</p>
+<pre style="background-color:#2b303b;color:#6c7079;" class="language-xhtml "><code class="language-xhtml"><span style="color:#abb2bf;">&lt;</span><span style="color:#eb6772;">p</span><span style="color:#abb2bf;">&gt;
+</span><span style="color:#abb2bf;">	Here&#39;s a list of some things
+</span><span style="color:#abb2bf;">	&lt;</span><span style="color:#eb6772;">ul</span><span style="color:#abb2bf;">&gt;
+</span><span style="color:#abb2bf;">		&lt;</span><span style="color:#eb6772;">li</span><span style="color:#abb2bf;">&gt;Item&lt;/</span><span style="color:#eb6772;">li</span><span style="color:#abb2bf;">&gt;
+</span><span style="color:#abb2bf;">		&lt;</span><span style="color:#eb6772;">li</span><span style="color:#abb2bf;">&gt;Item&lt;/</span><span style="color:#eb6772;">li</span><span style="color:#abb2bf;">&gt;
+</span><span style="color:#abb2bf;">	&lt;/</span><span style="color:#eb6772;">ul</span><span style="color:#abb2bf;">&gt;
+</span><span style="color:#abb2bf;">&lt;/</span><span style="color:#eb6772;">p</span><span style="color:#abb2bf;">&gt;
+</span></code></pre>
+<p>As much as people like to make fun of this, it's a positive to have well formed documents be
+enforced.</p>
+<h1 id="your-own-sanity">Your own sanity</h1>
+<p>XHTML forcing documents to be well formed isn't only good for maintaining a true standard, it also
+helps you, the author. By requiring everything be valid, it strongly discourages poor formatting,
+leaving it easier for you to maintain your site and edit in the future. Using XHTML puts you in
+better habits for writing sites and it's yet another reason why its strictness is a good thing.</p>
+<h1 id="negatives">Negatives</h1>
+<p>As XHTML is an older standard (the oldest full release being the second edition of XHTML 1.1
+in late 2010), it misses out on some newer features HTML5 and others brought in. It doesn't have
+<code>&lt;summary&gt;</code> or <code>&lt;details&gt;</code>, it doesn't have semantic elements like <code>&lt;main&gt;</code> (though I don't
+really think this matters as much), and it doesn't have inline SVG. I don't think any of these
+are really an absolute necessity, but the <code>&lt;summary&gt;</code>/<code>&lt;details</code>&gt; tags would be pretty nice.</p>
+<h1 id="further-reading">Further reading</h1>
+<p>This will be expanded if/when I find more relevant articles.</p>
+<ul>
+<li><a href="https://web.archive.org/web/20250405011146/https://www.nuegia.net/articles/open%20letter%20to%20webmasters.xhtml">https://web.archive.org/web/20250405011146/https://www.nuegia.net/articles/open%20letter%20to%20webmasters.xhtml</a></li>
+</ul>
+
+</div>
+
+
+		</div>
+	</body>
+</html>

blog/atom.xml

@@ -4,8 +4,70 @@
     <link rel="self" type="application/atom+xml" href="/blog/atom.xml"/>
     <link rel="alternate" type="text/html" href="/blog"/>
     <generator uri="https://www.getzola.org/">Zola</generator>
-    <updated>2025-03-24T00:00:00+00:00</updated>
+    <updated>2025-04-13T00:00:00+00:00</updated>
     <id>/blog/atom.xml</id>
+    <entry xml:lang="en">
+        <title>XHTML is good, actually</title>
+        <published>2025-04-13T00:00:00+00:00</published>
+        <updated>2025-04-13T00:00:00+00:00</updated>
+        
+        <author>
+          <name>
+            
+              wanderlost
+            
+          </name>
+        </author>
+        
+        <link rel="alternate" type="text/html" href="/blog/2025-04-13-xhtml-is-good-actually/"/>
+        <id>/blog/2025-04-13-xhtml-is-good-actually/</id>
+        
+        <content type="html" xml:base="/blog/2025-04-13-xhtml-is-good-actually/">&lt;p&gt;About a month or two ago, I finally converted everything I run and currently maintain to XHTML 1.1.
+I had been considering it for months and finally decided it was the right decision, and came to the
+conclusion that XHTML is far better than HTML.&lt;&#x2F;p&gt;
+&lt;h1 id=&quot;an-open-web-needs-real-standards&quot;&gt;An open web needs real standards&lt;&#x2F;h1&gt;
+&lt;p&gt;Unlike the SGML-based HTML, documents in XHTML must be valid. Browsers will let you get away with
+some mild errors, but it&#x27;s far less lenient than normal HTML. While this is one of the most common
+things people criticize XHTML for, it&#x27;s a good thing. Had everyone used XHTML and followed its
+standards when it first came out, maybe we wouldn&#x27;t have the browser monopoly we have today, or at
+least not to such a severe extent. The web needs well-formed XML documents, not the sloppily thrown
+together garbage HTML allows and borderline encourages. At the start, XHTML was designed with the
+intention of fixing this, but many people kept clinging onto their shitty documents. Now so many
+pages are still so annoying to parse that only a couple companies actually do it. XHTML could&#x27;ve
+helped fix this.&lt;&#x2F;p&gt;
+&lt;p&gt;XHTML tags must be properly closed, so it will not let you use &lt;code&gt;&amp;lt;br&amp;gt;&lt;&#x2F;code&gt; instead of &lt;code&gt;&amp;lt;br &#x2F;&amp;gt;&lt;&#x2F;code&gt;. XHTML
+will not let you uppercase your elements and attributes, so you can&#x27;t &lt;code&gt;&amp;lt;IMG SRC=&lt;&#x2F;code&gt;. XHTML will not
+let you mess up nesting (even though some browsers will), so you can&#x27;t (or at least shouldn&#x27;t) do
+the following:&lt;&#x2F;p&gt;
+&lt;pre data-lang=&quot;xhtml&quot; style=&quot;background-color:#2b303b;color:#6c7079;&quot; class=&quot;language-xhtml &quot;&gt;&lt;code class=&quot;language-xhtml&quot; data-lang=&quot;xhtml&quot;&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;&amp;lt;&lt;&#x2F;span&gt;&lt;span style=&quot;color:#eb6772;&quot;&gt;p&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;&amp;gt;
+&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;	Here&amp;#39;s a list of some things
+&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;	&amp;lt;&lt;&#x2F;span&gt;&lt;span style=&quot;color:#eb6772;&quot;&gt;ul&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;&amp;gt;
+&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;		&amp;lt;&lt;&#x2F;span&gt;&lt;span style=&quot;color:#eb6772;&quot;&gt;li&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;&amp;gt;Item&amp;lt;&#x2F;&lt;&#x2F;span&gt;&lt;span style=&quot;color:#eb6772;&quot;&gt;li&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;&amp;gt;
+&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;		&amp;lt;&lt;&#x2F;span&gt;&lt;span style=&quot;color:#eb6772;&quot;&gt;li&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;&amp;gt;Item&amp;lt;&#x2F;&lt;&#x2F;span&gt;&lt;span style=&quot;color:#eb6772;&quot;&gt;li&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;&amp;gt;
+&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;	&amp;lt;&#x2F;&lt;&#x2F;span&gt;&lt;span style=&quot;color:#eb6772;&quot;&gt;ul&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;&amp;gt;
+&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;&amp;lt;&#x2F;&lt;&#x2F;span&gt;&lt;span style=&quot;color:#eb6772;&quot;&gt;p&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;&amp;gt;
+&lt;&#x2F;span&gt;&lt;&#x2F;code&gt;&lt;&#x2F;pre&gt;
+&lt;p&gt;As much as people like to make fun of this, it&#x27;s a positive to have well formed documents be
+enforced.&lt;&#x2F;p&gt;
+&lt;h1 id=&quot;your-own-sanity&quot;&gt;Your own sanity&lt;&#x2F;h1&gt;
+&lt;p&gt;XHTML forcing documents to be well formed isn&#x27;t only good for maintaining a true standard, it also
+helps you, the author. By requiring everything be valid, it strongly discourages poor formatting,
+leaving it easier for you to maintain your site and edit in the future. Using XHTML puts you in
+better habits for writing sites and it&#x27;s yet another reason why its strictness is a good thing.&lt;&#x2F;p&gt;
+&lt;h1 id=&quot;negatives&quot;&gt;Negatives&lt;&#x2F;h1&gt;
+&lt;p&gt;As XHTML is an older standard (the oldest full release being the second edition of XHTML 1.1
+in late 2010), it misses out on some newer features HTML5 and others brought in. It doesn&#x27;t have
+&lt;code&gt;&amp;lt;summary&amp;gt;&lt;&#x2F;code&gt; or &lt;code&gt;&amp;lt;details&amp;gt;&lt;&#x2F;code&gt;, it doesn&#x27;t have semantic elements like &lt;code&gt;&amp;lt;main&amp;gt;&lt;&#x2F;code&gt; (though I don&#x27;t
+really think this matters as much), and it doesn&#x27;t have inline SVG. I don&#x27;t think any of these
+are really an absolute necessity, but the &lt;code&gt;&amp;lt;summary&amp;gt;&lt;&#x2F;code&gt;&#x2F;&lt;code&gt;&amp;lt;details&lt;&#x2F;code&gt;&amp;gt; tags would be pretty nice.&lt;&#x2F;p&gt;
+&lt;h1 id=&quot;further-reading&quot;&gt;Further reading&lt;&#x2F;h1&gt;
+&lt;p&gt;This will be expanded if&#x2F;when I find more relevant articles.&lt;&#x2F;p&gt;
+&lt;ul&gt;
+&lt;li&gt;&lt;a href=&quot;https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20250405011146&#x2F;https:&#x2F;&#x2F;www.nuegia.net&#x2F;articles&#x2F;open%20letter%20to%20webmasters.xhtml&quot;&gt;https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20250405011146&#x2F;https:&#x2F;&#x2F;www.nuegia.net&#x2F;articles&#x2F;open%20letter%20to%20webmasters.xhtml&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
+&lt;&#x2F;ul&gt;
+</content>
+        
+    </entry>
     <entry xml:lang="en">
         <title>The Internet Sucks</title>
         <published>2025-03-24T00:00:00+00:00</published>

blog/index.xhtml

@@ -34,6 +34,14 @@
 			
 			<div class="posts">
 				
+				<h3 class="post-title">
+					2025-04-13 -
+                    <a href="/blog/2025-04-13-xhtml-is-good-actually/">
+						XHTML is good, actually
+                    </a>
+                </h3>
+				<p>In defense of a needlessly controversial document standard</p>
+                
 				<h3 class="post-title">
 					2025-03-24 -
                     <a href="/blog/2025-03-24-the-internet-sucks/">

blog/rss.xml

@@ -7,7 +7,58 @@
       <generator>Zola</generator>
       <language>en</language>
       <atom:link href="/blog/rss.xml" rel="self" type="application/rss+xml"/>
-      <lastBuildDate>Mon, 24 Mar 2025 00:00:00 +0000</lastBuildDate>
+      <lastBuildDate>Sun, 13 Apr 2025 00:00:00 +0000</lastBuildDate>
+      <item>
+          <title>XHTML is good, actually</title>
+          <pubDate>Sun, 13 Apr 2025 00:00:00 +0000</pubDate>
+          <author>wanderlost</author>
+          <link>/blog/2025-04-13-xhtml-is-good-actually/</link>
+          <guid>/blog/2025-04-13-xhtml-is-good-actually/</guid>
+          <description xml:base="/blog/2025-04-13-xhtml-is-good-actually/">&lt;p&gt;About a month or two ago, I finally converted everything I run and currently maintain to XHTML 1.1.
+I had been considering it for months and finally decided it was the right decision, and came to the
+conclusion that XHTML is far better than HTML.&lt;&#x2F;p&gt;
+&lt;h1 id=&quot;an-open-web-needs-real-standards&quot;&gt;An open web needs real standards&lt;&#x2F;h1&gt;
+&lt;p&gt;Unlike the SGML-based HTML, documents in XHTML must be valid. Browsers will let you get away with
+some mild errors, but it&#x27;s far less lenient than normal HTML. While this is one of the most common
+things people criticize XHTML for, it&#x27;s a good thing. Had everyone used XHTML and followed its
+standards when it first came out, maybe we wouldn&#x27;t have the browser monopoly we have today, or at
+least not to such a severe extent. The web needs well-formed XML documents, not the sloppily thrown
+together garbage HTML allows and borderline encourages. At the start, XHTML was designed with the
+intention of fixing this, but many people kept clinging onto their shitty documents. Now so many
+pages are still so annoying to parse that only a couple companies actually do it. XHTML could&#x27;ve
+helped fix this.&lt;&#x2F;p&gt;
+&lt;p&gt;XHTML tags must be properly closed, so it will not let you use &lt;code&gt;&amp;lt;br&amp;gt;&lt;&#x2F;code&gt; instead of &lt;code&gt;&amp;lt;br &#x2F;&amp;gt;&lt;&#x2F;code&gt;. XHTML
+will not let you uppercase your elements and attributes, so you can&#x27;t &lt;code&gt;&amp;lt;IMG SRC=&lt;&#x2F;code&gt;. XHTML will not
+let you mess up nesting (even though some browsers will), so you can&#x27;t (or at least shouldn&#x27;t) do
+the following:&lt;&#x2F;p&gt;
+&lt;pre data-lang=&quot;xhtml&quot; style=&quot;background-color:#2b303b;color:#6c7079;&quot; class=&quot;language-xhtml &quot;&gt;&lt;code class=&quot;language-xhtml&quot; data-lang=&quot;xhtml&quot;&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;&amp;lt;&lt;&#x2F;span&gt;&lt;span style=&quot;color:#eb6772;&quot;&gt;p&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;&amp;gt;
+&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;	Here&amp;#39;s a list of some things
+&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;	&amp;lt;&lt;&#x2F;span&gt;&lt;span style=&quot;color:#eb6772;&quot;&gt;ul&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;&amp;gt;
+&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;		&amp;lt;&lt;&#x2F;span&gt;&lt;span style=&quot;color:#eb6772;&quot;&gt;li&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;&amp;gt;Item&amp;lt;&#x2F;&lt;&#x2F;span&gt;&lt;span style=&quot;color:#eb6772;&quot;&gt;li&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;&amp;gt;
+&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;		&amp;lt;&lt;&#x2F;span&gt;&lt;span style=&quot;color:#eb6772;&quot;&gt;li&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;&amp;gt;Item&amp;lt;&#x2F;&lt;&#x2F;span&gt;&lt;span style=&quot;color:#eb6772;&quot;&gt;li&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;&amp;gt;
+&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;	&amp;lt;&#x2F;&lt;&#x2F;span&gt;&lt;span style=&quot;color:#eb6772;&quot;&gt;ul&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;&amp;gt;
+&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;&amp;lt;&#x2F;&lt;&#x2F;span&gt;&lt;span style=&quot;color:#eb6772;&quot;&gt;p&lt;&#x2F;span&gt;&lt;span style=&quot;color:#abb2bf;&quot;&gt;&amp;gt;
+&lt;&#x2F;span&gt;&lt;&#x2F;code&gt;&lt;&#x2F;pre&gt;
+&lt;p&gt;As much as people like to make fun of this, it&#x27;s a positive to have well formed documents be
+enforced.&lt;&#x2F;p&gt;
+&lt;h1 id=&quot;your-own-sanity&quot;&gt;Your own sanity&lt;&#x2F;h1&gt;
+&lt;p&gt;XHTML forcing documents to be well formed isn&#x27;t only good for maintaining a true standard, it also
+helps you, the author. By requiring everything be valid, it strongly discourages poor formatting,
+leaving it easier for you to maintain your site and edit in the future. Using XHTML puts you in
+better habits for writing sites and it&#x27;s yet another reason why its strictness is a good thing.&lt;&#x2F;p&gt;
+&lt;h1 id=&quot;negatives&quot;&gt;Negatives&lt;&#x2F;h1&gt;
+&lt;p&gt;As XHTML is an older standard (the oldest full release being the second edition of XHTML 1.1
+in late 2010), it misses out on some newer features HTML5 and others brought in. It doesn&#x27;t have
+&lt;code&gt;&amp;lt;summary&amp;gt;&lt;&#x2F;code&gt; or &lt;code&gt;&amp;lt;details&amp;gt;&lt;&#x2F;code&gt;, it doesn&#x27;t have semantic elements like &lt;code&gt;&amp;lt;main&amp;gt;&lt;&#x2F;code&gt; (though I don&#x27;t
+really think this matters as much), and it doesn&#x27;t have inline SVG. I don&#x27;t think any of these
+are really an absolute necessity, but the &lt;code&gt;&amp;lt;summary&amp;gt;&lt;&#x2F;code&gt;&#x2F;&lt;code&gt;&amp;lt;details&lt;&#x2F;code&gt;&amp;gt; tags would be pretty nice.&lt;&#x2F;p&gt;
+&lt;h1 id=&quot;further-reading&quot;&gt;Further reading&lt;&#x2F;h1&gt;
+&lt;p&gt;This will be expanded if&#x2F;when I find more relevant articles.&lt;&#x2F;p&gt;
+&lt;ul&gt;
+&lt;li&gt;&lt;a href=&quot;https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20250405011146&#x2F;https:&#x2F;&#x2F;www.nuegia.net&#x2F;articles&#x2F;open%20letter%20to%20webmasters.xhtml&quot;&gt;https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20250405011146&#x2F;https:&#x2F;&#x2F;www.nuegia.net&#x2F;articles&#x2F;open%20letter%20to%20webmasters.xhtml&lt;&#x2F;a&gt;&lt;&#x2F;li&gt;
+&lt;&#x2F;ul&gt;
+</description>
+      </item>
       <item>
           <title>The Internet Sucks</title>
           <pubDate>Mon, 24 Mar 2025 00:00:00 +0000</pubDate>

blog/sitemap.xml

@@ -15,4 +15,8 @@
         <loc>/blog/2025-03-24-the-internet-sucks/</loc>
         <lastmod>2025-03-24</lastmod>
     </url>
+    <url>
+        <loc>/blog/2025-04-13-xhtml-is-good-actually/</loc>
+        <lastmod>2025-04-13</lastmod>
+    </url>
 </urlset>

index.xhtml

@@ -10,9 +10,9 @@
 	<body>
 		<div class="navbar">
 			<h1 class="title"><a href="/">wanderlost</a></h1>
-			<a href="/links.xht">links</a>
+			<a href="/links.xhtml">links</a>
 			<a href="/blog/">blog</a>
-			<a href="/mirrors.xht">mirrors</a>
+			<a href="/mirrors.xhtml">mirrors</a>
 		</div>
 		<div class="main">
 			<hr />
@@ -39,7 +39,7 @@
 		</div>
 		<div class="footer">
 			<img src="/assets/svg/kopimi.svg" alt="" style="vertical-align: middle; width: 15px" />
-			<a href="/kopimi.xht">Kopimi</a> 2025
+			<a href="/kopimi.xhtml">Kopimi</a> 2025
 		</div>
 	</body>
 </html>

kopimi.xhtml

@@ -10,9 +10,9 @@
 	<body>
 		<div class="navbar">
 			<h1 class="title"><a href="/">wanderlost</a></h1>
-			<a href="/links.xht">links</a>
+			<a href="/links.xhtml">links</a>
 			<a href="/blog/">blog</a>
-			<a href="/mirrors.xht">mirrors</a>
+			<a href="/mirrors.xhtml">mirrors</a>
 		</div>
 		<div class="main">
 			<hr />
@@ -25,7 +25,7 @@
 		</div>
 		<div class="footer">
 			<img src="/assets/svg/kopimi.svg" alt="" style="vertical-align: middle; width: 15px" />
-			<a href="/kopimi.xht">Kopimi</a> 2025
+			<a href="/kopimi.xhtml">Kopimi</a> 2025
 		</div>
 	</body>
 </html>

links.xhtml

@@ -11,9 +11,9 @@
 		<div class="header">
 			<div class="navbar">
 				<h1 class="title"><a href="/">wanderlost</a></h1>
-				<a href="/links.xht">links</a>
+				<a href="/links.xhtml">links</a>
 				<a href="/blog/">blog</a>
-				<a href="/mirrors.xht">mirrors</a>
+				<a href="/mirrors.xhtml">mirrors</a>
 			</div>
 		</div>
 		<div class="main">
@@ -174,7 +174,7 @@
 		</div>
 		<div class="footer">
 			<img src="/assets/svg/kopimi.svg" width="15px" alt="" style="vertical-align: middle" />
-			<a href="/kopimi.xht">Kopimi</a> 2025
+			<a href="/kopimi.xhtml">Kopimi</a> 2025
 		</div>
 	</body>
 </html>

mirrors.xhtml

@@ -10,9 +10,9 @@
 	<body>
 		<div class="navbar">
 			<h1 class="title"><a href="/">wanderlost</a></h1>
-			<a href="/links.xht">links</a>
+			<a href="/links.xhtml">links</a>
 			<a href="/blog/">blog</a>
-			<a href="/mirrors.xht">mirrors</a>
+			<a href="/mirrors.xhtml">mirrors</a>
 		</div>
 		<div class="main">
 			<hr />
@@ -28,7 +28,7 @@
 		</div>
 		<div class="footer">
 			<img src="/assets/svg/kopimi.svg" alt="" style="vertical-align: middle; width: 15px" />
-			<a href="/kopimi.xht">Kopimi</a> 2025
+			<a href="/kopimi.xhtml">Kopimi</a> 2025
 		</div>
 	</body>
 </html>