(I can’t see the edited out part but if it was about yay…)

Yay builds in your local cache and then when it is ready to install it asks for sudo. The reason for this is because sudo can timeout during long builds, and more importantly if you compile with sudo you run the risk of arbitrary code execution. So it is safer to run with just yay and then it will ask for sudo when it actually needed.

what you use for your documentation

Hugo (markdown) files that i host on my internal server.

how you organize it

I use basic directory structure. Top level directories are like “dev”, “home”, “general”. Self hosting is a dev/ subdir.

what information you include

Depends on how familiar i am with it and how often I’ll be referencing it. Something i know well or access often will be more high level. Things like an annual process i have documented in more detail

how you work documentation into your changes/tinkering flow

My site has an “edit this page” feature which i use to open my IDE and make the change as I’m doing things. Sometimes I’ll be lazy and just add in what i did this time and then let future me reconcile the differences 🙃

Codeberg has limited private repos though which i assume is what they were referring to.

Sourcehut allows private repos. Alternatively id look into a self hosted forgejo instance you control.

And many people overlook it but git has its own webui.

If I’m being completely honest, it sounds like you hit a problem and then just kinda gave up (I’m not trying to sound mean or anything - please don’t take it that way).

I got the same impression. Which is fine if that’s someone’s approach, but that same person probably shouldn’t be on an arch-based distro if that’s the case.