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.

I like how I can reuse books, topics, and parts of topics to create online knowledge bases for different audiences. It's also incredibly helpful that hyperlinks are objects so it's easy to identify the impact of removing a target topic.