Conversation
53eac4e to
f6dd3ac
Compare
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
- !relative # Obtains the directory of the currently rendered Markdown file
- !relative $docs_dir # Obtains the docs_dir
- !relative $config_dir # Obtains the directory of mkdocs.yml
|
Tagging @facelessuser now also on the pull request for any comments. Now I actually mention |
|
Could we allow plugins to register custom YAML tags? I suspect that this would need to be implemented outside of the plugin, because when the plugin is loaded, the configuration has already been parsed, but maybe plugins could provide something like a |
|
There's no clear technical solution how to do that (see also #3261), no known use case, and so no plan to do that |
|
It would be very helpful for the new projects plugin in Material for MkDocs to define tags to inline navigation from projects into the top-level site and other custom tags for additional features. From the top of my head: If a project defines an That'll work, wouldn't it? Edit: okay, the author would need to add the |
|
That sounds like not something that would require tags to function. Instead of |
|
Thanks, I'll think a little about this and might open a dedicated discussion. |
Uh oh!
There was an error while loading. Please reload this page.