paritybit.ca

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

commit 6ad5adbed8cccb28a9963b3150806ee769a9a26e
parent e8579ab55c01afeea154fedf3b88956c09c2aa43
Author: Jake Bauer <jbauer@paritybit.ca>
Date:   Fri, 12 Jun 2020 18:36:49 -0400

Fix typo from blog post in RSS feed

Diffstat:
Mpublic/feeds/sitewide-feed.xml | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/public/feeds/sitewide-feed.xml b/public/feeds/sitewide-feed.xml @@ -16,7 +16,7 @@ <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>There were a few things in his article which caught my eye and made 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>