AsciidoctorJ Block Processor Problems

Given that Sean wants to donate his source code I would certainly happily add it to that repository.

The only extension that is currently in there in fact only works with 1.6.0 as well.:)

So we should only consider moving the asciidoctorj-extension-lab repository into the asciidoctor organization, if Dan is ok with it, once 1.6.0 is released.

Best regards
Robert

Sure, I have no problem sharing the code, though it's ugly right now and should use freemarker or something similar. When I get some free time I'd also love to contribute some more examples. I've found that extensions are critical when you want to manage large amounts of content, let alone doing something out of the box. Examples I'd like to see:

- Adding attributes to an existing block/style, such as source code, tables, headings for images, etc.
- Processing custom blocks for common scenarios such as adding tabs to output, adding gists, custom video blocks, diagrams, etc.
- Validation, which could be everything from enforcing consistent syntax (since there are many ways to do things in Asciidoctor), validating links, ensuring a referenced image actually exists in the selected path, spell checking, etc.

Some of these fall under "best practices," which would also be something I'd like to see and could contribute to when I feel more confident.