why does naming things have to be so hard ugh

currently: trying to think about how i manage my various web sites and general web presence, and while i *could* put stuff onto the apex trwnh.com domain, it would be far more convenient to break things off into various "content management systems", one "cms" running per fqdn. this encourages me to (and puts me in the conundrum of having to) come up with some kind of "bucket" for my resources, and that requires me to actually know wtf i'm doing with all this before i name it

at least i *think* that division makes sense. it seems like it's more trouble than it's worth to orchestrate content from multiple systems into a single directory structure, unless you drop to the level of just copying some static output into a folder. but i'm too lazy to do that

so much easier to point all my dns records at my vps and then create nginx server configs that let me set up whatever subdomain pointing at like a hugo project's public output

i suppose i *could* use subdirectories in my trwnh.com nginx config, but idk, it somehow seems less annoying to set up an entire subdomain config than to add a location block. i guess the mental blocker for me is that i'm afraid the config for trwnh.com will just keep growing and growing and get harder to manage.

now that i'm actually talking it out with myself, it does seem pretty ridiculous. although there are some benefits to the separation, there seem to be just as many problems.

i guess the other mental blocker is not wanting to "burn" uris and identifiers? linking to something in one system makes it hard to migrate out of that way of doing things. but this shouldn't be a big issue, certainly not the point that it paralyzes me from actually doing things.

but also also... i guess it doesn't really matter what i do, there are multiple valid ways to approach all this stuff. just pick one and do the thing

ok now that i found some hugo projects on my drive that i don’t remember ever setting up… i think it may actually be a good idea to consolidate all this shit into a single domain and git repo. there’s quite possibly duplicate work in here too

trying to think of which "buckets" make sense here

1. i have a subproject rn (blog.hugo) which contains a bunch of old threads in a /threads/ subdirectory, and it'd be weird to have /blog/threads/some-title/

most of the stuff in there is not really contextful, because when i was compiling my self-replies and going through those threads, oftentimes the other participants had deleted their posts or accounts, so there wasn't anything else to contextualize my side of things. what do i call this

2. i'm probably moving my "wiki" from wiki.trwnh.com to trwnh.com/wiki but idk if it should exactly be called a "wiki" anymore. it's not terribly structured like one, it's more an arbitrary folder structure made browsable by the hugo templates i wrote to list all subfolders and subfiles

this is less pressing bc "wiki" isn't the worst name ever, but i do think there's potentially a better name here, i just don't know what it is yet

@trwnh it's like they say, there's only one hard problem in computer science: naming things, and off-by-one errors

@jdp23 that's outdated information. the two problems in computer science are naming things, off-by-one errors, and cache invalidation

so what *would* you call a thing that just mostly contained a list of loosely collected threads archived off of my social media, anyway

@trwnh
Notes or Zettelkasten

@yala not really a good fit, it’s closer to a very low-effort blog with only one category than a system of note-taking