⭐ The sites are inspiring me, that’s why they are in my favorites!
🔸 A good technical content should be:
- Technically true (that’s the minimum!)
- Balanced between necessary and useful information (you can type this, but you’d rather type that)
- User and action-oriented
- Clear for both native and non-native speakers
- Easy to translate
- Attractive
- Responsive
I use Adobe software for a long time. I started with Adobe Acrobat, then continued with Photoshop, PageMaker and FrameMaker. Now RoboHelp is an Adobe software too.
20 years later, Adobe offers a 🔗 complete solution 🔗 for technical authoring and communication. This is a sign that technical content is strategic!
However, my absolute favorite at the moment is 🔗 Markdown !
🔸 Technical Writing is also technical illustrating. As a technical author, you have to add screenshots to your words, diagrams and icons.
I started using PaintShop in 1997, at a time it was just a tool to make screenshots. It upgraded to a Jasc software, and now it is a complete Corel solution that provides so many features! 🔗 PaintShop Pro pretends being the “best alternative to Photoshop” and I agree with it.
This a great tool for great diagrams: 🔗 Draw.io
