It’s not quite 2018 yet, but here are our predictions for technical communication in 2018 and beyond. We also look back at the predictions we made for 2017.


Predictions for technical communication in 2017 and beyond

Five predictions for technical communication in 2016 and beyond

Docs Like Code - Interview with Anne Gentle

Every Page is Page One - Interview with Mark Baker at UAEurope 2017 

Cherryleaf website


Flickr image by byronv2 

November 14, 2017

If not DITA, then what?

We look at the pros and cons of using the DITA standard, and the alternatives.


Every Page is Page One - Interview with Mark Baker at UAEurope 2017

Interview with Tony Self - UAEurope 17

October 30, 2017

Books on technical writing

We look at some of the best books to read on technical writing.


Single Sourcing, Kurt Ament

Ron Blicq and Lisa Moretto

Minimalism Beyond the Nurnberg Funnel, John Carroll

Lean for Practitioners, Mark Eaton

Managing Your Documentation Projects, JoAnn Hackos

Information Development, JoAnn Hackos

Modern Technical Writing, Andrew Etter

Docs Like Code, Anne Gentle

Current Practices and Trends in Technical and Professional Communication, Stephen Crabbe

The Language of Technical Communication, Ray Gallon

The Language of Content Srategy, Rahel Bailie

Every Page is Page One, Mark Baker

Automate the Boring Stuff with Python, Al Sweigart

Don't Make me Think, Steve Krug

Rocket Surgery Made Easy, Steve Krug

Content Strategy: Connecting the Dots Between Business, Brand, and Benefits, Rahel Bailie and Noz Urbina

Content Design, Sarah Richards


Advice on writing a CV for Technical Author vacancies.



Cherryleaf - how to register as a candidate

Top 25 Content Experience Influencers 2017


We explore these questions from listeners:

  • What’s your opinion of Zendesk and Mindtouch? Someone in our company thinks it might be a good idea to explore the idea of moving our Help content  – have you heard of anyone doing this and then using it in a way of single sourcing etc? 
  • Our boss wants us to consider the idea of merging our Help content and our “Knowledge base” which is like articles/support troubleshooting etc. Whether this is our content going into the knowledge base or vice versa, we’re not sure in terms of direction. Do you have any opinions on merging article-based content like this into a Help Authoring tool or Help content into a “normal” website like that?


Just-In-Time Documentation: A Practical Guide to Agile Documentation

AI and chatbots in technical communication - A primer



Interview with Anne Gentle, author of Docs Like Code and Product Manager at Cisco. 

Interview by Ellis Pratt, Cherryleaf

Subscribe to Cherryleaf's newsletter

Cherryleaf training course – Advanced technical writing techniques

For comments and feedback:

Topics covered: 

  • What is docs as code?
  • Why do it?
  • When might this approach might be applicable?
  • The limitations
  • Docs like code in development sprints
  • Is it only for developer docs?
  • Do you you need to understand programming?
  • Why did you self publish?
  • The benefits of taking this approach
  • The future developments
  • Automating document builds

Links to topics mentioned:

Conversation and Community: The Social Web for Documentation

Troy Howard Documentarian, Super Genius at Twitter Repository analytics for code and docs

Matt Fleming on Twitter

Docs Like Code GitHub repository



Liquid scripting



Lunr Search Engine 

Solr (Search Engine)

Why we use a ‘docs as code’ approach for technical documentation Jen Lambourne, GDS, GOV.UK

The Definition of Done

Learn Python the Hard Way



GitHub Flavoured Markdown spec

XML Press


Building Docs Like Code - article

Travis CI 


Circle CI


Bash scripts

An Introduction to Static Site Generators

GitHub Pages 


Interview with David Farbey of the Institute of Scientific and Technical Communicators, about training, accreditation and CPD in technical communication.

We discuss:

  • Becoming a technical communicator is different from becoming a lawyer, doctor, developer or an accountant in that, in the UK, there is no standard career path from school. How does that affect the profession and starting a career?
  • What training, if any, do you need to be a technical communicator?
  • The ISTC's Professional Development and Recognition
  • Certifying technical communicators
  • The ISTC certified courses.
  • What does a undergraduate or post-graduate course offer someone?
  • Where does CPD fit into this?
  • What are we likely to see in the future with regards to training and certification?

Cherryleaf's ISTC accredited training course: 

ISTC website:

David's email: 


We look at the job of a Technical Author/Technical Communicator, and how you can start your career.

Cherryleaf’s online Technical Author/technical writing course


It seems likely artificial intelligence (AI) and AI-driven chatbots will play a key role in helping users in the future. So what does this mean for technical communicators and for User Assistance?

Part 1 - What are chatbots?

Part 2 - Making a chatbot

Part 3 - What does this mean for technical communicators and for User Assistance?


About the speaker

Ellis Pratt is a Director at Cherryleaf, a technical writing services and training company based near London.

He has over 20 years of experience working in the field of documentation, has a BA in Business Studies, and is an Associate of the Institution of Engineering and Technology. Ellis is contributor to two books on technical communication. He is also on the management council for the Institute of Scientific and Technical Communicators (ISTC), the professional body for technical communicators in the UK.

Contact information

More information

Primer article -


Robot image From From Wikimedia Commons, the free media repository.


The UK Parliament is one of the oldest organisations in the world. So how do you deliver a strategy to a body that has over 700 years of content? Cherryleaf's Ellis Pratt interviewed Rosie Hatton, Strategy Digital Lead at the Parliamentary Digital Service, to find out. 


Topics covered:

  1. What is Parliament? 1'56"
  2. The content Parliament creates. 3'38"
  3. What is the PDS? 5'08"
  4. The I AM PARLIAMENT programme. 9'00"
  5. The PDS's digital strategy framework, its assumptions and principles. 10'18"
  6. Having an open and agile digital culture in a traditional organisation. 13'08
  7. Working in a continuous interative process. 20'45"
  8. Sharing ideas with the Government Digital Service. 25'24"
  9. Where does the PDS's content strategy fit within its digital strategy? 28'22"
  10. Tracking the impact of changes to laws on other laws. 37'01"
  11. The similarities between PDS and Open Source software projects. 41'55"
  12. Crowdsourcing a digital strategy. 43'30"
  13. Benefits management. 44'00"
  14. How to manage and sell change. 47'50"


Parliamentary Digital Service blog (knowledge hub)





This is a recording of a 2012 webinar called "Recruiting the right Technical Author". 

For more details on Cherryleaf's contract and recruitment services, see


For comments and feedback:


Load more