Feature Request

There is a significant need to provide offline access to help documentation for countries or hospitals where internet connectivity is restricted. This is a critical challenge in scenarios where documentation is required for offline users. Could Document360 offer any potential solutions for this use case? Given that there may be a large number of customers in similar situations, exporting the full knowledge base as PDFs or HTML pages alone does not fully meet the requirements.

I want to be able to provide users with the exact help they need, based on the specific scenario they are experiencing or the unique combination of settings they have. For this, I'd like to create a decision tree, that will lead the user eventually to the best possible help content for their scenario.

We are raising this feature request on behalf of the customer (Michelle Vankolck). Currently, once an article is published, the comments are automatically resolved. However, the customer would like to have the comments remain unresolved even after the article is published.

Numbering is not continued (it restarts) most of the time - if there is a Note, warning, figure etc..added in-between the steps (example: figure added or Note added between step 3 and 4, step 4 becomes step1) It has to be continuous even if there is a image, note, caution, warning, etc.. added in-between the step. There should be an option to restart or continue numbering.

Currently, if we set the font as Verdana in the global settings, the KB site will render as Verdana. But the KB portal editor will show Inter for all the articles. Our customers would like the same font to be displayed in the editor whichever is configured on the global settings (Customize Site) page.

It would be very helpful to be able to "unpublish" a new article. For instance, if someone prematurely published a new article that has no previous versions, I could just click a button that would revert the article back to its unpublished state. (This is not the same as switching to a previous forked version -- I'm thinking of new articles that have no revision history yet.)

When glossary terms are imported, it will be nice to have glossaries associated to the related terms automatically across all the articles.

Public online commenting for non-paying team members (where a DOC360 paid seat is not required). We want to allow 10-100 of our team the ability to make inline comments.

It would be helpful if Document360 could incorporate an AI-powered feature that automatically generates step-by-step articles from video inputs or a series of screenshots, similar to the functionality provided by Scribe. This would streamline content creation and enhance the user experience.

Visual Editor: An intuitive visual interface allows admins to add, remove, and connect different elements of the guide, resembling a flowchart or diagram. Drag-and-Drop Functionality: This enables admins to easily drag and drop elements within the editor to structure their guide. Guide Step Customization: New steps with text and media. Paths to existing steps for branching. Embedding other guides or resources. Adding external links. Interactive Elements: Incorporate interactive elements like dropdown lists, radio buttons, and regular buttons that can collect information or guide users through the decision-making process. Preview and Organization: Preview guide in a new tab. Feature tools for organizing and reordering guide steps directly within the diagramming interface. Advanced Interactions and Navigation: The next steps can include adding a new step, linking to an existing step, linking to another guide, or an external link. The next step for behavior for radio buttons and dropdowns includes adding branching options within a step for multiple user paths, configuring linear steps that users can scroll through, and including choices in a step to create branching guides. Delete node option for removing steps from the guide. Publishing Options: Clear options for publishing the guide, including saving drafts, publishing immediately, or saving guides without publishing for future edits. Embedding and Collaboration: Embed one guide into another guide within a decision tree guide to create a cohesive flow of information. Internal notes in guides for team collaboration and clarity, providing context, guidelines, or reminders about the content of the guide, visible only to team members.