Feature Request

To make tables render in a controlled way and similar in both web views and in PDF exports I suggest a “WYSIWYG behavior for table sizes and column widths“. This could also be made as a setting such as “use manually set table column widths in all media”. Why? All is related to support ticket #306539 "PDF export show truncated right column" Experimenting with a tremendous number of tables I now realize that the Doc360 system is automatically adjusting tables to a set standard (?). Trying to get tables to look similar in both web and PDF exports I attempted to: 1. use the recommended % width instead of px for max width and column width. 2. avoid multiple inline CSS attributes 3. minimize any included images’ sizes. All above was done to tables which were: 1. created from scratch 2. copied from other articles with correct looks in PDF. 3. imported from other media The unwanted result looking back into the code after publishing were always the same: • set % sizes are swapped into the not recommended px • column widths are either disregarded or not interpreted as a number, resulting in string such as colwidth="NaN". • PDF export remained living its own life, showing the unacceptable truncated right column ... Attached are sample screenshots of the readers view, the editors view, and the from the PDF export causing all this to be investigated. Code samples exists but I suggest that a Doc360 expert try scenarios above.

It would be great if we have an option to customize the H1, H2, H3 and H4 font sizes in the text settings of the PDF template. Currently, Document360 doesn't allow the users to set the heading font size for the PDF templates. At times, there are confusions between H1 and H2 in the exported version.

This request was created on behalf of Oren Currently, users are unable to export a parent page-type category or the category alone when exporting only a few selected child articles from the knowledge base site. It would be beneficial to support the ability to export selected articles along with their associated page-type categories, as well as the option to export just the page-type category independently. Thank you.

Currently, when exporting articles to PDF, only the Table of Contents (TOC) links navigate within the PDF itself. Any links placed inside article content redirect to the Knowledge Base site in a browser instead of referencing the relevant section within the PDF. This creates a limitation for users who rely heavily on PDFs, as they expect in-article links to also work as internal cross-references within the exported document.

The customer would like to have the option to export PDFs in US Letter size (8.5 x 11 inches). Document360 supports the A4 paper size (8.26 x 11.69 inches) by default.

I use a lot of custom CSS in our knowledge base. For example, I make it so that a border around images appears as a thin blue line instead of a thick gray line, and I've changed the color of the info callout box from blue to transparent. However, when I export to pdf, that styling is lost. There needs to be a way to apply the custom styling to exported PDFs.

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

When I need to export my documentation to PDF, I must split it up into multiple exports due to Document360 limitations. Needing to wait for one export to complete (often 30 minutes) before I can start the next export request makes it a very difficult and time consuming task. I should be able to start one export, and while that export is happening start another export.

Submitting this feature request on behalf of the customer (Deepak from Blueheer). The customer reported that the customizations added to the callouts are not rendering in the PDF as they do on the user website.