Fix some typos and publish the microfeatures post
Signed-off-by: Danila Fedorin <danila.fedorin@gmail.com>
This commit is contained in:
parent
6a7b6ffc1f
commit
b3db25c470
|
@ -1,7 +1,6 @@
|
||||||
---
|
---
|
||||||
title: "Microfeatures I Love in Blogs and Personal Websites"
|
title: "Microfeatures I Love in Blogs and Personal Websites"
|
||||||
date: 2024-06-23T11:03:10-07:00
|
date: 2024-06-23T11:03:10-07:00
|
||||||
draft: true
|
|
||||||
tags: ["Website"]
|
tags: ["Website"]
|
||||||
description: "In this post, I talk about pleasant but seemingly minor features in personal sites"
|
description: "In this post, I talk about pleasant but seemingly minor features in personal sites"
|
||||||
---
|
---
|
||||||
|
@ -21,14 +20,14 @@ I've been running a blog for a while --- some of the oldest posts I've found
|
||||||
and I've seen quite a few little things that are nice to use, but relatively
|
and I've seen quite a few little things that are nice to use, but relatively
|
||||||
easy to implement. They don't really make or break a website; the absence of
|
easy to implement. They don't really make or break a website; the absence of
|
||||||
such features might be noticed, but will not cause any disruption for the reader.
|
such features might be noticed, but will not cause any disruption for the reader.
|
||||||
On the other hand, their presence serves a QoL enhancement. I find these to be
|
On the other hand, their presence serves as a QoL enhancement. I find these to be
|
||||||
analogous to Hillel's notion of "microfeatures". If you're interested in adding
|
analogous to Hillel's notion of "microfeatures". If you're interested in adding
|
||||||
something to your site, consider browsing this menu to see if anything resonates!
|
something to your site, consider browsing this menu to see if anything resonates!
|
||||||
|
|
||||||
One last thing is that this post is not necessarily about microfeatures
|
One last thing is that this post is not necessarily about microfeatures
|
||||||
I'd like _every_ blog or personal website to have. Some ideas I present
|
I'd like _every_ blog or personal website to have. Some ideas I present
|
||||||
here are only well-suited to certain types of content and certain written
|
here are only well-suited to certain types of content and certain written
|
||||||
voices. They need not be applied indiscriminantly.
|
voices. They need not be applied indiscriminately.
|
||||||
|
|
||||||
With that, let's get started!
|
With that, let's get started!
|
||||||
|
|
||||||
|
@ -78,7 +77,7 @@ whose site will be mentioned plenty in this post anyway --- is [Faster than Lime
|
||||||
Take this post on [Rust's Futures](https://fasterthanli.me/articles/understanding-rust-futures-by-going-way-too-deep);
|
Take this post on [Rust's Futures](https://fasterthanli.me/articles/understanding-rust-futures-by-going-way-too-deep);
|
||||||
this is what the top of it looks like at the time of writing:
|
this is what the top of it looks like at the time of writing:
|
||||||
|
|
||||||
{{< figure src="fasterthanlime-toc.png" class="small" caption="A screenshot of the table of contents on Faster than Lime" alt="A screenshot of the table of contents on Faster than Lime. A box with the word \"Contents\" contains links to several sections on the page bellow (offscreen)" >}}
|
{{< figure src="fasterthanlime-toc.png" class="small" caption="A screenshot of the table of contents on Faster than Lime" alt="A screenshot of the table of contents on Faster than Lime. A box with the word \"Contents\" contains links to several sections on the page bellow (off screen)" >}}
|
||||||
|
|
||||||
The quality and value of TOCs certainly depends on the
|
The quality and value of TOCs certainly depends on the
|
||||||
sections within the page itself --- and whether or not the page has sections
|
sections within the page itself --- and whether or not the page has sections
|
||||||
|
@ -99,7 +98,7 @@ I also find this very nice, though it does miss out on headings within a page.
|
||||||
|
|
||||||
I've mentioned that tables of contents can communicate the structure of the
|
I've mentioned that tables of contents can communicate the structure of the
|
||||||
page. However, they do so from the outset, before you've started reading.
|
page. However, they do so from the outset, before you've started reading.
|
||||||
In their "base form", the reader stops beneffiting from tables of contents
|
In their "base form", the reader stops benefiting from tables of contents
|
||||||
{{< sidenote "right" "jump-top-note" "once they've started reading." >}}
|
{{< sidenote "right" "jump-top-note" "once they've started reading." >}}
|
||||||
That is, of course, unless they jump back to the top of the post and
|
That is, of course, unless they jump back to the top of the post and
|
||||||
find the table of contents again.
|
find the table of contents again.
|
||||||
|
@ -113,7 +112,7 @@ the [most recent article at the time of writing](https://www.quantamagazine.org/
|
||||||
|
|
||||||
{{< figure src="quanta-scroll.gif" class="fullwide" caption="The progress bar on a Quanta Magazine article" alt="The progress bar on a Quanta Magazine article. As the page scrolls, an orange bar at the top gradually fills up from left to right." >}}
|
{{< figure src="quanta-scroll.gif" class="fullwide" caption="The progress bar on a Quanta Magazine article" alt="The progress bar on a Quanta Magazine article. As the page scrolls, an orange bar at the top gradually fills up from left to right." >}}
|
||||||
|
|
||||||
One immediate thought is that this is completely superceded by the regular
|
One immediate thought is that this is completely superseded by the regular
|
||||||
browser scroll bar that's ever-present at the side of the page. However,
|
browser scroll bar that's ever-present at the side of the page. However,
|
||||||
the scroll bar could be deceiving. If your page has a comments section,
|
the scroll bar could be deceiving. If your page has a comments section,
|
||||||
the comments could make the page look dauntingly long. Similarly, references
|
the comments could make the page look dauntingly long. Similarly, references
|
||||||
|
@ -357,7 +356,7 @@ at the time of writing, I'm seeing the following footer:
|
||||||
{{< figure src="drew-openring.png" class="fullwide" caption="Links to other blogs from Drew DeVault's blog" alt="Links to other blogs from Drew DeVault's blog. The links consist of three side-by-side boxes, each with a title and brief excerpt." >}}
|
{{< figure src="drew-openring.png" class="fullwide" caption="Links to other blogs from Drew DeVault's blog" alt="Links to other blogs from Drew DeVault's blog. The links consist of three side-by-side boxes, each with a title and brief excerpt." >}}
|
||||||
|
|
||||||
As indicated in the image, Drew's site in particular uses a program
|
As indicated in the image, Drew's site in particular uses a program
|
||||||
called [openring](https://git.sr.ht/~sircmpwn/openring), which is based on
|
called [`openring`](https://git.sr.ht/~sircmpwn/openring), which is based on
|
||||||
RSS feeds (another [microfeature I love](#rss-feeds)). However,
|
RSS feeds (another [microfeature I love](#rss-feeds)). However,
|
||||||
_how_ the site finds such articles (statically like `openring`, or
|
_how_ the site finds such articles (statically like `openring`, or
|
||||||
on page load using some JavaScript) isn't hugely important to me. What's
|
on page load using some JavaScript) isn't hugely important to me. What's
|
||||||
|
|
Loading…
Reference in New Issue
Block a user