On 12/3/2012 5:19 PM, Dan Allen wrote:
Stuart and the AsciiDoc community,

I'm a big fan of AsciiDoc (thanks to Matthew McCullough for turning me on to it). I'm interested in continuing to promote it with the goal of improving documentation (software or otherwise) across the globe.

I recently gave a presentation on AsciiDoc [1] (composed from AsciiDoc) at RWX 2012 which I'd like to share. It's rendered using dzslides, an awesome HTML5-based presentation framework. I developed a custom backend to AsciiDoc to generate the HTML5 and linked assets that dzslides requires [2].

I plan to keep this talk in my repertoire for the 2013 conference season.

...on to my main point:

Since I anticipate a groundswell of adoption for AsciiDoc in the near future (or at least I hope so), I reserved the domain names asciidoc.org and asciidoc.info in order to donate them to project. The motivation for reserving the domains was two-fold. First, to prevent the domains from being snatched up and used for an unrelated purpose and, second, to make it easier for people to find the project page (methods.co.nz is sort of hard to remember ;))

For now, I have setup a 301 redirect on each domain to point them to the current AsciiDoc project page.

I'm happy to manage the domains on behalf of the project, which Stuart is in support of. If you have other ideas about how to manage the domains as a group, I'm certainly open to handling them another way. Feedback welcome.

I'm honored to be a part of the vision to transform documentation. We constantly hear that documentation is weakest leg of software--open source software in particular. There's no shortage of passion in many of the projects, which points to the fact that a *huge* barrier must exist that prevents documentation from being written. AsciiDoc has proven to allow the gates in your mind to open and the words pour into the editor.

It quickly became apparent to me that the value in AsciiDoc was more than just a terse syntax, but the capability to preserve the semantics of the document (and to promote DRY). Before using AsciiDoc, I used Textile and Markdown extensively and that's how I was able to recognize that AsciiDoc stood out. It's time to drop the angled brackets, but in doing so we don't want to lose the semantics. AsciiDoc strikes that balance.

Cheers,

Dan Allen
http://google.com/profiles/dan.j.allen

[1] http://mojavelinux.github.com/decks/asciidoc-with-pleasure <http://mojavelinux.github.com/decks/asciidoc-with-pleasure/>
[2] https://github.com/mojavelinux/asciidoc-dzslides-backend
--
You received this message because you are subscribed to the Google Groups "asciidoc" group. To view this discussion on the web visit https://groups.google.com/d/msg/asciidoc/-/XC0g4XEIkCEJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/asciidoc?hl=en.

this looks even nice, probably the best one for html slides? (among slidy,slidy2,keydown,deckjs...)

problem after a quick test:
in the source file here:
https://raw.github.com/mojavelinux/decks/master/asciidoc-with-pleasure/slides.asciidoc

// asciidoc -a data-uri -a linkcss! slides.asciidoc
//
// HTML5:
// asciidoc -b html5 -o outline.html slides.asciidoc

but following that I got errors:

ping@640g-laptop:~/.asciidoc/backends/dzslides$ asciidoc -a data-uri -a linkcss! ~/Dropbox/temp-transfer/slides.asciidoc.txt asciidoc: WARNING: slides.asciidoc.txt: line 30: include file not found: /home/ping/.asciidoc/backends/dzslides/dzslides/themes/highlight/monokai.min.css asciidoc: WARNING: slides.asciidoc.txt: line 30: include file not found: /home/ping/.asciidoc/backends/dzslides/dzslides/themes/style/stormy.css asciidoc: WARNING: slides.asciidoc.txt: line 30: include file not found: /home/ping/.asciidoc/backends/dzslides/dzslides/core/dzslides.css asciidoc: WARNING: slides.asciidoc.txt: line 30: include file not found: /home/ping/.asciidoc/backends/dzslides/dzslides/themes/transition/fade.css asciidoc: WARNING: slides.asciidoc.txt: line 30: include file not found: /home/ping/.asciidoc/backends/dzslides/dzslides/core/dzslides.js asciidoc: WARNING: slides.asciidoc.txt: line 30: include file not found: /home/ping/.asciidoc/backends/dzslides/dzslides/highlight/highlight.min.js asciidoc: WARNING: slides.asciidoc.txt: line 37: missing style: [blockdef-listing]: qrcode sh: /home/ping/Dropbox/temp-transfer/images/mild.png: No such file or directory asciidoc: WARNING: slides.asciidoc.txt: line 139: {sys3:"/usr/bin/python" -u -c "import base64,sys; base64.encode(sys.stdin,sys.stdout)" < "/home/ping/Dropbox/temp-transfer/images/mild.png"}: non-zero exit status

ping@640g-laptop:~/Dropbox/temp-transfer$ asciidoc -b html5 -o outline.html slides.asciidoc.txt asciidoc: WARNING: slides.asciidoc.txt: line 37: missing style: [blockdef-listing]: qrcode asciidoc: WARNING: slides.asciidoc.txt: line 55: missing style: [blockdef-example]: NOTES asciidoc: WARNING: slides.asciidoc.txt: line 115: missing style: [blockdef-example]: NOTES asciidoc: WARNING: slides.asciidoc.txt: line 130: missing style: [blockdef-example]: NOTES asciidoc: WARNING: slides.asciidoc.txt: line 296: missing style: [blockdef-example]: NOTES asciidoc: WARNING: slides.asciidoc.txt: line 396: missing style: [blockdef-example]: NOTES asciidoc: WARNING: slides.asciidoc.txt: line 464: missing style: [blockdef-example]: NOTES asciidoc: WARNING: slides.asciidoc.txt: line 657: missing style: [blockdef-example]: NOTES asciidoc: WARNING: slides.asciidoc.txt: line 723: missing style: [blockdef-example]: NOTES


I guess I missed sth in the installation step 2:

Next, make a symlink to dzslides in that folder.

cd ~/.asciidoc/backends/dzslides
ln -s /path/to/dzslides .

If you enable the linkcss attribute, then the symlink should be added in the same directory as the presentation.

what is that /path/to/dzslides ? where/how can I get it installed?
I find this:
https://github.com/paulrouget/dzslides

is this the one your refer dzslides to?

thanks.

regards
ping


--
You received this message because you are subscribed to the Google Groups 
"asciidoc" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/asciidoc?hl=en.

Reply via email to