I appreciate Author-it Cloud because it is a one-stop-shop with all the required tools integrated. I also appreciate how simple Author-It is to use, making training very quick. I've been using it for twenty-one years, and I love its capability. The authoring tool is great, and I like the new web interface because it's quicker for logging in and you can publish from there. I love that we can write once and publish to 30 brands, translating once to publish across those brands. The JSON output for integrating with Microsoft 365 Copilot is something I'm loving as it helps with better reuse of instruction manuals. I also love Author-it Xtend, which is kind of like a translation memory for the English, which is strong at reusing content at the fragment level, reducing translation costs. And reusing at the topic level is as simple as drag-and-drop.

For more than 20 years, I have used Author-it to create and maintain documentation for a large ERP system. One of its greatest strengths is its object-based, single-source architecture, which enables extensive content reuse and significantly improves the efficiency of the technical writing process. By maintaining content as reusable objects, we can quickly produce consistent, accurate documentation across multiple product releases while minimizing duplication and maintenance effort.

I love how Author-It allows us to maintain multiple versions through variants and define metadata easily with variables. I really appreciate the content reuse feature, which means we can write or update once and it updates everywhere it's embedded automatically. The documentation localization process is also very easy to manage. I also like the ability to standardize templates and styling so those decisions are made only once, along with the ability to publish to multiple outputs. Additionally, I find it easy to publish to Fluid Topics for hosting on the web, and I value the localization manager. The initial setup of Author-It was very easy, even though the migration took some time due to many topics, but that was expected.