Use GitBook 2.0 block tags?

[leesei]

What do you think of using block tags instead of hacking ```? The quote type will be one of the parameter and would not interfere with the content of the quote.

> **Info** Info quotes

to

{% richquotes info %}
Info quotes
{% endrichquotes %}

Optionally we can strip /$>[\s]*/ to accept this:

{% richquotes info %}
> Info quotes
{% endrichquotes %}

(I think the Github parser parsed it wrongly.)

[erixtekila]

That may be good idea. I ddin't get the time to read the last plugins features. WIll check that.

[leesei]

I did an experiment.

{% myTag %}*World*{% endmyTag %}

yields

Hello *World*

The content is not passed to Markdown pipeline so we can no longer use Markdown. We have to use HTML tags unless we're parsing blk.body in the handler.

{% myTag %}<i>World</i>{% endmyTag %}

I think that is a limitation of block tags. I would open an issue on GitBook to discuss the merits of template block tags.

[glueckpress]

+1 for what @leesei says, Markdown inside of block level HTML elements will not be parsed:

Note that Markdown formatting syntax is not processed within block-level HTML tags. E.g., you can’t use Markdown-style emphasis inside an HTML block.

As attractive as block level elements seem for common use cases of this plugin, I think they justify another plugin rather than modifying this one.