Feature Request

When exporting multiple categories in HTML offline documentation, all articles are merged into a single docs folder with shared assets and one index.html. The category-level structure is not preserved. Problem / Use case We manage ~26 modules where each category or subcategory maps to a module in our help center repository. The exported HTML is not used as-is and needs to be pushed into a structured repo. Since the export flattens everything, each writer has to export categories individually and manually merge them, which leads to repeated effort and multiple deployments. Expected behavior Allow exporting multiple categories such that each category is preserved as a separate folder (with its own docs, assets, and index.html) instead of merging everything into a single structure. This should align better with repository-based workflows and reduce manual effort.

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.

When importing Word documents generated from Google Docs entire table is rendered as table headers and they are in bold formatting. It would be great to have the table in a normal paragraph formatting.

Improve the Word import behavior to preserve ordered list numbering when lists are interrupted by images or headings. Currently, due to a limitation in the Mammoth Word import plugin, ordered lists that appear between headings or are interrupted by images may not retain their original numbering during import. The enhancement would ensure that hierarchical list numbering from Word documents is preserved correctly during the conversion to HTML.

When a user exports a project with the outline feature enabled, all article outlines should be preserved. Upon importing that project into another project (where the outline feature is also enabled), the outlines should remain intact and fully functional.

We maintain two workspaces for different customer needs and sync content each release by exporting and importing projects. After the first import, incremental imports create duplicate articles instead of updating existing ones. Also, current replication supports only single-article replication, not bulk or category-level operations. Enhancement Requested Bulk / Category-Level Replication: 1.1 Ability to replicate multiple articles or entire categories (including hierarchy and metadata) between workspaces. UUID or Persistent Identifier Support: 2.1 Match articles during incremental import. 2.2. Update existing articles instead of creating duplicates. 2.3 Add only new articles that don’t already exist.

It's inconvenient to have only a 15MG limit when I import a Word Doc in IMPORT/EXPORT --> IMPORT ARTICLES. Please increase this limit. It's 2023, 15MG is NOT that large. :) Thanks.

The current library used for Word Import has limitations. Tables inserted from Google Docs are rendered as table headers and font, background colours are not retained in the table after import

When a PDF file is uploaded to Drive, and its link is inserted into an article, exporting the article to PDF preserves the link correctly. Clicking the link opens the file as expected. However, the generated URL includes a SAS token (Shared Access Signature). Once the SAS token expires, users receive an AuthenticationFailed error when accessing the file. Currently, the SAS token remains valid for approximately 8 hours, after which the link breaks. Expectation - The nested PDF file should be active at all times