Confluence is documentation theater. For most Confluence usage I've ever seen, the author's real purpose is mostly to signal that documentation has been written, and the experience of whoever might be using it later is a distant second.

Confluence docs tend to be written as the result of timed events, for each project or sprint or meeting or whatever, rather than organized by topic. And most are write-only and never looked at again.

What a Confluence (or any documentation) repository really needs is continuous refactoring, to be organized by functionality rather than time implemented. Just like code, if you never do that, what you get is documentation debt and a big ball of documud.