Feature Request

If you generate a multi-article PDF from Portal > Content Tools > Import & Export > Export to PDF, you can only include published articles in the file. It would be great if I can create a file with unpublished articles retaining the same structure in the Potal.

Customer has requested the ability to export multiple selected articles into separate PDF files, instead of generating a single combined PDF. Currently, the "Export to PDF" feature only provides one consolidated file. This enhancement would allow users to download each selected article as an individual PDF file in a batch operation.

With the migration to Aspose for PDF generation, the Table of Contents now has wider line spacing, making it less compact and reducing readability, particularly for larger documents. A narrower line spacing would improve readability, make better use of space, and provide a cleaner, more organized layout. It would be beneficial to reduce the spacing or provide an option to configure the Table of Contents line spacing based on user preference.

When the HTML content size exceeds the 25 MB limit, currently the system displays the following generic error message: "Failed to export PDF". Instead the system should display a clear, specific, and user-friendly error message such as: "PDF export failed because the HTML content size exceeds the maximum allowed limit of 25 MB. Please reduce the content size and try again." This would help users immediately understand the issue and take the appropriate steps to resolve it.

We imported a branded PDF to Word and then into Document 360 and the advanced WYSIWYG editor did a good job on the conversion. While there are branded styles that we can include in the CSS and HTML, my client is very concerned with PDF export. I will share one of their manuals and provide the assessment of the limitations in your current PDF export. Very limited flexibility around branding, on the PDF export template, for example, on the cover page, the logo width is limited to 300 pixels, on subsequent pages, the header is limited to 300 pixel width as well. Most platforms that feature PDF export would allow you not only a header image, but a left and a right header image, they would also allow you to have a footer image at the bottom. If there was a way to put full length headers and footers to the edge of the page like you do in Word for example, we could simply add three images for those and be able to brand the document. We are doing a lot of work in Document 360 so when we exported a markdown manual to PDF to see how quickly we could convert to advanced WYSIWYG, we were alarmed to find that the PDF that gets exported, loses mass amounts of the content when that PDF is opened in Word (which is what you must do to import in WYSIWYG. This is giving my client a huge pause for thought, that all the work we are doing will essentially have to be done all over again if we leave the platform. My clients are asking me for what specifically is going to improve in the PDF export and they want an ETA on that as well. I sent the PDF to Ramesh as file size was too big here. Thanks, David Forbes, The KYO Group

The process to export articles into a PDF is unreasonably obtuse, and is severely lacking in the features necessary to produce a professional looking document of a web-based document. Currently if you wanted to create a singular PDF of several Articles, you would have to first publish the articles, and I cannot find reason why that should be necessary. Additionally, the template UX/UI for exporting PDFs is missing a lot of the configuration options I would expect to see. Much of the formatting such as font type is not configurable when trying to export published articles and fonts used on articles are not maintained in the export. However, when exporting a singular article from the Preview page, font and style choices are maintained in this export process. It would improve the exporting process a great deal if PDFs could be generated using multiple unpublished articles, and they kept their fonts and style formatting in the export. Additionally, trying to create a decent looking PDF from web-base documents is quite difficult. The articles being created with HTML which does not-nor does it need to-account for text and images fitting properly on a standard size paper. This means there really should be an easier way to preview what an article would look like on standard document sized pages. Users should not have to create a preview page to generate an export just to to determine if images are of an appropriate size or if there are any awkward cutoffs of text. Each adjustment means creating another export to confirm the layout is fixed, and more time spent finding workarounds for lacking features

Currently there is an option to add header images while customizing the PDF export. There should also be an option to add text in the Header section so once can add company name, brand name or any text.

Allow adding variables to PDF cover page title and description, and T&Cs.

We have a use case where we would like to export only specific sections or headings from an article and share them with our team. Currently, when using the Export to PDF option on the site, the entire article is included in the exported PDF. We would like the ability to select and export only certain headings or sections instead of the full article. Thank you.