About the book
We've transformed the way teams work together on docs, and we want to show you the best practices for writing docs using development tools and techniques. Now available in both print and ebook, check out Docs Like Code.
Why use GitHub for docs? If you're unsure of a good fit for your projects and teams, read about the potential wins with these techniques. Or, you may learn how to convince others who need to hear about the use cases.
Information architecture and workflows, how do you choose? Read these chapters to find out lessons learned when making sure the users are served first.
How can I improve upon my team's work? Author and build content like a pro, whether you're a writer or a developer. Build in quality assurance, automate builds, and review with your teammates to make great docs.
What are the best practices for REST API docs? While Swagger/OpenAPI, RAML, and other standards work well when considering the entire API lifecycle, you can also consider collaboration gains with simple markup and narrative documents beyond the REST API reference doc set.
Who's using these techniques?
“I met with one of the devs today to go over a Pull Request that I had submitted with editorial comments, and in the course of conversation, I mentioned that I had not been working directly with developers for very long.
He replied that he’d worked with technical editors in the past who were not very helpful, but that I was different. In fact, he assumed I was a developer at first because I was working in GitHub, effortlessly creating PRs!”
— Kelly Holcomb, Senior Technical Editor, Rackspace
“This book will be the go-to guide for people looking to get into the Docs like Code world. It has been on my list to write for a while, and I’m glad someone did for me. :)”
— Eric Holscher, Cofounder of Read the Docs and Write the Docs