Docs Like Code – Interview with Anne Gentle

Here is early access to the latest episode on the Cherryleaf Podcast – Interview with Anne Gentle, author of Docs Like Code and Product Manager at Cisco. It will be published on the podcast channel on Monday.

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:

Subscribe to Cherryleaf’s newsletter

Cherryleaf training course – Advanced technical writing techniques

https://www.docslikecode.com/

Conversation and Community: The Social Web for Documentation

Troy Howard Documentarian, Super Genius at Twitter

http://codewerdz.org/ Repository analytics for code and docs

Matt Fleming on Twitter

Docs Like Code GitHub repository

Jekyll

https://docs.openstack.org/pike/

WADL RAML OpenAPI

https://bitbucket.org/

http://docs.metacloud.com/

Liquid scripting

YAML

PrinceXML

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

AsciiDoc

ReST

GitHub Flavoured Markdown spec

XML Press

REST API

Building Docs Like Code – article

Travis CI 

Jenkins

Circle CI

Webhooks

Bash scripts

An Introduction to Static Site Generators

GitHub Pages 

Delivering a digital strategy for Parliament – Interview with Rosie Hatton

From the Cherryleaf podcast: 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”

Links:

People:

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

Here is an interview we carried out with Mark Baker, author of Every Page is Page One. The interview is interspersed with audio snippets from Day 1 of the UAEurope 2017 conference.

Presentations:

  • Caroline Loverage (Thermo Fisher Scientific). Teaching by Example: Worked Examples in the Documentation of Complex Systems
  • Kelly O’Brien (Kayako). Practical Information Architecture: Building Templates For Better Content.
  • Helena Pichler (Nominet). AsciiDoc to Responsive Webhelp: Agile documentation for small teams/

With thanks to Matthew Ellison and Mark Baker.

The ContentHug interviews

I was asked to take part in the ContentHug series of interviews on technical communication and content strategy.

It was fun and challenging, going through the questions.

ContentHug’s Vinish Garg is interviewing a number of consultants involved in technical communication and content strategy, and asking them essentially the same questions. By reading the interviews, you can see where there are areas of agreement and where there are a variety of opinions. In general, there is a fair bit of consensus. They are worth reading.

What it’s like to be a Technical Author

We’re planning to carry out a number of videoed interviews with a range of Technical Authors this week. This is to help promote the profession. We’ll be asking questions such as what their role is inside their companies, and how they became a Technical Author.

The videos will be uploaded to the YouTube Channel for the Institute of Scientific and Technical Communicators, once we’ve edited and published them.