Paligo Technical Writer
Your search for a technical writer with Paligo experience is over! I started working with the cloud-based authoring tool in 2016, and quickly came to love its many content reuse features. If you've never heard of it, I'll give a brief overview below. If you have Paligo and need some technical writing assistance, here's what I can do for you:
- Plan and implement your Paligo documentation from scratch
- Write Paligo content taking full advantage of topics, informal topics, examples, etc.
- Use content reuse features to reduce your documentation costs in the future
- Take advantage of variables so that changes to product names etc. can be handled quickly and easily
- Enable/Disable 'Additional Links' on a per topic basis (with a little customisation courtesy of Paligo)
- Write and design Paligo HTML5 help, including customising the CSS
- Organise publications for exporting to other formats and systems, including Zendesk.
I'm a fan of Paligo and started working with it in 2016. I've also written about Paligo in the award-winning Communicator magazine, which is the journal of the ISTC.
What is Paligo?
Created by ex-DITA consultants in Sweden, Paligo is a cloud-based XML component content management system. It uses a topic-based customisation of the DocBook XML schema and is designed to make it easier for technical writers to create structured content. Although its a tool that's used online, the output that it generates can be used offline.
The main reasons my customers choose Paligo are:
- It is not vendor-specific. If you needed to move the content to another product in the future, that's not a problem.
- It produces smart, modern-looking online help and PDFs.
- Paligo can export to Zendesk, so content can be written once in Paligo and used for PDF, online help, and customer support centre articles.
- It is topic based and uses structured content.
- It supports markdown, which is popular with developers.
- It has powerful content reuse features. These can dramatically reduce the cost of updating content in the future.
- It makes it easier to write structured text. I was able to create content without any knowledge of the DocBook schema.
I'll Save You Money with Paligo's Content Reuse Features
I'm always banging on about content reuse. And for good reason - it can save you a lot of money. If you're not already familiar with this concept, content reuse allows writers to create a piece of text once, and reuse it wherever it is needed. Then, if the content has to be updated or changed, I make the change once, and it applies in every topic that contains that same piece of text. It's much quicker, and so saves me time, and you money.
Paligo has lots of impressive content reuse features, and I when I start your project, I will make sure they are used effectively. This needs some planning ahead, as there's no 'one size fits all' approach to content reuse. But thanks to my experience on past projects, I can create a plan for you very quickly.
It's not just about the plan, though. If a piece of content is going to be used in lots of different topics, it has to make sense in each of those topics. Writing your content so that it conveys meaning without being too tied to one particular place can be tricky, but it's something I've been doing for years, so your content is in good hands.
On a recent project, Adaptable Blotter, I used Paligo's topics, informal topics, examples, notes, tips, and content fragment features to make the content modular.
Each topic takes advantage of content reuse features, and there's a variety of content that's reused, including tables, descriptions, and individual steps in procedures. When the content needs to be updated later, it will be so much easier to apply the changes, as each alteration can be made once, in one topic, and it will be updated wherever that topic is used.
If you want to get your Paligo project started, or already have a live project and need a technical writer who knows his way around the product, please get in touch. Let me know what you need and we'll take it from there.