Feature Request

When importing articles, usually there is only word documents. But apparently our existing files are in PDF already. Converting the whole documents into word document always resulting the article to be slightly untidy (some of the pictures turns into code and some of the heading turns into code too) therefore maybe it would be helpful if our pdf documents can be imported directly without making the whole document becomes untidy that we need to tweak the articles manually through HTML coding to look exactly as the pdf we have. Thank you

Hello, We would like to have the ability for our team members to export articles from the Knowledge Base Portal as a Word Document for our internal use. This is different than allowing users/readers to download articles as Word documents which would not be wise in our case for confidentiality purposes. Thank you!

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.

Add ability to import translated articles via word document.

When I import a Word doc with numbering, the numbers get mixed up, and the numbering begins again after an image, so I have to renumber things manually.

PDF files seems to be very big. When acrobat is integrated with other applications, there is some configuration that makes the exported files smaller, compresses graphics etc. So request to configure the PDF generator behind the scenes to optimize file size, compress graphics and other things that can be compressed to create smaller PDF files.

At present, the exported zip file and the article within it do not include tag details. The customer has requested that article tag information be added to the metadata in the article's HTML. Currently, the only data available in the HTML metadata is as shown below. The goal is to include the tag details in the metadata as well.

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.

When exporting a knowledge base, include workflow status, publication status, and any comments on each article, so that import restores all of these items for each article. Currently an import causes you to lose all of this.