What's New in Paligo?

In this release, we have some exciting enhancements to Paligo versioning, publishing to Azure repos, better spell-checking, and not the least, a great new integration to improve collaboration in your team. Read on...

Collaborate on technical documentation in Slack


Paligo now lets you collaborate with your teammates right in Slack, allowing you to send direct messages to other users, as well as get notifications of assignments, document shares, comments, and publishing events to your Slack workspace. The Slack integrations has two types of notifications:

  • Send "personal" notifications to each user. These appear as messages sent from the Paligo app.

  • Send notifications to a channel of your choice in a Slack workspace.

So if your team uses Slack for interacting with each other, making video calls, etc., now you can get your Paligo information there too!

To find out more, see Slack Integration.

Publish to Microsoft Azure Repos


A while ago we released the popular feature to publish to GitHub, BitBucket, FTP, and Amazon S3.

Now we're adding to our growing number of publishing channels with Microsoft Azure Repos. Create content in Paligo and publish directly to any Azure Repos project and branch.

To find out more, see Azure Repos Integration.

Revision history and roll-back for Publications

We've made it much easier to work with revisions for publication structures, so if you change a publication structure, it's now much easier to revert back to an earlier version if needed. This is going to make it much quicker to modify your publications, as there's no need to recreate a previous structure from scratch.

Every time you make a change to a publication structure, Paligo will store a revision. You can then revert to that revision (or any previous revisions).

Paligo will even recreate topics from that publication revision if they had been deleted.

To find out more, see Revert a Publication to a Different Revision.

Faster, More Reliable Spellchecker

Many of you asked for a more robust spellchecker, so here it is! For the new spellchecker, we have taken a different approach and have built it almost from scratch. The result is a spellchecker that's faster, more reliable, and more stable.


Other enhancements and fixes

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

  • Manage image resolution for HTML publications. You can now set the resolution for all block images in your HTML publication. You can choose to exclude all images, use their original resolution, or use one of several resolution options. For example, you may choose to publish your images in lower resolution so that your website loads more quickly.

    To find out more, see Image Resolution.

  • Hide topics from the default HTML search engine. Have you ever wanted to include a topic in an HTML publication, but stop it from appearing in the search? Well now you can! You can exclude a topic from the search by giving the section element a role attribute with the value: notinsearch.

    To find out more, see Exclude a Topic from Search (HTML).

  • Improvements to XLIFF import (no importing empty fragments)

  • Added notification text to the Dashboard when the user password is about to expire

  • Update to source code editor in the Paligo XML editor.

  • Much faster performance when saving structure changes on large publications

  • Email notifications. Sometimes email notifications sent to users contained garbled characters. This has been fixed.

  • Translation view comments. Translation view comments sometimes stopped working. This has been fixed.

  • Review interface. Certain punctuation and diacritics were not visible in the review interface. This has been fixed.

  • Search function. The search function did not work for output with certain language combinations. This has been fixed.

  • Annotations in Search. Search data in HTML5 output contained annotation content. This has been fixed.

  • Callout code listings. These were not working on HTML5 output when syntax highlighted was enabled. This has been fixed.

  • HTML5 help center output. This output was not working correctly when a certain combination of reused HTML5 help center layouts was in place. This has been fixed.