thinking of documentation as code [yuiconf 2013]

18
Thinking of Documentation as Code Evan Goer YUIConf 2013

Upload: evangoer

Post on 22-Nov-2014

1.191 views

Category:

Business


1 download

DESCRIPTION

As a software engineer, one of the best things you can do for your documentation is to take the principles of code construction that you already know and apply them to your writing. We'll demonstrate how thinking about documentation as code will help you avoid many of the classic high level mistakes people make when launching documentation projects. This is a companion piece to last year's talk, which focused on how to optimize English prose at the micro level.

TRANSCRIPT

Page 1: Thinking of Documentation as Code [YUIConf 2013]

Thinking of Documentation as Code

Evan GoerYUIConf 2013

Page 2: Thinking of Documentation as Code [YUIConf 2013]

Frontend Engineer @ Intuit

And much more…

YUI 3 Cookbook Author

Page 3: Thinking of Documentation as Code [YUIConf 2013]

Thinking of Documentation as Code

Page 4: Thinking of Documentation as Code [YUIConf 2013]

Or:

Improve Your Documentation With This One Weird Old Tip

Invented by a San Jose dad!(okay no, not really)

Page 5: Thinking of Documentation as Code [YUIConf 2013]

A Fable

The Magical Unit Test Repository

Page 6: Thinking of Documentation as Code [YUIConf 2013]

Why do you tell me this when you know I will kill you for it?

Page 7: Thinking of Documentation as Code [YUIConf 2013]

“To first order, software documentation is like code.”

Page 8: Thinking of Documentation as Code [YUIConf 2013]

The radical notion thatDocumentation is part of your project

Just like your source code and build scripts

and unit tests and everything else

Page 9: Thinking of Documentation as Code [YUIConf 2013]

Documentation lives in your repo(just like code!)

Page 10: Thinking of Documentation as Code [YUIConf 2013]

Documentation source is plain text(just like code!)

Page 11: Thinking of Documentation as Code [YUIConf 2013]

Code is very expensive(documentation even more so)

Page 12: Thinking of Documentation as Code [YUIConf 2013]

Corollary of “Docs are expensive”:Given a choice between writing lots

of docs or fixing your code,fix your code.

Page 13: Thinking of Documentation as Code [YUIConf 2013]

Technical Documentation on the Wiki:Threat or Menace?

Page 14: Thinking of Documentation as Code [YUIConf 2013]

Don’t Allow User Comments on Documentation Pages

Page 15: Thinking of Documentation as Code [YUIConf 2013]

Separation of ConcernsWhat, How, and Why

Page 16: Thinking of Documentation as Code [YUIConf 2013]

DRY Documentation

Page 17: Thinking of Documentation as Code [YUIConf 2013]

Documentation Build Targets: HTML, EPUB, PDF, TROFF…

Page 18: Thinking of Documentation as Code [YUIConf 2013]

Contact Info: [email protected] || @evangoer

Thank You!