Maybe. It wasn't a bad breakup, just some other factors made us take a step back. It felt like there's still a chance for something really good there. Guess not.

Welp, door closed on getting back together with my ex. That sucks. :(

Want to watch: I Survived “I Kissed Dating Goodbye”

Want to watch: The Heretic

One of my favorite albums from my youth is now on streaming. Steve Taylor, Squint:

https://open.spotify.com/album/36C7Gp34qvlQWtHJa9ORhl

Want to watch: Chicago: A Land of Wilderness and Oasis

This album is *so good*. Life-giving. Get on it. https://open.spotify.com/album/4Q2g4d99lyPAMXELy34sPI?si=SDIoJaCtQfqiD9gtb6IOog

https://twitter.com/WilliamMatt22/status/1060761947258314752

This is so good! Life-giving. Congratulations and thank you for making it.

It was great. Thank you for sharing it!

Want to read: The Enneagram: A Christian Perspective by Richard Rohr (ISBN 9780824519506)

I've been listening to @TheLiturgists for a while and loving it, so I'm looking forward to the Liturgists Gathering this weekend.

Want to read: Artemis by Andy Weir (ISBN 9780553448146)

Want to read: Rising Strong by Brené Brown (ISBN 9780812985801)

Want to read: The Alchemist by Paulo Coelho (ISBN 9780062315007)

Recommended by Isha

While working on my archives page, I decided to upgrade it to CSS Grid. I followed this tutorial and put together this rough mockup. I’m liking it so far.

This is still for articles only. I’m thinking about if/how to link my notes. I could use a series of notepad icons, but that got me wondering what the actual use-case is. With articles the title is shown so that might catch someone’s interest while scrolling the page. Who is going to be interested in clicking one of hundreds of notepad icons on the page, though, without any additional context?

@RELEVANTpodcast Loved hearing @EdwardorEddie on the show again, though was disappointed he didn’t get the outro audio clip.

Also am I missing it or did you not tweet about #658? I smell a @JesseCarey cover-up!

Another year is wrapping up (how?!), so time for my #indieweb #newwwyear resolutions for my website.

By 2019-01-01 I would like to:

• Update my archive pages to cover more post types, not just articles
• Add back the next/previous article navigation. I lost those as part of updates to the footer

As a stretch goal, I would like to work on my channels more. I would like to set up one to feed into my micro.blog that excludes replies to non-micro.blog posts. I would like to start treating micro.blog as my primary, external social network instead of Twitter.

Previously: 2017, 2016, 2015

I’ve experimented with a reply-chain like that a couple times, e.g. https://gregorlove.com/2017/12/finished-reading-a-wrinkle-in/

I think a read post primarily indicates an action related to reading it. “I want to read this,” “I am currently reading this,” or “I finished reading this.” I think any of those could include an optional comment. The Goodreads status update UI is a good example of this: you can update your reading progress and include a comment each time. Once you’ve marked a book as finished, you have a separate UI to enter a review and a rating, independent of your previous status updates and comments.

I think the general indieweb workflow for this would be several posts:

1. A read post with status to-read
2. read post(s) with status reading (one or more)
3. A read post with status finished
4. An h-review post

Personally I don't think updating existing posts is a great idea in this workflow, but I'm open to ideas. These are my suggestions based on experience with Goodreads.

During tonight’s Homebrew Website Club Online I finished off some improvements to my CSS. I updated responses on my articles and notes to use CSS Grid.

This isn’t a visually stunning update — in fact they look almost exactly the same — but I was able to simplify the HTML quite a bit. Previously, I was using some conditionals in the templates to show different HTML+CSS class names in order vertically center “one-line” responses like “John Doe mentioned this.” Using CSS Grid with Flexbox as a fallback made the HTML and CSS more straightforward. I am looking forward to doing more with CSS Grid. I hope to get to the point I can remove the Skeleton CSS framework.

I also split out sections for RSPVs and Other Responses on my event posts.