Log in to your Document360 account to give feedback

Boards

Feature Request

Bugs

Migration Requests

Powered by Canny

Feature Request

Anonymous

Schema markup (JSON-LD) support

We want to add Schema Markup (JSON-LD) to build a standardized, structured metadata API directly into our HTML <head> to give web crawlers a clean object model to parse. Additionally, Voice assistants (Siri, Alexa, Google Assistant) rely heavily on structured Q&As, so a properly configured Answer.text property acts as a read-ready script. Core Schema types we want for our help center: TechArticle (highest priority) For individual help articles (e.g., "Send a Message", "Download Dialpad"). This is the most impactful schema for a help center. Fields: headline, description, datePublished, dateModified, author, articleSection (maps to the category like "Calls & Messages") FAQPage Many help articles are structured as question-and-answer content. Adding FAQPage with Question + Answer pairs can earn FAQ rich results directly in Google SERPs — high-value for support queries. HowTo For step-by-step setup and configuration guides (e.g., "Set Call Routing Rules", "Set a Custom Ring Duration"). Enables rich result display with numbered steps. BreadcrumbList The site has a clear hierarchy: Help Center → Category → Article. Breadcrumb schema improves navigation display in search results. WebSite + SearchAction (Sitelinks Search Box) The homepage has a prominent search bar (CTRL + K). Adding SearchAction on the WebSite schema can surface a search box directly in Google results for the brand. VideoObject The homepage and articles embed YouTube videos (e.g., tutorial videos). Marking these up can enable video rich results and carousels. Organization On the homepage/footer to establish Dialpad's identity — name, logo, social profiles, contact URL. Supports knowledge panel accuracy. SoftwareApplication For pages describing the Dialpad app itself (download page, feature pages)

Nested folder structure for subfolder hosting

Having an option to use nested path while configuring sub folder hosting ( Ex: /cloud-storage/resources/docs) will help with better SEO, proper reporting on all web metrics, and more.

Track Resource for Documented Workflow within the Tool

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.

Add option to support multiple versions of the docs using a dropdown selection

Readme.io and Paligo both support a very simple tool for creating new versions of the documentation using branching. This allows the writers to work on a new version but to keep the previous ones available for customers to view rather than override or clone the page. Considering Readme.io and Paligo have had this solution in place for many years now, it's obviously not something very cutting edge or difficult to implement. I considered using your forking solution (suggested by Eddy) but doesn't do the work and simply adds confusion to the writer's workflow. Any of your customers who have both on-prem and SaaS solutions need to have doc versions, and you're not addressing this important issue.

Expand JWT To 2 URL Configuration

We have two separate servers we use that are customer-facing. One is the production server for all our customers. The other is the demo (demonstration tenant) that our salespeople use to show our product to potential customers. Right now, we can only have one JWT URL to our production server -- that's all Docs360 allows for. The URL to our demo tenant cannot be added because of this limitation. We'd appreciate if you could allow for two Login URL instead of one so that our salespeople can show potential customers the knowledge base and not just the widget.

Nginx doesn't support sub_filter when hosted on Heroku

Customer tried using the sub_filter when hosted on Heroku and mentioned that their nginx doesn't support this. They need a way to use sub_filter on Heroku.

Add multiple domain names

Sometimes we need to access our project with multiple domain names, so Document360 team should provide option to add multiple domain names. Currently we can only add one domain name.

Provide different tree view for specific categores.

We would like to focus our readers on specific parts of the tree and elimiate other tree options, hence provide a different tree hierarchy depending on the article or category. See exmample of this behaviour in this KB: https://docs.uipath.com/

Ability to fork replicated articles to make changes

For versioning, on replicated articles, I should be able to make changes/edits/updates to the child article as it represents the newer version documentation. This is superrrr critical for our use case.

Language drop-down always defaulting to English language when switching between the versions.

The customer reported that the language drop-down menu consistently shows English, even after switching between versions. We've explained that the language drop-down will always point out the default language of the version since they have multiple languages available in different versions and desire the language drop-down to display the same language as the previous version.

Load More

→

Powered by Canny