Plugin improvements

[dobarx]

• Improves plugin schema and allows to specify content location & invocation order from plugin level.
• TOC can now be placed anywhere inside document and it will be invoked last and content placed on top.
• FrontMatter now is rendered at the top of the markdown.
• Text calculates relative title size.

[traut]

TOC can now be placed anywhere inside document and it will be invoked last and content placed on top.

can both of these be configured? For the cases where TOC should render for a specific section (not the whole doc) and be placed in a specific location, instead just on the top of the doc.

With depends_on, for example, we could define a scope for TOC. As for the location, maybe we need place_at_the_top_of_the_doc (or something) bool flag, that defaults to true, but can be see to false with TOC placed inline.

apologies if some of this is covered, I haven't looked through the code yet!

[traut]

I think these sub titles would be on the same level as Title 1. They would be sub- titles if they would be inside the section that defines nesting

[dobarx]

From specs it says:

If format_as is title and absolute_title_size is not set, the relative title size is calculated from the local context object that contains a document body (issue TBD) -- the multiplier for # for a Markdown title prefix is the number of title text seen previously in the document

So shouldn't it be lower level?

[dobarx]

Or do we need to calculate it based on section nesting instead of previous titles?

[traut]

My apologies. I think I described it the wrong way there!

If we think of the template as a tree, the deeper you go down the branch, the smaller titles get. The nested sections would represent depth -- so the title should be calculated looking for previous titles up the branch to a root level

[dobarx]

TOC can now be placed anywhere inside document and it will be invoked last and content placed on top.

can both of these be configured? For the cases where TOC should render for a specific section (not the whole doc) and be placed in a specific location, instead just on the top of the doc.

With depends_on, for example, we could define a scope for TOC. As for the location, maybe we need place_at_the_top_of_the_doc (or something) bool flag, that defaults to true, but can be see to false with TOC placed inline.

apologies if some of this is covered, I haven't looked through the code yet!

Ahh, so then I should turn off content placement at top for it and keep original one? As for the scope it should be based on scope variable that can either be document or section

[dobarx]

Fixes:

• Split text into separate title, text, code, blockquote blocks. Refactor content.text options into separate content providers #133
• Transformed content in data context from flat list to tree structure
• All content elements contain unique IDs that can be used to find or replace content elements from plugin level.
• InvocationOrder no-longer effects content position in the rendered markdown. TOC content can be rendered in the same position where it is defined even though it is instructed to executed last.

[dobarx]

Fixes:

• Decreased title low size values to zero.

[traut]

closes:

• Built-in content.toc plugin #56
• Built-in content.text plugin #15