| Conversation with #asciidoctor at Fri 10 Jan 2014 10:04:59 AM MST on graphite6@irc.freenode.net (irc) | |
| (10:24:59 AM) chm007: Point to be discussed : Future of asciidoctor / hyla | |
| (10:25:46 AM) lightguard_jp: chm007: Individually or together? | |
| (10:25:55 AM) lightguard_jp: Like using hyla with asciidoctor? | |
| (10:26:45 AM) chm007: lightguard_jp Wait the points that I'm currently writing ;-) This is just a title | |
| (10:27:11 AM) graphite6: chm007: And could you give me a little intro to what hyla does (when you get a chance...no rush) | |
| (10:31:29 AM) colinmcnamara left the room (quit: Read error: Connection reset by peer). | |
| (10:31:40 AM) chm007: suggestions : 1) hyla becomes the command line tool of asciidoctor project, 2) asciidoctor => parser tool (from Asciidoctor to HTML/DocBook ...) / we could simplify it by removing the CLI, 3) Does it make sense to have some backends in asciidoctor and others in asciidcotor-backends (haml, slim, ...) - maintenance cost is high, 4) asciidoctor-backend should be more rationale and sup |
This gist is connected to this issue: 366
Make a list of all of the parts of the Asciidoctor toolchain.
Make a list of the different types/stages of Asciidoctor users.
What parts of the toolchain are missing?
Just a few types of users have been added. We need to flesh out the groups and add (or cut).