What's New in Paligo?

This release includes a variety of new features and enhancements, and we've especially got some exciting updates regarding publishing directly to your delivery platform as well as great performance upgrades. Read on...

Publishing to a Git Pipeline or Directly to Your Web Server

We know many of you have been asking for this and looking forward to this for a long time. With this release it is now possible to publish directly to your web server via FTP. But not only that, now you've also got direct integration with three additional popular platforms and Git workflows.

All of these options will allow you to fully automate the entire publishing process to go live with your content as soon as you hit the publish button.

Publish Directly to Your Web Server Via FTP

ftp.png

If you're publishing to your own web server, you can now greatly simplify and automate the publishing process by directly pushing your content there via the direct FTP publishing option.

See FTP Integration for more on how to do this.

Publish to Amazon Web Services S3 (Amazon S3)

awss3.png

Paligo now offers publishing directly to the very popular Amazon Web Services S3 (Amazon S3). This means you can create content in Paligo, such as PDFs or an HTML help center, and publish it to Amazon S3 so that it is instantly live to your end users.

See Amazon S3 Integration for more on how to do this.

Publish to BitBucket

bitbucket.png

For you Continuous Integration fans out there, now you can get your Paligo publishing right into your Git workflow. Publish directly to any Git branch you choose, and then automate the publishing with BitBucket Pipelines so it's instantly live for your end users.

See Bitbucket Integration for more on how to do this.

Publish to GitHub

github.jpg

Just like the BitBucket integration, those of you who work with GitHub can have the same Continuous Integration workflow, publishing your Paligo content directly to any branch. Automate the publishing (or any workflow you need) with GitHub webhooks.

See GitHub Integration for more on how to do this.

Greatly Enhanced Performance

The team has been working a lot on the backend of Paligo, updating, tweaking, and fine tuning on every end to make your Paligo experience as great as possible. With this release the performance will be significantly enhanced overall, and you'll see a noticeably snappier interface.

Paligo performance enhancement

This update is part of a larger infrastructure project that is still ongoing, and there will be further enhancements in the near future too.

Other enhancements and fixes

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

  • Batch translate multiple languages. It is now much easier if you translate to many languages, to just select all the languages you need and download a zip of the XLIFF or send it all to a translation integration like Memsource. When importing languages, there is also now an option to disregard the translation status of completed segments, to import the entire translation and overwrite existing completed segments.

  • Salesforce Sandbox publishing. If you're using the Salesforce integration, and need to be able to publish to a Salesforce Sandbox environment, you now have support for that too!

  • Improved pasting of HTML into the Contributor Editor. Using the Contributor Editor, you can paste HTML and get it converted to XML. There were some issues with some kinds of HTML, for example if copying and pasting "ReadMe" files from GitHub. This has now been greatly improved making it easier to get such content into Paligo.

  • Reader-Friendly Hash Links (Fragment Identifiers). You know when you have an anchor link you copy for a title in the middle of an HTML5 page? Those used to only be available as unique ids, in order to support the many complexities of reused content. However, now there's an option to create prettified hash links. Enable it in the Layout Editor if you want to use this.

  • Better cleanup of completed/old assignments. Assignments could hang around on the dashboard for quite a while, even though completed. This has now been fixed.

  • Bug fix for duplicate section TOC. For a brief period (a day or two) there was a regression bug that caused the section TOC to be added twice at the bottom of an HTML5 page. That was no good, so it's been fixed!

  • Option to exclude internal sections from TOC and bookmarks in PDF. If you're publishing to PDF, and don't want internal section titles (inside topics) to show in the Table of Contents or bookmarks, there's now an option in the Layout Editor to exclude them.

  • Bug fix for sub menu in Zendesk when using accordions. If you're using the Paligo Zendesk asset files to get the sub menu for articles, there was a bug if using accordions as well. This has now been fixed if you update your account with the asset files in the Zendesk output zip.