Feature Request

When switching between workspaces the platform always redirects to the top-level category list. This forces users to manually search for the article they were just viewing. Suggestion: Enable context-aware workspace switching—so when a user is viewing an article in one workspace, switching to another keeps them in the same article path, just in the target workspace (if that article exists there). This would significantly improve efficiency when: Comparing how an article appears across versions. Reviewing changes before publishing Maintaining consistency between versions or locales Optional Enhancements: If the article doesn’t exist in the target workspace, offer a message like “This article doesn’t exist in [workspace]. View root instead?” Allow users to set a default fallback behavior (stay on current article or go to article list)

Currently, when working with snippets, there is no built-in option to insert variables or glossaries within them. This limitation presents a significant challenge when dealing with frequently changing content, such as mentioning a particular software or vendor name, as these details need to be updated across multiple documents. In traditional articles, variables can be inserted, ensuring that updates to a single variable are automatically reflected across all relevant documents. However, this functionality is missing in the snippet builder. The lack of reusable content integration within snippets forces the users to maintain a separate list of documents to update manually each time a variable is updated, leading to additional overhead and potential inconsistencies.

When creating snippets, they should have the same font as the one we use in our documentation and not a different one or at least have the option to change the font. Also, the spacing in the back end around numbers doesn't apply correctly in the front end.

We do not have the option to select the font size of 16px in the variable creation section. Since we are using the same size(16px) in all their articles. In the content reuse section, we don't have the exact list of sizes which is available in our editor. It would be great if we could include all the font sizes in the content reuse editor as well.

Our customers would like to know the limits on the number of variables, snippets, and glossary terms that can be added in their Project. The customers would like this information to be displayed on the KB portal itself as tooltip so that they can see these details themselves and manage their Variables, Snippets and Glossaries accordingly.

We are currently unable to save or update a snippet while in code view. We need to exit the code view first to save the content. It would be helpful if the update button could be greyed out while editing in code view.

Currently, the glossary popup cut off when we scroll top in site 2.0. It would be great if we could fix this.

Currently, the exact term used within the glossary is shown on the page. This doesn't look that great when different capitalization, plurals, or tenses are used in the text that the glossary term is used within. A simple example would be to have a glossary entry called "Canada Goose" which might get used in different scenarios. In many places, the term should not be capitalized for the word "Goose". In places where they are talking about a flock of "Canada geese" this would also need to be altered. Having a replacement text available as the glossary is used would be desirable.