The docinfo processor doesn't run for embedded documents (which is the mode Asciidoctor uses inside a site generator like Jekyll). As to whether it should, that's an open discussion.

But don't despair. You can use a postprocessor instead. When producing an embedded document, the two are effectively the same.

(The other solution would be to create a liquid tag that can be used in the page template, or just add the additional resources to the page template directly. Though I realize that's not as encapsulated).

Cheers,

-Dan

On Wed, Nov 6, 2019 at 4:11 PM maxandersen [via Asciidoctor :: Discussion] <[hidden email]> wrote:

Hi,

I initially created https://github.com/asciidoctor/asciidoctor-extensions-lab/pull/112
and it is working great in standalone asciidoctor.

Now I created a simple gem to use in a site using jekyll asciidoctor.

https://github.com/maxandersen/asciidoctor-tabbed-code


What is now weird is that the extension registration does happen (verified by adding logging),
but the extension is never actually called/applied.

Is there a chance that in jekyll docprocessors are not called or am I doing something completely wrong ?

You can see what I did in this jekyll asciidoctor enabled project to try and get it integrated:

https://github.com/quarkusio/quarkusio.github.io/compare/develop...maxandersen:tabbed-code?expand=1


Any tips/pointers to what can cause docinfo processor extensions not to be called would be very appreciated!

Thanks!

---

If you reply to this email, your message will be added to the discussion below:

https://discuss.asciidoctor.org/Problem-with-getting-docinfo-processor-to-be-used-in-jekyll-asciidoctor-tp7326.html

To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML

--

Dan Allen | @mojavelinux | https://twitter.com/mojavelinux