![]() The platform itself is super intuitive, as is the publishing workflow. Since all of our content is currently unstructured, the trainer will also be workshopping our content directly with us to ensure we can hit the ground running. We decided to get a license for my team and we are also bringing the Paligo trainer down to train my team on advanced features (like versioning and localization), best practices, and strategies. It's also clear they are really passionate about their platform and its benefits. The rep I've been working with (Steve) and the support people who answered my questions have all been incredibly responsive and also quite knowledgeable about how to manage the ZenDesk integration effectively. The Paligo trial has been super interesting and a great learning experience (I basically got a crash course in structured and topic-based authoring in the last month and a half, which has completely changed my perspective on how my company has been doing things - shout out to the Write the Docs community for chatting with me and sending me tons of great content). With content reuse, all you have to do is update one piece of content and the changes are deployed across multiple articles. And with articles spanning multiple categories or sections, we have to hope that running a search on Zendesk tells us all the places where we need to update certain content. Without content reuse, we have to manually update those five articles whenever a URL, definition, or procedure changes. So anytime we drop that shortcode in an article, the ordered list generates automatically. With content reuse, we can reference that ordered list with a shortcode. ![]() Let's say we have five articles that all include these steps:
0 Comments
Leave a Reply. |