#dev 2024-07-16

2024-07-16 UTC
barnaby, thegreekgeek, thegreekgeek_, [snarfed], solislupus[d], Zegnat, oenone, gRegor, gRegorLove_, GuestZero, gRegorLove__, [Murray], Star, benji, Zic, GuestZero_, [contact898], [KevinMarks], eitilt, eitilt1, [pfefferle], StarrWulfe, [Joe_Crawford], joshproehl and [jacky] joined the channel
#
[jacky]
call to action for anyone wanting to do something _bold_: https://mastodon.social/@sarahjamielewis/112797152700861866
GuestZero joined the channel
#
Loqi
[preview] [Sarah Jamie Lewis] I think probably the best place to start would be to build a rendering engine that can support basic rss/atom feeds and a bare bones micropub client. i.e. something minimally useful that covers both creation and consumption. Soon after that you wou...
gRegorLove_, Zic, [schmarty], jonnybarnes, wagle and StarrWul1 joined the channel
#
timeissuspect
I'm getting increasingly disturbed by the accepted wisdom that a blog is a time sequenced object, and your latest content is at the top.
#
timeissuspect
A lot of my posts on money have got nothing to do with today's date, and the order in which I created them is certainly not the order to read them in.
#
timeissuspect
The thing that will break is articles where I have cross linked to those scheduled posts, those links will break until the series is fully published again
#
IWDiscord
<t​imeissuspect>
#
timeissuspect
So I'm going to experiment with taking a selection, putting a future scheduled date (one post per day) and release a series on one topic. That means my RSS subsribers will get something each day that connects to the previous day, as will visitors to the website.
#
IWDiscord
<t​imeissuspect>
#
IWDiscord
<t​imeissuspect>
#
timeissuspect
This is "recycling content" which might be frowned upon in purist circles
eitilt and [aciccarello] joined the channel
#
[aciccarello]
I think it is fair to question the date based timeline model if your content doesn't fit that well
#
[aciccarello]
Humans do have a recency bias though.
Jah joined the channel
#
timeissuspect
that's true, but I don't put dates on my blog posts anyway. It may be that someone read an article I created three months ago and sees it again in their feed and feels aggrieved. I don't have that many subscribers anyway and most readers will not have read the back catalogue.
#
timeissuspect
I'll give it a go and see what happens. Republishing old content within a current context is much easier that trying to think of something new to write.
#
IWDiscord
<t​imeissuspect>
#
[Joe_Crawford]
A lot of the time bias was about how the earliest blogging tools worked and how things got divided up as time passed. Archive pages of lots of posts with full content (or just an excerpt), often by month, or individual pages. URL structure seems like this small decision but has big implications for how one expects to use a site.
#
artlung
capjamesg[d] you mentioned: *I noticed that one page on my site doesn't have my code styling JavaScript, for example. I overlooked that in implementation.
#
artlung
I don't know exactly how, but I'd like a workflow that lets me find these kind of things.* and following up here...
#
artlung
For me the only way to manage that stuff across time is to put the content and the dependency (the script and styles, usually, but also images or other assets) as close to the content as possible. Sometimes like a txt or json file that mentions it. So my-article.html is right next to my-article.figure-1.gif and my-article.js are all in the same folder.
#
[Joe_Crawford]
For the headers in my site when I switched to keeping *every* bit of CSS and JavaScript inline in the HTML of each header because I don't have confidence in creating a system that will be future-proof.
#
[snarfed]
we talk pretty regularly about "evergreen" pages, wiki style, vs dated posts
#
[snarfed]
(cc timeissuspect)