Feature Requests

The translation process is at best, clumsy. A user shouldn't have to go to each individual language to translate it. Make it so it's an auto-translate into the multiple languages upon publish from the default language.

Once we submit an article for review, we can't remove the review state unless we publish it. This isn't ideal in scenarios where the article was disapproved and we just want to get it out of review and submit it again when it's adjusted. In these cases, we have to publish the article and unpublish it to remove the review state. Once the reviewer disapproves the article and the author makes the changes, he can't resubmit it for review. How does the reviewer know they updated it and that they need to review it again? Related to those two points, users without the "unlock publish" ability cannot get articles outside of the review state and cannot re-submit them for review. The only approach right now is to add a comment in the article to notify the reviewer that he needs to check it again. Review comments aren't saved in the editor. We should have a log of the review rounds with the corresponding comments.

Main content takes too long to appear on mobile across all pages, causing Core Web Vitals failures (take a look at your own Google Stats!) and a noticeably sluggish user experience. Likely due to page bloat and/or server response time. Needs platform-level performance improvements.

Since we enabled Swifty AI tool in our knowledge base, we've been receiving lots of spam through it. For the contact form, we enabled a reCAPTCHA to avoid this, but I don't think there's any option of doing that also for Swifty, since it's under Helpjuice domain. Is there any way we can solve this?

Like google, make it so if someone has a typo or something in the search it will offer other search suggestions.

Articles should all be categorized - and it's so easy to miss that step. When publishing, it should throw an error message if there is no Category selected.

In the dashboard section, we have categories that allow us to divide the content by topic. We can navigate through folders for better organization within the Knowledge Base and to improve how visitors view the information. We manage categories with different topics, and we also have some articles with very similar titles. Example: Category: Employees Article: How to Register an Employee Category: Payroll Article: How to Register Payroll However, internally, our documentation team needs a filter on the dashboard that allows them to search by category. The search bar at the top currently searches all categories, leading to confusing results for pages with virtually identical titles.

When using Swifty in the helpbar it would be very helpful if the documents Swifty referenced were linked below the answer, as it does on the Swifty chat bot.

Be able to define collaborators or admins as having permissions to publish in certain groups/categories only. That way they can freely edit and publish in their selected category and not be able to do so anywhere else on the knowledgebase.