Why software documentation needs more than words In software documentation, images aren’t optional: they are essential. Screenshots help users confirm that they are in the right place. Icons guide them through actions without language barriers. Diagrams clarify workflows. And mock-ups? They future proof your content when interfaces change faster than you can update a support page. But visuals must be purposeful: too many screenshots clutter, outdated ones mislead, and poorly edited photos...

(while Flow shapes understanding!) A process flow brings the underlying architecture to life, doesn't replace it (and vice versa). In technical documentation, flows that use the Business Process Model and Notation (BPMN) standard serve a vital role: they clarify processes in a consistent way. What is BPMN? BPMN is a standard for the graphical representation of business processes. By using this notation, you represent complex processes as diagrams that will be clear to understand for...

At the Tekom Netherlands-Belgium 2025 cross-border event in Rotterdam tech writers from both countries (and some more) met with 3 million words living in MadCap Flare, multilingual maintenance work instructions in a CCMS, and a pledge for more video content in tutorials. All that on the 23rd floor, with an exquisite view of the sunny city of Rotterdam. But it wasn't that we had much time to enjoy that view. Instead, we took in Jori Hagevoort's (ChipSoft) step-by-step build-up of how his team...