Files relating to the AsciiDoc presentation showcasing HubPress and Asciidoctor technologies.
- run-sheet.adoc
-
The 'presentation' I displayed in the video.
- example.adoc
-
A very simple AsciiDoc document you can experiment with.
- Asciidoctor_Tech_Demo_Slides.adoc
-
Source for the reveal.js slide deck I created from run-sheet.adoc. See
View the video on Vimeo.
Tip
|
To see how videos appear in
|
The demos start about 20 minutes into the presentation.
- Get Learning
-
http://asciidoctor.org/ is the place to go to learn more about the fast text processor & publishing toolchain for converting AsciiDoc to HTML5, DocBook & more. On this landing page, you get links to all Asciidoctor Docs. Itβs a great resource I refer to regularly when writing.
- Get Building
-
https://github.com/jaredmorgs/Pinball_Arcade_Users_Guide_Android is an example of a complete user guide, with include statements and some more advanced AsciiDoc markup. You can practise building this locally by following the instructions in the README.adoc
- Get Publishing
-
https://github.com/asciidoctor/jekyll-asciidoc-quickstart is a forkable Jekyll site using AsciiDoc. It uses Travis-CI to automatically build and publish your book when you commit changes to the repository. Follow the instructions in the README.adoc to get this set up for use. You can use the Users Guide above as a base for your guide, or not worry about includes and have one flat file.
- Get Blogging
-
https://github.com/HubPress/hubpress.io is a forkable Blogging app that uses asciidoctor.js as the transformation engine, and Ghostscript themes to style the blog posts. Follow the instructions in the README.adoc to configure the blog.
- Get Presenting
-
http://asciidoctor.org/docs/install-and-use-revealjs-backend/ is how I created the reveal.js slide deck from the
Asciidoctor_Tech_Demo_Slides.adoc
file. This is hosted at http://jaredmorgs.github.com/Asciidoctor_Presentation - Default to Open
-
All the links above are Free and Open Source (FOSS) projects created with collaboration in mind. If you want to contribute, fork the projects and start contributing. No contribution is too small: a bug fix to spelling, corrections to procedures, anything.