<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Design | The .NET Blog</title><link>https://thedotnetblog.com/tags/design/</link><description>Articles, tutorials and insights from the .NET community.</description><generator>Hugo</generator><language>en</language><managingEditor>@thedotnetblog (The .NET Blog)</managingEditor><webMaster>@thedotnetblog</webMaster><lastBuildDate>Fri, 20 Jun 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://thedotnetblog.com/tags/design/index.xml" rel="self" type="application/rss+xml"/><item><title>New Design: Dark Mode and a Minimal Theme</title><link>https://thedotnetblog.com/posts/emiliano-montesdeoca/new-design-dark-mode-and-minimal-theme/</link><pubDate>Fri, 20 Jun 2025 00:00:00 +0000</pubDate><author>Emiliano Montesdeoca</author><guid>https://thedotnetblog.com/posts/emiliano-montesdeoca/new-design-dark-mode-and-minimal-theme/</guid><description>The .NET Blog got a full visual refresh — a custom minimal dark theme built from scratch. Here's what changed and why.</description><content:encoded>&lt;p&gt;The blog has a new look.&lt;/p&gt;
&lt;p&gt;I spent a few weeks redesigning The .NET Blog from the ground up with a custom Hugo theme I&amp;rsquo;m calling &lt;code&gt;dotnet-minimal&lt;/code&gt;. It&amp;rsquo;s dark by default, fast to load, and designed to keep the focus on the writing.&lt;/p&gt;
&lt;h2 id="what-changed"&gt;What changed&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Dark mode as the default.&lt;/strong&gt; Not as an option, not as a toggle you have to find — dark by default, with a light mode toggle in the header for those who prefer it. Most developers I know have their editor in dark mode, their terminal in dark mode, their OS in dark mode. The blog should match.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Typography first.&lt;/strong&gt; The previous design had too much visual noise. The new one strips everything back to the content: a clear reading width, generous line height, and a font stack that respects the system.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Code blocks.&lt;/strong&gt; Syntax highlighting uses the Nord theme, which pairs well with the dark background. Line numbers are off by default — they add visual weight without much value for most posts.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Performance.&lt;/strong&gt; No JavaScript frameworks, no CSS-in-JS, no npm install required to edit the theme. The entire CSS is a single file. Page load times are in the sub-100ms range on the CDN.&lt;/p&gt;
&lt;h2 id="what-stayed-the-same"&gt;What stayed the same&lt;/h2&gt;
&lt;p&gt;The content structure didn&amp;rsquo;t change. Posts still live in Markdown files organised by author. The Hugo build pipeline is identical. If you were a contributor before, nothing in your workflow changed.&lt;/p&gt;
&lt;h2 id="the-typewriter-effect"&gt;The typewriter effect&lt;/h2&gt;
&lt;p&gt;The one bit of JavaScript on the home page is a small typewriter animation in the hero. It cycles through phrases like &amp;ldquo;share what they build.&amp;rdquo; and &amp;ldquo;build cloud-native apps.&amp;rdquo; It&amp;rsquo;s purely cosmetic and degrades gracefully if JS is disabled.&lt;/p&gt;
&lt;h2 id="open-source"&gt;Open source&lt;/h2&gt;
&lt;p&gt;The theme is part of the &lt;a href="https://github.com/thedotnetblog/blog"&gt;blog repository&lt;/a&gt; and is available under the MIT license. If you want to use it as a base for your own Hugo blog, go ahead.&lt;/p&gt;</content:encoded></item></channel></rss>