Feature Request

Some localization variables are inexplicably in-editable. That raises an issue when a translation is too big to fit into the UI and we would like to edit it into something shorter.

We have a few versions on the site which have different functions. Some are all part of Product A, and one is Product B. We would like the possibility to choose which versions will be in the menu, and which will stay as dropdown. For instance version 1 and version 2 will be menu, and product Z will be dropdown. Thanks

Initially, we expected the tagging feature in the Workflow section to work differently. We anticipated that it would involve opening the workflow, using the visible notify box to tag a user, and then assigning the article. However, the process currently involves navigating through the workflow, clicking a small assign button, tagging users, and then assigning the article. I suggest finding a way to better distinguish these two options to make the process clearer. In-app assigning and notifications should take priority in the user experience, with these being the first visible options, over email notifications.

When creating another language version the internal links to other pages are not updated, so they still point to pages in the default language. For example, we used English as our default language, but when we created the Spanish version and translated our content, all links on the Spanish site link to English pages. This issue was recently fixed when creating a new version based on an existing version, so that links would be automatically updated to point to the correct version - we need something similar so we don't need to manually update every link on the site for each new language.

I would like to create a new version of our documentation to match the recent product release without having to purchase a new workspace. The new version of documentation would contain 2 new articles, which I don't believe this merits the purchase of an additional workspace. Our users (readers) would prefer to choose their version of the product in a drop down menu to make sure they have the correct version of the documentation.

Customers need an option to view recently published English articles within the draft of German workflow assignments. This would allow them to sync the content with third-party translation tools.

Raising this feature request on behalf of the customer (Omkar). The customer would like to have the option to get the version ID of the project within the portal. We suggested the customer about the API endpoint to retrieve the workspace ID. However, the customer would like to get the version ID from the portal.

we have versions - we need to be able to duplicate an entire category or multiple categories in order to create a new version...

When I create a new knowledge base version from an existing one, all the articles default to the "Draft" status. I then need to compare both workspaces and manually publish articles using the "All articles" section. I would like an option to ensure that all published articles in the existing version remain published in the new version, and draft articles retain their draft status.

The selected workspace should remain constant when refreshing and navigating across different sections, rather than reverting to the Main workspace and having to select the one you're working on all the time.