commit 76c14ed3f26adaaa0a567122266952eb6c7400ed
parent 83d1fc18edf39ee62d787c6fe424afa4ac7a8f6f
Author: Jake Bauer <jbauer@paritybit.ca>
Date: Fri, 12 Jun 2020 18:32:13 -0400
Publish new blog post
Diffstat:
5 files changed, 72 insertions(+), 2 deletions(-)
diff --git a/pages/blog.md b/pages/blog.md
@@ -20,6 +20,7 @@ href="https://social.paritybit.ca/@jbauer">Mastodon</a>.
### 2020
<ul>
+ <li>2020-06-12 <a href="blog/making-my-site-easier-to-read">Making My Site Easier to Read</a></li>
<li>2020-06-11 <a href="blog/improving-my-blog-post-publishing-script">Improving My Blog Post Publishing Script</a></li>
<li>2020-06-11 <a href="blog/trying-out-dwm">Trying Out dwm</a></li>
<li>2020-06-09 <a href="blog/setting-up-a-status-page">Setting Up a Status Page</a></li>
diff --git a/pages/blog/making-my-site-easier-to-read.md b/pages/blog/making-my-site-easier-to-read.md
@@ -0,0 +1,52 @@
+## Making My Site Easier to Read
+
+[//]: # "META_TEXT"
+
+[//]: # "main.min.css"
+
+[//]: #
+
+<div class="byline">
+<b>Written By:</b> Jake Bauer |
+ <b>Posted:</b> 2020-06-12 |
+ <b>Last Updated:</b> 2020-06-12
+</div>
+
+Kev Quirk recently posted an [article about improving his website's
+design](https://kevq.uk/whats-in-a-font-researching-website-typography/) which
+sparked me to review my own site's typography and design. During my [previous
+site redesign](https://www.paritybit.ca/blog/website-redesign), I tried to make
+sure that things were as readable as possible but it never hurts to review
+things. There may be something I like more now or something I missed the first
+time.
+
+There were a few things in his article which caught my eye and make me
+reconsider if I was doing all I could regarding typography. For one, I had my
+line height set at `1.4em` which I've lowered to `1.3em` and I also increased
+the spacing between paragraph headers and the paragraph above so that individual
+paragraphs or sections feel more like a single unit. This made text- and
+section-heavy pages like my [About This Site](/about-site) page much nicer to
+read.
+
+I also played around with different fonts and line widths, but nothing other
+than what I currently have looked good to me. I've also considered adding a
+light theme back to my website via a `@media` query because it's supposedly
+easier to read, but I originally got rid of it because I didn't like the look of
+the light theme that I had, despite my best efforts to tweak it. I do also
+personally prefer dark themes, so I think I'll just stick with what I have for
+now.
+
+There was one thing I disagree with Kev about: font sizes. I laid out my
+[thoughts regarding font
+sizes](https://www.paritybit.ca/blog/a-quick-rant-about-web-font-sizes) in a
+previous blog post, but to summarize: font sizes should not be specified in
+`px`, they should be specified using some relative measurement like `rem`s or
+`%`s.
+
+Other than that (😉), I think it's an excellent post and I hope it influences
+others to make their websites more readable. Thanks Kev!
+
+_This is my forty-third post for the
+[#100DaysToOffload](https://social.paritybit.ca/tags/100DaysToOffload)
+challenge. You can learn more about this challenge over at
+[https://100daystooffload.com](https://100daystooffload.com)._
diff --git a/pages/home.md b/pages/home.md
@@ -20,6 +20,8 @@ extent)! Access through `gopher://paritybit.ca` or `gemini://paritybit.ca`.
src="/img/feed-icon.png" width="15" height="15" alt="Click for RSS Feed"/>
</a>
</div>
+2020-06-12 <a class="feed-item" href="blog/making-my-site-easier-to-read">Making My Site Easier to Read</a>
+
2020-06-11 <a class="feed-item" href="blog/improving-my-blog-post-publishing-script">Improving My Blog Post Publishing Script</a>
2020-06-11 <a class="feed-item" href="blog/trying-out-dwm">Trying Out dwm</a>
@@ -37,8 +39,6 @@ extent)! Access through `gopher://paritybit.ca` or `gemini://paritybit.ca`.
2020-06-02 <a class="feed-item" href="blog/dnd-xp-system">My Custom XP System for DnD</a>
2020-05-31 <a class="feed-item" href="blog/it-doesnt-have-to-be-perfect">It Doesn't Have to Be Perfect</a>
-
-2020-05-29 <a class="feed-item" href="blog/book-review-the-mediocre-programmer">Book Review: The Mediocre Programmer</a>
### What is a Parity Bit?
It is a bit (in the 1's and 0's sense) used in checking for errors in digital
diff --git a/public/feeds/sitewide-feed.xml b/public/feeds/sitewide-feed.xml
@@ -7,6 +7,22 @@
<description>The feed that covers all notable additions, updates, announcements,
and other changes for the entire paritybit.ca website.</description>
<item>
+ <title>Making My Site Easier to Read</title>
+ <link>https://www.paritybit.ca/blog/making-my-site-easier-to-read</link>
+ <guid>https://www.paritybit.ca/blog/making-my-site-easier-to-read</guid>
+ <pubDate>Fri, 12 Jun 2020 18:32:02 -0400</pubDate>
+ <description><![CDATA[<h2 id="making-my-site-easier-to-read">Making My Site Easier to Read</h2>
+<div class="byline">
+<p><b>Written By:</b> Jake Bauer | <b>Posted:</b> 2020-06-12 | <b>Last Updated:</b> 2020-06-12</p>
+</div>
+<p>Kev Quirk recently posted an <a href="https://kevq.uk/whats-in-a-font-researching-website-typography/">article about improving his website’s design</a> which sparked me to review my own site’s typography and design. During my <a href="https://www.paritybit.ca/blog/website-redesign">previous site redesign</a>, I tried to make sure that things were as readable as possible but it never hurts to review things. There may be something I like more now or something I missed the first time.</p>
+<p>There were a few things in his article which caught my eye and make me reconsider if I was doing all I could regarding typography. For one, I had my line height set at <code>1.4em</code> which I’ve lowered to <code>1.3em</code> and I also increased the spacing between paragraph headers and the paragraph above so that individual paragraphs or sections feel more like a single unit. This made text- and section-heavy pages like my <a href="/about-site">About This Site</a> page much nicer to read.</p>
+<p>I also played around with different fonts and line widths, but nothing other than what I currently have looked good to me. I’ve also considered adding a light theme back to my website via a <code>@media</code> query because it’s supposedly easier to read, but I originally got rid of it because I didn’t like the look of the light theme that I had, despite my best efforts to tweak it. I do also personally prefer dark themes, so I think I’ll just stick with what I have for now.</p>
+<p>There was one thing I disagree with Kev about: font sizes. I laid out my <a href="https://www.paritybit.ca/blog/a-quick-rant-about-web-font-sizes">thoughts regarding font sizes</a> in a previous blog post, but to summarize: font sizes should not be specified in <code>px</code>, they should be specified using some relative measurement like <code>rem</code>s or <code>%</code>s.</p>
+<p>Other than that (😉), I think it’s an excellent post and I hope it influences others to make their websites more readable. Thanks Kev!</p>
+<p><em>This is my forty-third post for the <a href="https://social.paritybit.ca/tags/100DaysToOffload">#100DaysToOffload</a> challenge. You can learn more about this challenge over at <a href="https://100daystooffload.com" class="uri">https://100daystooffload.com</a>.</em></p>]]></description>
+ </item>
+<item>
<title>Improving My Blog Post Publishing Script</title>
<link>https://www.paritybit.ca/blog/improving-my-blog-post-publishing-script</link>
<guid>https://www.paritybit.ca/blog/improving-my-blog-post-publishing-script</guid>
diff --git a/public/sitemap.xml b/public/sitemap.xml
@@ -3,6 +3,7 @@
<url><loc>https://www.paritybit.ca</loc></url>
<url><loc>https://www.paritybit.ca/home</loc></url>
<url><loc>https://www.paritybit.ca/blog</loc></url>
+ <url><loc>https://www.paritybit.ca/blog/making-my-site-easier-to-read</loc></url>
<url><loc>https://www.paritybit.ca/blog/improving-my-blog-post-publishing-script</loc></url>
<url><loc>https://www.paritybit.ca/blog/trying-out-dwm</loc></url>
<url><loc>https://www.paritybit.ca/blog/setting-up-a-status-page</loc></url>
