Posted by mojavelinux on Oct 08, 2013; 12:32am
URL: https://discuss.asciidoctor.org/Asciidoctor-as-content-managment-tp723p751.html

Marek,

I think this is a great idea to explore, especially with this statement in mind:

> I feel like it is good idea to stay with pure asciidoc because of simplicity for content editors.

Precisely.

As with anything, the use of AsciiDoc can be taken too far. You just have to pay attention to how it feels. If it begins to feel awkward, even forced, in certain contexts, that's when you need to challenge your assumption that it's a reasonable approach. Ideas, like materials, are strongest when combined.

On Oct 6, 2013 2:47 AM, "smigielski [via Asciidoctor :: Discussion]" <[hidden email]> wrote:

> I've checkout asciidoctor-java-integration but I can't find the way of retrieving different parts of main text based on block role or style. Can it be achieved somehow by manipulating input parameters or by extending java to ruby integration?

As Jason mentioned, this is possible, but not yet exposed out of the box. Java can read any information from Ruby objects, as the extension API integration proves, but it requires some type mappings to be put in place. That's planned for the Java integration. For now, you could study the extensions package to get an idea of how it's done.

I'm very interested to follow your experiment using AsciiDoc for this purpose!

-Dan