Techcomm experts reveal their three most favorite writing tools

by Uta Lange on August 30, 2016

Sabine Stoye, technical communicator at parson, recently participated in an exciting survey. Ferry Vermeulen's one and only question was: If you could use just three technical writing tools in your company, which ones should you use?

Ferry Vermeulen (INSTRKTIV) asked 70 Techcomm experts. The list of names is impressive and looks like the Who's Who in technical communication. The top ten tools are at the end of the article. DITA (if you include oXygen) ranks second, which pleases us a lot.

http://instrktiv.com/en/technical-writing-tools/

What are your three favorite writing tools?

Add new comment

The iiBot gives instructions

by Uta Lange on November 07, 2019

In a joint project with Endress+Hauser, tcworld has developed an iiRDS-based chatbot demonstrator. more...

Recommend+To? A Clear Recommendation

by Uta Lange on March 01, 2018

In technical documentation, we avoid recommendations. They rarely help the reader: The producer recommends ultra-light power cells. Why? What happens if I use others? more...

iiRDS – How a Novice Sees the Information Delivery Standard

by Judith Hallwachs on February 20, 2018

Lately, the newly developed tekom standard iiRDS has gained quite some attention. The next exciting step will be the release of version 1.0, which will be released soon. Requesting and delivering intelligent information as a standardized approach is a pioneering step in the Internet of Things – but let’s rewind a little. more...

Technical documentation and search engine optimization.

by Dr. Markus Nickl, doctima on April 26, 2017

Search engine optimization is a broad field. SEO agencies seem to be everywhere. Still, the technical documentation industry has not quite recognized the potential of search engine optimization. Why is that? more...

API documentation – What software engineers can teach us

by Stephanie Steinhardt on January 30, 2017

When asking software engineers about API documentation, you soon find out that there are two groups. The first group is convinced that good code does not require any explanation. Members of the second group frequently read documentation and even enjoy writing it. You also find out that software engineers have completely different opinions and approaches when it comes to the layout, presentation, and contents of a perfect API documentation. more...