Repository navigation
Replies: 2 comments
|
This seems to be caused by incorrect directory hierarchy. Please provide a minimal reproduction for troubleshooting. |
0 replies
|
You can upload a minimal reproduction package here. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello,
we're currently transitioning our knowledgebase projects from Mkdocs-Material to Mkdocs-MaterialX, so I'm checking for any issues that come with the change.
I noticed that the custom admonition icons we defined in mkdocs.yml are no longer working. I would appreciate help in identifying the issue.
Our configuration/icon setup looks as follows:
The icons we want to use for the admonitions are saved in /overrides/.icons:

Our knowledgebase consists of multiple sub-projects, each with its own mkdocs.yml. There is no mkdocs.yml on root level and all paths in the mkdocs.yml files are defined to account for that:

The

custom_iconsoption goes back one step to root-level before entering the overrides directory:The custom icons for admonitions are defined as described in https://jaywhj.github.io/mkdocs-materialx/reference/admonitions.html#custom-icons-and-colors-structure:

Here is a comparison of what the custom icons, e.g. for tip admonition, should look like vs. what it looks like in Material-X:
Old (Mkdocs-Material):

New (Mkdocs-MaterialX):

What am I doing wrong here?
Interestingly enough, the custom icon works if I define a fontawesome icon in the mkdocs.yml:

Any help is much appreciated, thank you :)
All reactions