Feature Request

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.

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

At times, the export failure status does not update in the UI for large content. After triggering the PDF export, the status is in progress, but after the background job completion, the success/failure status is not appended. While regenerating the same template, the status is updated with a success or failure status.

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.

Hi team, Raising this feedback on behalf of Panaya. When importing a .docx file into an existing empty article, the system automatically overwrites the article title and slug based on the file name. This happens even when the user has manually set the title and slug earlier. Customer's workflow and concern: The user creates an empty article with a specific title and slug. They often share this slug/URL with their R&D team for integration on the Panaya application. After a few weeks, they import content from a Word file into the same article. The DOCX import unexpectedly overwrites the article title and slug. This breaks previously shared URLs and causes confusion Customer expectation: If the title and slug were manually defined, the import should not overwrite them, or the user should be prompted before changes.

The export project tool does not include snippets. We rely on snippets - considerable % of our content is contained in them - and need to have them included in the exports that we capture weekly as a part of our DR mitigation plan.

I would like to import .docx documents as article in the format of Markdown instead of HTML. Alternatively a HTML to Markdown converter would also work.