initial commit of Asciidoctor backend #2

Merged
merged 1 commit into from Jun 18, 2014

Conversation

Projects
None yet
2 participants
@mojavelinux
Contributor

mojavelinux commented Jun 17, 2014

Here's the very start of a packt backend for use with Asciidoctor. I choose to use the slim template languages because it's the most concise language for creating XML output.

I've just done (most of) the document template so far. This covers the [header] and [footer] parts of the AsciiDoc Python backend. The next step is to do the paragraph block, then enable call to =content in the document template. Once you have these started, the rest should come quickly.

@mojavelinux

This comment has been minimized.

Show comment
Hide comment
@mojavelinux

mojavelinux Jun 17, 2014

Contributor

You enable the backend using:

$ asciidoctor -T slim -b packt book.adoc

Once you have the backend created, then you'll be able to use Groovy plugin to drive Asciidoctor as an alternative to using the asciidoctor command.

Contributor

mojavelinux commented Jun 17, 2014

You enable the backend using:

$ asciidoctor -T slim -b packt book.adoc

Once you have the backend created, then you'll be able to use Groovy plugin to drive Asciidoctor as an alternative to using the asciidoctor command.

@gregturn

This comment has been minimized.

Show comment
Hide comment
@gregturn

gregturn Jun 18, 2014

Owner

Thanks! I'll see how far I can get.

Owner

gregturn commented Jun 18, 2014

Thanks! I'll see how far I can get.

@mojavelinux

This comment has been minimized.

Show comment
Hide comment
@mojavelinux

mojavelinux Jun 18, 2014

Contributor

Excellent. If you get stuck, just let me know (ideally by posting to the list). I've done enough of these backends that they are practically second nature.

The trickiest part with slim is dealing with nested inline markup. Keep in mind that you always have the option of just using a long, interpolated Ruby string anywhere you want to. There's no rule that says that every tag must be represented in Slim's DSL hierarchy.

Contributor

mojavelinux commented Jun 18, 2014

Excellent. If you get stuck, just let me know (ideally by posting to the list). I've done enough of these backends that they are practically second nature.

The trickiest part with slim is dealing with nested inline markup. Keep in mind that you always have the option of just using a long, interpolated Ruby string anywhere you want to. There's no rule that says that every tag must be represented in Slim's DSL hierarchy.

gregturn added a commit that referenced this pull request Jun 18, 2014

Merge pull request #2 from mojavelinux/asciidoctor-backend
initial commit of Asciidoctor backend

@gregturn gregturn merged commit 46b0e37 into gregturn:master Jun 18, 2014

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