We use Paligo as our mission-critical authoring tool. It is a CCMS that enables our globally diverse team to work together to create various documentation deliverables in a topic-based method, with different writers working on the same publication, the same chapter, and sometimes the same topic in an efficient and consistent manner. It is based on the open-source DocBook schema, so if you change your mind a few years down the road, you are not locked into Paligo but can migrate with minimal expense and time. Paligo does single-sourcing better than other CCMS tools, creating beautiful PDFs out of the box and with easy customization, HTML5 for product Help, Word, SCORM, and more. It integrates perfectly with Zendesk, letting us push out 100s of new articles and articles updates in minutes. It has integration with AWS S3, GitHub, Memsource, and many other third-party tools for delivery and storage. L10N features are built-in and easier to use than in other CCMS and CMS tools. Variables are centralized and easy to manage with variable sets and variants for parallel publishing to OEMs and simultaneous versions. It has an easy-to-use XML interface if you want to get into the backend, and a nice WYSIWYG interface if you want to create content simply. The best thing about Paligo is its Best-In-Class Support and Customer Success. Actually, it's everyone at Paligo. Though Paligo has grown in the past couple of years, it still offers the awesome responsive expert solutions that it did when it was newer. For any team of technical writers, I highly recommend Paligo.