The UConn Knowledge Base is built on Confluence, a knowledge management and collaboration platform. ITS recently moved our content to a cloud-hosted version of Confluence, and this has led to a few key changes:
New URLS
The URLs for all the articles have changed. They now begin with kb.uconn.edu/…
To minimize disruptions, we left the older version of the Knowledge Base visible after the migration to the cloud. This gave our community time to adjust to the new environment and meant that links sent out during the migration would not break.
Starting the evening of March 15, 2022, we are hiding the old KB, and any links that point to the old KB will break. The older links begin with confluence.uconn.edu/…
To update these links, go to kb.uconn.edu and find your article. Then copy the URL in the browser’s address bar. Replace the old link with this new one.
New Log In
Log in has changed. If you have access to Confluence and the Knowledge Base, you now log in with your UConn email address, click the button
Log in with single sign-on, and then enter your NetID credentials.
Updated Organization
The Knowledge Base has grown substantially over the years, and we wanted to better position it for growth. Content is now organized into categories so that similar topics are grouped together. This organization also makes the left-hand navigation is more manageable.
The Knowledge Base is not just for ITS! If your area is interested in adding support articles to the KB, contact us at ITKB@uconn.edu
Modified Design
We use a theming plugin, Refined Themes, to create a public view of the Knowledge Base and make it feel and function more like a website than a content management system. This new product has let us create custom landing pages for the different categories and unifies the different spaces that make up our Knowledge Base.
Changes to the Editor in Confluence
Confluence Cloud is very similar to the data center version but a few processes have changed and features added.
Confluence Cloud also has a new editor, and we found that some of the content in the legacy editor was not compatible. to help our editors, we have documented known issues and suggested workarounds.