Following on from an idea of Dan Allan, this explores desires for authoring documentation from an engineering point of view. THhe second half looks at how Asciidoctor project is trying to address some of these desoires.
4. Information Mapping®
Chunking - Information in small manageable units.
Consistency - Format, structure.
Integrated graphics - Diagrams & tables are part of the
text.
Accessible detail - Put what the reader needs, where the
reader needs it.
http://www.informationmapping.com/en/
7. CodeDoc Proximity
The further the distance between the code and the
documentation, the lower the probability of the
documentation being maintained.
8. Desire #1
We want to use the same editor for code & docs
so that we do not have to switch tools.
10. Signature Skills
People will development affinities for certain tools
When the user has to fight the tool, the tool will not get
used effectively (or not at all).
14. Tracking changes
Engineering has already solved this problem.
Source control (Git, Subversion and others).
Easy to diff between changesets.
Collaborate with multiple commits and merging.
15. Desire #4
We want to store document source in a textual,
non-proprietary format, so that we can use existing
tools and track the changes.
16. Desire #5
We want to concurrently, collaborate on documents
and modify them without fear.
17. Automation
CI & CD and standard engineering practices.
Commit → Build → Feedback → Publish
18. Desire #5
We want documentation to be built
and published automatically.
19. Desire #6
We want our documentation to be
included with software publications.
20. We want…
to use the same editor for code & docs so that we do not
have to switch tools.
to focus on content, not layout.
to use one source to publish to multiple formats.
to store document source in a textual, non-proprietary
format.
documentation to be built and published automatically.
documentation to be included with software publication.
23. Why?
Focus on content, not formatting.
Source-control friendly.
No proprietary source format.
More powerful than Markdown, including
Github MD.
Leanpub MD & Markuva.
More user friendly than RText or LaTeX.
No need to fight Docbook.
31. Projects
A number of projects use Asciidoctor for documentation
complete with tested code snippets, including:
Groovy Language
Spring
Griffon
32. Actively in the works
Asciidoctor → Leanpub
Asciidoctor → Mallard
Asciidoctor → LaTeX
Asciidoctor → Pdf
Asciidoctor → Epub
33. About this presentation
Written in Asciidoctor (1.5.3.2)
Styled by asciidoctor-revealjs extension
Built using:
Gradle
gradle-asciidoctor-plugin
gradle-vfs-plugin