What's New in Paligo?

The October 2020 release brings some major additions to Paligo, most notably, the long-awaited Paligo API. We also have new integrations for ServiceNow and Microsoft Teams, support for multi-level sections in Zendesk Enterprise, and much more. Read on ...



Yes, the Paligo API is here! Now your developers can connect external applications to Paligo and automate a variety of tasks, including:

  • Remote publishing

  • Remote editing of XML

  • Remote imports.

The REST API is available on the Business plan and up. For an overview of the Paligo API and information on how to generate an API key, see Paligo API.

For the developer documentation, see https://paligo.net/docs/apidocs/.

XML Tree View for easy structuring in the editor

We've added an XML tree view to the Editor's sidebar to make it easier to and move and restructure the block elements in a topic. The XML tree view shows the structure of the currently displayed topic and you can easily drag and drop elements around. The editor view instantly updates to match the structure in the XML tree view.

XML Structure view shows your content in a tree structure. On the left, there are blue tags for each element in your topic and these are nested to show the different levels of content.

The XML Tree View is available on all plans. To find out more, see Editor and Move Block Elements.

Collaborate on Technical Documentation in Microsoft Teams


Paligo now lets you collaborate with your teammates in Microsoft Teams, allowing you to send direct messages to other users, as well as get notifications of assignments, document shares, comments, and publishing events. With the Microsoft Teams integration, Paligo can send two types of notification:

  • "Personal" notifications to each user. These appear as chat messages in Microsoft Teams

  • "Channel" notifications to a Microsoft Teams channel of your choice.

So if your team uses Microsoft Teams for communicating with each other, you can now get your Paligo information there too!

The Microsoft Teams integration is available on the Business plan and up. To find out more, see MS Teams Integration.

Publish to ServiceNow


We have also added support for ServiceNow, with a new integration that allows Paligo to publish content directly to the ServiceNow platform. So you can use Paligo's powerful authoring features to create your content, but use ServiceNow to present that content to your audience.

The ServiceNow integration is available on the Enterprise plan. To find out more, see ServiceNow Integration.

Publish to Multiple Levels of Sections in Zendesk Enterprise Guide

Paligo now supports publishing content to mulitple levels of sections in Zendesk Enterprise Guide (available on the Enterprise plan). For example, you can now publish to a structure such as Category > Section > Section > Section > Article rather than the traditional Category > Section > Article.

Zendesk Preflight showing the topics in a list on the left with tags that indicate what those topics will be in Zendesk.

Publishing from Paligo to multiple sections in Zendesk is available for customers on the Paligo Enterprise plan. And you must also have an enterprise license for Zendesk too.

To find out more, see Zendesk Enterprise Layouts.

Other enhancements and fixes

There are also a number of other enhancements, bug fixes, and other updates in this release.

  • Algolia search

    The Algolia search bar did not support Internet Explorer 11. A workaround has been added to solve this.

    There was a bug where the Algolia JSON would miss some taxonomies. This has now been fixed.

  • Context-sensitive help support for a "not found" topic. You can now mark a topic's section element with xinfo:appid='not_found'. The topic will then be displayed if a context-sensitive link calls the website using an appid that does not exist.

  • Contribution editor

    If you had an emphasis element inside of a link it would get removed after saving. This has now been fixed.

    There were some issues with list elements in the contribution editor. This has been fixed.

  • DITA import process. We have streamlined the DITA import process so that there's much less preparation required.

    To find out more, see Importing DITA.

  • Editor icons update

    Some new glyph icons have been added to the editor icons widget.

  • Error message fixes

    In some situations the editor would incorrectly show an error message when trying to insert an element in a paragraph. This has been fixed.

    For a short period of time, a small amount of users may have received error messages when working with structure revisions. This has been fixed.

    Made some error messages more descriptive.

  • Glossary improvements

    For PDF outputs, you can now get your glossary to only include glossary terms that are actually used in your publication. For example, you could use the same glossary for a guide aimed at novice users and a guide aimed at technical users. Previously, the glossary would contain all terms for both guides, so novice users may see technical terms that are not intended for them. Now, the glossary can be set so that it only includes terms that are in the publication, either in the topics or referenced in the glossary itself.

    To set a PDF glossary to only include used terms, add the role attribute to the glossary element and set its value to auto.

    We have also fixed an issue where Glossary titles would cause an issue in PDF outputs.

  • HTML Help Center output back button fix

    Two back button presses were required to go to the previous page after opening an HTML5 Help Center output. This has now been fixed.

  • HTML5 outputs

    Reusing a publication in multiple places in another publication could cause issues with the HTML5 table of content links. This has now been fixed.

  • Hyperlinks

    Some users experienced an issue where links required two clicks to open. This has been fixed.

    External links now automatically use any selected text as the label.

  • Integration settings fix

    When entering incorrect settings, some integration panels would sometimes get stuck in a loading state. This has now been fixed.

  • Lightbox feature in HTML5 output disabled for Internet Explorer 11 due to incompatibility issues.

  • Notifications

    In some situations the “All comments” document notification option wasn’t working. This has now been fixed.

  • Output file names with multi-byte characters

    Better file names for outputs that contain multi-byte characters (ex: emojis, non-latin script).

  • Output taxonomies as class names now applies to images

  • PDF output

    Improved styling of admonitions inside lists.

  • Publishing

    The Combine languages option is now only selectable if multiple languages are selected.

    The Branch selector for the integrations that use “Upload output” would sometimes be empty in the publishing window. This has now been fixed.

  • Release status

    The Change status for all included components option now works even when not changing the release status of the publication.

  • "Request a Feature" link added to Paligo's Help menu

  • Salesforce integration

    Salesforce integration now has Custom link prefix setting that allows you to customize how your cross-references will look in Salesforce.

  • Search snippets no longer include the keywordset element

  • Slack integration

    The “Download logfile” link in the Slack notifications was incorrect. This has been fixed.

    There was a broken link on the Slack integration settings page. This has been fixed.

  • Topic titles now support double byte space character

  • Top-navigation links now allow language selection.

    You can now define what links should be visible in the top navigation depending on the language. Use the lang attribute.

  • Translation improvements

    There were certain special characters that would cause issues with the  XLIFF import and export. This has been fixed.

    Nested topics with profile attributes were not rendered properly in the translation interface. This has been fixed.

  • Upload SVG files in the layout editor There was a bug here that has now been fixed.

  • Zendesk integration

    A document that was deselected in Zendesk Preflight would still be published sometimes when publishing multiple languages. This has been fixed.

    In some situations the Zendesk “Test connection” option would say that the connection was successful when it was not. This has now been fixed.