Firstly, this is not a technical discussion about confluence or plugins for confluence. It's about how an organisation should or could manage the use of confluence so that the information contained in it us useful.
We are a large organisation that has made confluence available to the staff. Over the years, people have added information in about projects, products, architectures, system connectivity, you name it. The result to date, conceptually, is that confluence has become a mixture of "gold" and "dirt" (mostly dirt) with the problem that one cannot tell what the gold is and what the dirt is. We have no central management of confluence and so it's a very dangerous place to look for information, especially for newcomers to the company, because you cannot tell what's gold and what's dirt. You find info that says system x connects to system y via an SFTP link but that was true 4 years ago, not today.
So the question is how are larger organisations managing the content of confluence so that the information contained in it is accurate. I recognize that there is a place for historical information (info on completed projects) but it should be clear to a reader that the info they are looking at is historical and may not be accurate today.
In past lives, I've seen this managed by a Knowledge Manager who's sole job was to curate the content, getting rid of crap and managing/forcing knowledge owners to refresh their content periodically to keep it accurate and useful. They also transitioned owners of pages who left the company to other employees.
So, what processes and/or management frameworks have larger organisations established to manage the content held in confluence to ensure it contains as much gold as possible.
Calling all collaborators! Appy Hours on the Atlassian Community is a monthly event where 4 Partner and app vendor presenters go head-to-head with 5-minute demos for the title of Best App Demo. I...