Sustainable Content for Software Documentation Powered by Simplified Technical English
summary
Adopting Simplified Technical English (s-t-e 100) claims a measurable payoff: a conservative 20–40% text reduction that cuts translation cost, improves machine translation quality and post‑editing, and yields noticeably higher readability. Practical moves include swapping continuous tense for simple present, preferring verbs like show instead of displaying, and using consistent wording such as select the compartment where…. Short workshops (two–three days) and 70–80% compliance for software teams deliver the bulk of benefits without full standard conformity.
AI-written summary · about
chapters (8)
- 0:00Simplified Technical English intro
- 3:18Breaking down complex ideas
- 9:24Simplified English in software documentation examples
- 13:48Sustainable content benefits
- 20:42Managing STE authoring teams
- 23:56STE adoption case study
- 28:14Cost savings with STE
- 31:29Q&A
related talks
44mWriting Technical Documentation in a Lean Style
13mTechnical documentation – how can I write them better and why should I care?
28mHumanizing Your Documentation
37mHumanising Your Documentation
40mHow to Write Documentation for People That Don't Read
18mTechnical Documentation - How Can I Write Them Better and Why Should I Care?
44mTesting Documentation: Why So Technical?
34mDocumentation Thinking Beyond the Docs: Lessons from Decision-Facing Technical Writing