Or if you’re publishing helpful reference material.

I am under no illusion that my content is popular… but if I spend the better part of a weekend trying to get a config file working for a poorly documented tool, I’ll share it knowing that low double digit number of people will google and find it.

Content exclusively behind rss is like tech support exclusively on discord. Discoverability approaches zero.

Or if your goal is that interested parties can find and access it easily.

Otherwise why make it a blog and not just a private document?

But it's not private?

By adding addition friction, one reduces that 'accessibility'. Adding unnecessary friction by doing extra work setting something up as feed-only so that readers have to do extra work to decide if the feed-only content is worthwhile, the question I have is 'why?'

Subscribing to a site sight unseen, no pun intended, is not something I or anyone who is protective of their feed inbox would do. I curate my feeds so that I can sit down a few times a week and deeply read.

Precisely, that's the whole point.