This site uses third party services that need your consent. Learn more

Skip to content


Paligo HTML5 help center




Software - Component Content Management System, Technical communication

Screenshot of page from the Paligo HTML5 online help. It shows the Workflow for Internal Translation page. It has some text, a diagram that shows the workflow, and subsections for each stage of the workflow.

I have worked on many projects for Paligo, mostly as a technical writer, but also as a customer support agent. So if you thought my name was familiar, it could be that I’ve helped you out in the past.

On the projects, I’ve used the Paligo CCMS to create help pages for most areas of the product, with the exclusion of API documentation (the devs do that). Some of the subjects I’ve worked on are:

  • General editing

  • Content reuse

  • Publishing

  • Filters

  • Variables

  • Layouts

  • Front covers and back covers for PDFs

  • Review and contribution assignments

  • Translation

  • Integrations with other systems such as Zendesk and Salesforce

  • Creating “super publications” (a complicated process!)

In fact, there aren’t many areas of the product that I’ve not written about.

I’m not the only technical writer who works on the documentation, so I can’t guarantee that all of the work you see in the help center is mine. But some of it is, and I’ve heard that it has helped customers and support staff get to grips with Paligo. Content that I wrote (or made as video) was also used as the basis for some of the training school content and certification content.

How I’ve helped

When I started working on Paligo projects, much of the content lacked detail. Some articles would tell users what to do and what features to use, but without explanations of how to get to the relevant settings. So my main contribution has been to try and make sure each article works as a standalone piece.

Working as part of a team, I also made extensive use of Paligo’s content reuse features to make it easier to create and update content. In particular, we made lots of informal topics so that commonly used steps in procedures could be written once and used in many places.

As a technical writer who uses Paligo for work, I am also very similar to an actual customer. So I’ve been able to make suggestions on UX and UX writing to help improve the product. And lots of testing too - I don’t like to write about a feature unless I have tested how it works for myself.

Headshot of Craig.

Craig Wright is an experienced technical writer based in Chesterfield, UK.  He hates writing about himself in the third person, so I shall stop now.

Always interested in new content writing opportunities. Remote working preferred.

Get in touch

Let’s talk about your project

I’m here to help and offer my expertise as a technical writer. Get in touch and let me know what you need.