I find it frustrating when steps are skipped but you don't know that they are missing. If there is a brief description of install x or configure y, then no stress, I can go find the info.

I broke my akkoma install down into setting up a VPS as a stand alone guide, and the actual install itself as another. I still got hassled for it when someone failed to install when they enabled a non-default option when my guide didnt mention it. Like... there were defaults, maybe just install with those first man and see if it works.

So I feel your pain, I suppose.

The main reason I wrote my guide was for my own documentation and learning, as I wanted reproducible steps for myself, and the main sticking point that I had was nginx hogging port 80 and not letting certbot --standalone connect. Like, I gave up for months on a pleroma install because I could not find why certbot would fail. I have of course learned a lot since then, but I included that line and why in my guide, so others can learn from my ineptness.

But yeah, if I write a guide, then generally it has all the steps requiring action, so if my very average memory can't be relied on I can just follow my notes from last time in a repeatable fashion. Common tasks might be a casual mention/reference, but they will still be there unlike some guides I have found, so the info can be searched for online elsewhere.

I haven't read your posts so can't comment specifically (and I have zero expectation of others, people can do as they please), this was just to give some perspective from someone self-taught online.