mojavelinux wrote

We definitely would like to welcome your project into the Asciidoctor organization.

mojavelinux wrote

If you are interested, I'm also looking for someone to help maintain asciidoctor.js. What this involves is keeping the branch of Asciidoctor used to compile asciidoctor.js up to date with the latest Asciidoctor release. Opal requires certain changes to be made to the Ruby code for it to compile successfully to JavaScript. That branch (currently based on 0.1.2) holds those changes. Eventually we want to remove any differences so that no changes are required, but for now we need them.

mojavelinux wrote

If that's something you'd like to hack on, I'll put together some instructions so you know how to get started and other things you need to know to make it work. Andres from Neo Technologies has also expressed interested in helping out, so you won't be a lone wolf. I do need to start looking for some help for stuff like this, though, or else these integrations fall behind because I can't get to them quick enough.

mojavelinux wrote

Also, if you would like to make a news post about this on asciidoctor.org, just sent a pull request! Look at other news posts to see how to layout the AsciiDoc file. Note that you don't need to specify the revdate attribute in the header since that's generated automatically by the publishing script.

mojavelinux wrote

If you are using the default Asciidoctor stylesheet, you shouldn't need bootstrap.min.css. The default stylesheet uses Foundation, which is another framework like Bootstrap. All the styles it needs are in there already...unless you are using bootstrap for something else.