Feature Request

We would like to request the ability to configure a separate font specifically for the Japanese (JA) PDF template. We have noticed that the current font renders bold text correctly, but commas and certain punctuation marks are displayed incorrectly. We request support for a Mincho (serif) font, preferably Noto Serif JP, for the Japanese PDF template, while keeping the English (EN) PDF template unchanged. This would ensure that both bold text and punctuation are rendered accurately and improve the overall readability of Japanese PDF exports.

Our clients rely on the ability to download our release notes into Excel so they can filter/sort and perform UAT on our released items when they go to their sandbox environment. We previously had this capability with our prior vendor and now because we are unable to allow our clients to download their content from a table into Excel, we are duplicating work by maintaining our release notes in a table AND a separate Excel file, that we also have to ensure are always in sync.

Currently, when a project is exported, articles marked as deprecated are included in the offline documentation. While including these articles is the expected behavior, the exported documentation does not indicate that they are deprecated. This can lead to confusion for readers of the offline documentation, as they are unable to distinguish between active and deprecated content. Requested Enhancement: Add a visual indicator or label in the offline documentation export to identify articles that are marked as deprecated in the knowledge base. This would ensure consistency with the online experience and help users easily recognize deprecated content in exported documentation.

Currently, Variables and Snippets are excluded from the Project Export & Import process. When a project is exported and imported into a destination project, these content reuse elements are skipped, resulting in broken references and requiring users to recreate them manually.

We have two potential solutions to address the same business need. Either option would be acceptable: Option 1: Incremental Project Migration Support Enhance Project Export/Import functionality to support incremental migrations. During import, the system should be able to identify articles using a unique identifier and recognize when an article already exists in the target workspace/project. Instead of creating a duplicate article, the import process should update/replace the existing article. This would allow repeated imports of the same project content without generating duplicate records. Option 2: Bulk Replicate Functionality Provide a bulk replication capability that allows a project to be replicated across multiple workspaces in a single operation. Business Use Case We manage multiple clients who require access to the same project content, but within their own dedicated workspaces. Currently, maintaining identical projects across multiple workspaces requires significant manual effort and creates challenges when updates need to be propagated. Either incremental migration support or bulk replication would significantly improve operational efficiency and simplify content management across client workspaces.

Comma-separated CSV exports, such as feedback, are not protected by quotation marks. This is an import problem when article titles also contain commas because it destroys the column assignment in Excel or other tools. (Could be fixed in tandem with https://feedback.document360.com/feature-request/p/add-dedicated-column-for-internal-comments-or-notes-in-csv-export and https://feedback.document360.com/feature-request/p/include-a-date-field-in-the-eddy-ai-search-feedback-export .)

One of our customers is requesting for an option to export the HTML content in the Markdown format.

When you export a project/workspace including the media files from the Drive and import it to another environment, for example, a sandbox, the original folder structure of the Drive is lost. All images are put into Images\Documentation. The same folder structure on Drive should be restored when importing media files.

We would like to request a feature that allows users to export the entire project/knowledge base articles into a Microsoft Word (.docx) format.

Currently, RTL content works correctly in the Advanced WYSIWYG editor, but it is not supported in the Markdown editor. The customer is using Markdown articles and would like this RTL feature to be available in offline documentation as well.