can this plugin be used to change the jinja2 environment that mkdocs uses?

[ntno]

can i change the jinja2 environment using this plugin?

use case:
i would like to be able to install a jinja2 extension and then use that extension in my custom mkdocs theme

details:
in particular i would like to install jinja2_markdown which adds an extra jinja2 tag {% markdown %}
in that project's documentation it says i need to add the extension to the jinja2 environment like so:

from jinja2_markdown import MarkdownExtension

jinja_env.add_extension(MarkdownExtension)

does 'mkdocs_macros_plugin' make sense for this use case? i am not super experienced with plugins/jinja2 so i wanted to check before getting too deep into it

[ntno]

i think i found the answer in the 'advanced usage' section of the documentation:

Of course, you can declare macros, which appear to act on pages. But realize that these are only declarations and that their execution is deferred. The macros will actually be run later (by MkDocs' on_page_markdown() event), just before the markdown is rendered. The framework is so organized that, in macros, you are actually "talking" about objects that don't exist yet.

So you cannot influence the rendering process other than by adding macros, variables and filters to mkdocs_macros.

then later:

<meta name="description" content="{{ page.meta.description }}" />
Note that in the snippet above, Jinja2 is used by MkDocs to produce HTML pages. This is completely distinct from MkDocs-macros' use of Jinja2 on Markdown pages (it occurs at a later stage).

these parts of the documentation make me think that i cannot effect the general jinja2 rendering environment by adding a mkdocs_macros filter but please let me know if this is not correct.