Feature Request

Based on an earlier FR, Doc360 exports now support table of contents linking and allow entire categories, including subcategories and nested articles, to be exported together. The linking works as expected for navigation from the TOC. --- The issue arises with links inside the exported articles themselves. When one article in the export links to another article that is already included in the same export, the link does not navigate to that article within the exported file. Instead, it redirects users to the KB Help Center version of the article. This breaks the offline or self-contained nature of the export. If all referenced articles are already part of the export, internal cross-references should resolve within the exported document, not redirect to an external URL. Redirecting to online help is reasonable for links that point to: External websites such as Microsoft documentation. Articles in categories that are not included in the export. However, for links between articles that are already included under the same exported category or subcategory, the expected behavior is internal navigation within the exported file. --- For exports that include multiple related articles, we want: Cross-links between those articles are internalized automatically. Clicking a link should jump to the corresponding section or article within the export. External redirection to only occur when the target content is not part of the export. This ensures the export remains usable as a standalone document and supports offline consumption without loss of navigation context. --- PS: The export referred to here is PDF, not HTML export. The FR referenced is https://feedback.document360.com/feature-request/p/pdf-export-enhancements

Currently, if we schedule an article for publishing in Doc360, the editor does not allow us to make any changes to it. For any other instance, like when an article Workflow Status is in review, the changes can be made in real time. However, the only time the editor locks us out is during a scheduled publish. We want the ability to edit a scheduled article without having to move it to draft first. This increases the time to switch to draft and then schedule it afterward. Ideally, it should be smooth sailing as long as the article is unpublished. For example, in Slack, we have the option to edit scheduled messages without having to change their state. Once the editing is done, the user clicks the checkmark icon, and the updated message is locked for sending.

Customer needs an option to customize the email sent to users when they download a PDF from the site.

A bunch of our customers rely on offline documentation especially for airgapped environments, but the current offline docs are missing some of the basic capabilities that are severely impacting the customer experience and the ability to use the docs Priority item # 1 - Missing Table of Contents / left side navigation The offline documentation does not include a left-side Table of Contents or say the side navigation. Without a TOC, customers have no visibility into: What other articles exist within the same folder How content is organized How to navigate between related topics This results in a very poor user experience, as customers are forced to rely on direct links or guesswork instead of structured navigation. A TOC is fundamental to any documentation experience, especially offline, where internet access is already not available. Must have requirement: Include the same TOC/navigation in the left sidebar for offline documentation as in the online documentation Priority item # 2 - Missing Attachment Support Offline documentation currently does not support attachments. This is a huge turn off for customers accessing the docs in airgapped environments where there is no internet access to download attachments online. If an article contains an attachment, Document360 should be able to: Download the attachment as part of the export process Package it with the offline documentation Allow customers to access the attachment locally This is a reasonable and expected behavior for offline documentation and is critical for customers who rely on supplementary files. Must have requirement: Automatically include article attachments in offline exports and ensure they are accessible locally. Priority item # 3 - Other Enhancements (Low Priority) Some other important items that can be considered secondary include adding previous and next buttons, glossary items, and breadcrumbs. Currently, the TOC and attachment support are the most critical blockers.

In Doc360, there are several places where a certain action like creating a redirect rule or fixing a broken link does not show the person responsible for performing that action. Now there are two reasons; accountability and record keeping. We have multiple apps within our software and each is suited to a different category of customers. To cater to that, internal resources are accordingly assigned to deliver the best possible documentation experience. Often there is overlap between resources and when two or more teams work together, mistakes can occur. Following areas are without any visible resource tracking: 'URL Mapping' in Knowledge base widget 'Article redirect rules' in Site builder 'Style guide' in Site builder 'Variables' in Content tools 'Snippets' in Content tools 'Glossary' in Content tools For Glossary, we're already awaiting a Category-based glossary implementation, but to not able to sort via 'Last Modified by' or 'Created by', etc. makes the job very cumbersome. Similarly: 'Import and export project' in Content tools 'Export to PDF' in Content tools 'Manage links' in Analytics While Team auditing is available, however it's a global setting to monitor any compliance issues. We request you extend the existing functionality to the areas above. 'Templates' in Content tools Recycle bin Audit trail functionality at the article level The ask is a genuine business use case of 'who did what.' Tl;dr: Add a column 'Last Modified by' / 'Created by' to aforesaid settings/config pages.

I strongly urge you to consider how the custom data attributes affect our ability to use the code view. If such data needs to be added for things to work on your end, they should be added after processing the page, and not rendered in the code view. The way it is implemented now adds undue complexity for your users to sort through your added code. It makes for a quite bad user experience.

Currently, search results on the Knowledge Base site are displayed based on relevance, which can appear random when many articles match the search term. The current relevance flow follows this order: Article title → Associated tags → Article slugs → Breadcrumbs → Article content While this approach works for general discovery, it makes it challenging to systematically review and update content, especially during activities such as rebranding, where a predictable order is important. It would be beneficial to provide configurable options for displaying search results, such as: Current relevance-based behaviour (existing implementation). Alphabetical order by article title. Knowledge Base taxonomy order, matching the article structure shown in the left navigation tree.

The customer would like to retain logs and comments in the revision history. Currently, when an article is unpublished, the unpublish event appears in the revision history. However, once the article is published again, the earlier unpublish event is no longer visible in the revision history.

Several key features such as the Floik step by step guide, duplicate content detection, and the AI glossary generator are currently not usable due to limited language support. Adding support for English (US) and additional languages would allow customers to fully use these features as intended. This enhancement would significantly improve feature adoption and overall product value.

One of our customers would like the ability to identify articles that has an embedded PDF in it. Currently we do not have a separate filter for this. Hence, the customer would like an inbuilt for the same.