I took on this role for my team. I’ve maintained an internal website for probably 13 years that has all the links people need, as well as some useful tools I wrote. When a new link is discovered by someone on the team, or something changes, they tell me and I make the update. One update for everyone, and everyone on the team only needs one bookmark in their browser.

Searching is another big thing. Instead of making people go to one of a dozen places to search that specific site, I have a search box on the link page that people can use to search one of a dozen different internal sites. Some are pretty basic, just adding the search term to the query string and opening a new tab. Others try to be a little intelligent, for example looking at the term to see if it’s a ticket number and what type, a server, a knowledge article, or something else, and using the appropriate method in our ITSM tool to open it up. This alone makes me use my search instead of the ITSM tool’s search, because mine doesn’t require the user to navigate to the proper record type/table as a prerequisite to the search.

It’s an easy site to build and maintain, yet has become an indispensable part of many workflows. While I made it specifically for one team, I see it in bookmark bars of people across their organization all the time. I’ve also seen some of the little utilities used in other team’s demos, where my little page enables, in a small way, the new thing they are building and showing off.

Sounds like a job for RAG. We're about to prototype a system at work to point to all our confluence, Google docs, Jira tickets, gitlab source, and hand written KB articles, so adding a section for interesting links should turn the RAG system into a CBO.

Why not just librarian? Companies used to have their own libraries and librarians.