Feature Request

Currently when an new article is created, it isn't copied into the versions with other languages (the only happens when the language is added when the article has already been written). Therefor the content of the first published version should be automatically copied to the other languages (Proposal 1) and if an article is updated the translated version should be assigned a tag " to review", so that the translation can be updated (Proposal 2)

In KB Site 2.0 articles, inserted links are not underlined by default, unlike in the portal and KB Site 1.0. However, links inside callouts are underlined. Please ensure consistent link styling across all contexts.

Currently, when viewing article metrics to measure footfall - who visited or interacted with the articles, the available filter is limited to "Team accounts" and "Readers." While this is helpful, it can lead to overlapping data and prevent transparent tracking. For example, when user A views their published article in a production environment, Doc360 may categorize them as a "Reader," when in fact, it was a person from the documentation team viewing their live version of the article. We want the ability to filter views based on IP addresses, domains, and custom buckets, such as "customers of Company X" and "customers of Company Y," etc. You can draw inspiration from how Google Analytics provides filtering capabilities. For instance, if we filter out the internal domain or email addresses of our employees, anyone visiting the article from within the company will not be registered in the article metrics, AKA, Analytics dashboard. We believe these changes will significantly improve our ability to track article performance.

We have observed that at the time of editing an existing article, Doc360 automatically assigns it a version number. For example, if a published article is edited for the first time, the new draft becomes version 2 or V2, where the previous version is V1. Since our product uses a release cycle and patch updates to reflect new changes to the documentation (features, bug fixes, etc.), we want the option to assign a custom version, which in our case will be the release version. See the attached screenshot. Instead of "V2", we want it to say, for e.g., "Release 1.135 p01." Please let us know if you need any further clarification.

In the site view, the Left pane which displays the categories and articles can only be closed. There is no option to move and adjust the width of the left pane. Being able to view and adjust the width of the left pane will be more user friendly when viewing lengthy article titles.

I'd like to be able to create reuse text 'on the fly' from within an article. Select the text, click a button to create a new snippet. AND to be able to see the preview of a snippet in the article.

Customer requested an option to automate sending an acknowledgment email to readers when they submit feedback.

I'd like the ability to set/scope reusable content (snippets, variables, glossary) per category, while also allowing for global/all category reusable content. Scenario: We have different variables and glossary terms that are used in specific areas of our product. These product areas have their own categories in Doc360. I'd like to be able to set these variables and glossary terms to only display in their respective editor drop-downs when the article is in a specific category. This will reduce the clutter of options for other authors in different categories who don't need these specific variables or glossary terms. Reusable content scoped to other categories should still be searchable and usable from within other categories.

We want articles to show their respective category, AKA our module names, in the URL structure. For example, "/docs/onboarding/getting-started" Instead of "/docs/getting-started" Where "onboarding" is the category name and "getting-started" is the article name, which is nested under "onboarding." We have followed the instructions on creating the categories by either selecting "Page" or "Index" from the available category types, but we don't have the article's slug pointing to its parent category or its inclusion in the URL, which is vital for SEO and readability. The ask is an industry standard for block editors such as WordPress, where you can customize the slug format to suit. You're requested to look into this feature's availability at your earliest.

Provide display of anchor links inside accordion content when linked to another article or within the same article.