-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add YAML placeholder tags that resolve to current paths #3258
Conversation
oprypin
commented
Jun 11, 2023
•
edited
Loading
edited
- Closes Support for relative base_path in markdown_extensions #2154
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. |