Feature Request

Currently, when exporting the knowledge base as a ZIP file, custom CSS configured for the live site is not applied to the exported output. This causes several styling inconsistencies that make the exported file difficult to use as a deliverable. Below are the specific issues observed: * Inline code styling does not match the live knowledge base. * Code block styling is difficult to read. * Table styling does not match the live knowledge base and is hard to read. * Hyperlink styling within articles does not match the live knowledge base. * Font family, size, letter spacing, and line height are not configured correctly. * LNB hyperlinks appear to be using default Document360 CSS instead of the custom styles. * Overall, custom CSS does not appear to be applied to the exported file at all. We would like to request that custom CSS be reflected in the HTML Export ZIP file so that the exported output visually matches the live knowledge base. This is essential for us to use the exported file for external distribution and documentation purposes.

I add comments every time I publish an article. It would be helpful if these comments were included in the Article Published notification email. Team members and management monitor these emails to know when certain updates are available.

The linking feature only lets me link articles. When I have synonyms, I would like to enter the definition only once in one place and then link the synonym(s) to this definition within the glossary itself. Example: Term1 > Definition; Term2 > see Term1 (linked). This would also be useful for terms and their abbreviations.

We have offline environments that require access to our documentation. However, we noted, the customers on these setups don't have access to the KB Widget. Sure, there is an option to export the KB site for the users to consume the documentation but that is user experience averse. We want the ability to offer the same level of access and service to our offline users. Therefore, it is requested to offer support for this feature on priority. We'd be happy to chime in if you want help from our team in terms of configuration or mapping approach.

We use snippets extensively in our content. It is a show stopper that glossary entries are not supported in snippets. The whole point of a knowledge base is content reuse and content management, but Document360 does not correctly handle snippets, variables, and glossary terms. These need to be integrated.

If I search on (e.g.) "(DEFAULT)", I need to see instances with the parentheses. But the search renders instances without (e.g., "default"). Thanks.

We were able to link the headings inside the accordion with the old link popup. In the new link popup modal, we were unable to link to a heading within accordion / FAQ. It would be great to have this functionality included as well.

The Tasks card on the dashboard only shows tasks for the current calendar week (Sunday–Saturday), not a rolling 7-day window. This means a task assigned on a Friday with a due date the following Tuesday won't appear on the dashboard until Monday, leaving almost no reaction time before it's due. Tasks assigned near the end of a week, or with due dates just past the week boundary, can sit invisible on the dashboard for days before ever surfacing. A few of our customer's are dashboard-driven and they rely on the dashboard (not the full Tasks view) to react to newly assigned work. The current week-based logic undermines that workflow, since tasks can be invisible on the dashboard for extended periods depending on when in the week they're assigned. Requested at minimum: change the dashboard Tasks card filter from "current week" to a rolling 7-day window. Ideal/preferred solution: let users choose the bucket shown on the dashboard Tasks card, e.g.: Overdue Next 7 days Next 14 or 30 days All tasks (fallback/last resort)

Currently, the PDF export option available under Content Tools exports only the latest published version of an article. If a user wishes to export the draft version in PDF format, this can only be done individually from the article’s editor page, where the export captures the current draft content. However, there is no way to perform this action in bulk. When exporting from the All Articles section, even if the articles are in draft, the export still fetches the last published version rather than the draft. Customers have raised a concern about this behavior, since the Content Tools PDF export can already export the latest published article content, then why does "All articles" also do the same things. They have mentioned that, ideally, the bulk export from All Articles should function the same way as the individual export, but on multiple articles at once.

Team, we currently have the ability to export articles in the PDF, and which is fine. However, we want to be able to export in Word .doc or .docx format as well. In the previous tool our team was using, we could export a Word file. It is especially useful when we have to share the doc with the customer offline and they want to have updates made to it in real-time. Our sales staff in collaboration with our doc team can help them edit or update the exported version in real-time. Our tech writing team will then push the updates in Document360 for it to be published with the next release cycle. This way we're letting customers assist us on our tech doc efforts. See the screenshot below. A native capability to "Export to Word" similar to Export to PDF option is the need of the hour.