There’s a case to be made, realistically speaking, that using a well-known framework or even a CMS like Wordpress means less complexity specific to your website to understand for the next person. FTP cough SFTP or Markdown/HTML is definitely not beyond non-technical people to understand and use, but sadly there could be some resistance nowadays I imagine.

I would look into static website generators. Sadly I’m not sure what is most reliable nowadays, but I would prioritize easy of use and installation, as speed is probably meaningless on your scale. Here’s a random article.

There is !linuxmemes@lemmy.world and !linuxmemes@lemmy.fmhy.ml.

I mean… “who needs features in 2022” is onto something. But I use both, for various Nvidia and laziness related reasons, and have a dim idea what they do inside, as probably most flamers on the topic.

Feedback: to see an example one has to click through to another file in the repo.

Is it a subset of Markdown or YAML? It is a type of decision that it would be good to be upfront with to the users. It also gives you a framework for further thinking and development, and some out of the box parsability.

YouTube recommendations are often 30-60% decent and you can always fall back to that. Anything that has tags and similar artist functionality: Last.fm (still technically exists), everynoise.com, more specialized sites like Encyclopedia Metallum. I like to get some recommendations out of band even if I use streaming, otherwise it’s too easy to phase out and make your memory dependent on their algo.

Some (even) more niche and involved methods:

• I am experimenting with using search.marginalia.nu for searching for opinions on forums and personal websites, starting with my “initial” artist, genre or the vibe I’m looking for.
• if you look for an album on ebay or wherever and find a have a small seller with their personal collection, I like to take a listen to some other items from the same person that look promising.
• at least for jazz and probably mainstream pop/rock (? however to call it) there are physical books dedicated to briefly reviewing a ton of albums. I prefer this to typical written reviews because all I need is an album name and some gist of what to expect. If the writer has a long analysis etc. I tend not to agree after listening, I may like some things that they hate and the words have nothing to do with music. Probably the “1000 albums you have to listen to” lists on the internet can serve similar purpose.

Obvious things I don’t see mentioned:

• Bash scripts kept in the home directory or another place that’s logical for them specifically.
• history | grep whatever (or other useful piping), though your older commands are forgotten eventually. You can mess with the values of HISTSIZE and HISTFILESIZE environment variables in your system.

Context just before that quote:

As we understand it, this contract clearly states that the terms do not intend to contradict any rights to copy, modify, redistribute and/or reinstall the software as many times and as many places as the customer likes (see §1.4). Additionally, though, the contract indicates that if the customer engages in these activities, that Red Hat reserves the right to cancel that contract and make no further contracts with the customer for support and update services.

This is rich, don’t know how many people are aware of that.

I was looking into Arch-based environment and wondered if there is an option for a scenario where you don’t have to update for a few weeks for example, because you don’t use that computer or whatever. But you still want to try the Arch configurability and wiki docs for it.

From what you’re saying, it’s still actually all rolling release. From my (flawed? correct me) understanding it is different from Ubuntu or Fedora, where you can update an outdated OS state and it isn’t supposed to break. Possibly barring changing OS versions.