
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.
wayland was a mistake

There is [email protected] and [email protected].
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 ofHISTSIZE
andHISTFILESIZE
environment variables in your system.
Oliver Nelson - Stolen Moments

YouTube Video
Click to view this content.

Running retro 9x/workstation look on modern OSs
Linked a source of inspiration. This is a fuzzy topic but maybe will drive "engagement" of purists 😝
The idea is to get a daily driver machine GUI to look like a retro desktop or workstation while being functional. Sure, "functional" means different things for all people, tastes differ etc. Why? To me it's more soothing and makes me want to do Serious Computing (or even work, gasp) and not get distracted. Bonus points if we can actually run some ancient software for this (old Linux desktop environments? I once kinda got Enlightenment DE to work).
My current modern setup is KDE Plasma with "Platinum retro" theme: https://store.kde.org/p/1320042 and applications style (basically buttons) set to "MS Windows 9x". You can also mess with system fonts. Kind of lazy, but does give this gray austere vibe. Maybe people have more elaborate setups, or ones easier for non-Linux folks.