Knowledgebase Admin - Improved Navigation Performance
What's New
We've optimized the Knowledgebase Admin navigation menu to make browsing your knowledge base structure faster and more efficient. You can now expand and collapse categories and sections in the left sidebar without automatically loading all articles. Articles will only load when you explicitly select a specific section.
Why This Matters
Previously, expanding any category or section would immediately load all of its articles, even if you were just exploring the navigation structure. This caused unnecessary delays, especially in large knowledge bases. With this update, you can quickly browse through your content hierarchy and only load articles when you need them.
What's Changed
- Faster Navigation: Expand and collapse sections without triggering article loads
- On-Demand Loading: Articles load only when you click on a specific section
- Better Performance: Reduced API calls and faster response times when browsing your knowledge base structure
Knowledgebase Admin - A Cleaner Interface
What's New
We've simplified the KB Admin interface by removing the article category navigation from History, Settings, and Folders screens.
Why This Matters
These changes create a faster, cleaner, more focused interface that reduces clutter and makes it easier to find what you need. The navigation sidebar wasn't providing relevant information in these screens.
What's Changed
- Cleaner Interface: Removed navigation sidebar from History, Settings, and Folders screens
- Better Performance: Each screen now focuses on the core functionality without loading the article category navigation
Knowledgebase - Upcoming Release Process Changes - Phased Rollout for Customers
What's New
Starting with the next release, we will be implementing an automatic phased rollout process for all Knowledgebase changes, giving customers time to prepare and adjust before changes reach their environments. Most users will see changes roll out between 1 and 2 weeks from announcement.
Why This Matters
Customers with larger teams often need time to communicate changes internally, train their teams, and adjust their workflows before new features or updates are deployed. This phased approach ensures that our largest user bases have approximately one to two weeks from initial deployment to prepare for changes, reducing disruption and allowing for smoother transitions. The automatic rollout process also includes built-in gates that can pause expansion if issues are detected, ensuring quality and stability throughout the rollout.
Exceptions apply, for example for hot fixes, non-UI changes and others.