Skip to content

Instantly share code, notes, and snippets.

@mojavelinux
Last active August 29, 2015 14:23
Show Gist options
  • Save mojavelinux/883c0482128e8a806194 to your computer and use it in GitHub Desktop.
Save mojavelinux/883c0482128e8a806194 to your computer and use it in GitHub Desktop.
Why must documentation be a pain in our ass? (Devoxx Morocco)

Why must documentation be a pain in our ass?

“Is the documentation up to date?”
“Where’s the documentation for version 1.5?”
“What are the differences with the previous version?”
“How do I generate the table of contents?”
“How to generate a PDF of the documentation?”
“How can I change the styles for titles?”
“Damnit! Word again broke the numbering in my list again!”

Most of the time, the documentation is written in files that are isolated from the source code. The format can be constraining for the developer, which leads to frustration and impacts the final delivery. Taking care of the form is not our primary activity, but the content definitely is. And of course, what about seeing those difference between versions?

If this introduction sounds familiar, Asciidoctor is here for you. Simple, clear, concise. During this presentation we will see the syntax, the integration in the application lifecycle and how to customize the output. You’ll discover that writing documentation does not have to be a pain in your ass.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment