The mkdocs-alias-plugin
MkDocs plugin allows links to your pages using a custom alias such as [[my-alias]]
or [[my-alias|My Title]]
.
The aliases are configured through the meta-sections of each page (see Usage below).
If you like this plugin, you'll probably also like mkdocs-categories-plugin and mkdocs-live-edit-plugin.
I maintain a fairly large wiki and occasionally will restructure parts of it, resulting in many broken links. This plugin allows me to separate the wiki contents from the file system structure and resolves the paths during build time. Maybe this plugin will help you out as well.
Install the package using pip:
pip install mkdocs-alias-plugin
Then add the following entry to the plugins section of your mkdocs.yml
file:
plugins:
- alias
For further configuration, see the Options section below.
Add an alias
section to your page's meta block:
---
alias: wuthering-heights
---
Then, using the alias in the markdown content of your pages:
The song references [[wuthering-heights]].
Which, after the page builds, renders as a regular link to your page.
A more advanced example would be to use the dictionary-style configuration instead of providing a different link title:
---
alias:
name: wuthering-heights
text: Wuthering Heights, a novel by Emily Brontë
---
If you'd like to supply a custom link text instead on a link-by-link basis, you can do so using a pipe to separate the title from the alias:
The song references [[wuthering-heights|Wuthering Heights]].
As of version 0.6.0, you can also use link anchors in your aliases:
The song references [[wuthering-heights#references]].
Or, using a custom title:
The song references [[wuthering-heights#references|Wuthering Heights]].
As of version 0.8.0, you can enable the plugin option use_anchor_titles
to replace anchor links with the text of the page heading that defined it. This behavior is opt-in to preserve backward compatibility.
Please refer to the MkDocs documentation for more information on how the meta-data block is used.
As of version 0.3.0, assigning multiple aliases to a single page is possible. This feature does come with the limitation that these aliases cannot define a per-alias title and instead will use the page title. The syntax for this is:
---
alias:
- wuthering-heights
- wuthering
- wh
---
As of version 0.4.0, it is possible to escape aliases to prevent them being parsed by the plugin. This is useful if you use a similar double-bracket markup for a different purpose (e.g. shell scripts in code blocks). The syntax for this feature is a leading backslash:
\[[this text will remain untouched]]
[[this text will be parsed as an alias]]
You may customize the plugin by passing options into the plugin's configuration sections in mkdocs.yml
:
plugins:
- alias:
verbose: true
use_anchor_titles: true
You may use the optional verbose
option to print more information about which aliases were used and defined during the build process. The default value is false
.
Setting this flag to true causes the plugin to replace an alias containing an anchor ([[my-page#sub-heading]]
) with the text of the header that defined it. You can still override the title of the link as usual.
Your alias doesn't have link text defined and your page doesn't have a title H1 tag or a title
attribute in its meta data section. Once you add this, your link will render with the appropriate text.
WARNING - Alias 'my-alias' not found
The alias could not be found in the defined aliases, usually due to a typo. Enable verbose output in the plugin's configuration to display all of the found aliases.
However, it is also possible that the plugin is trying to interpret another double-bracketed syntax as an alias. In this case, use the escape syntax to prevent the plugin from parsing it.
You're getting a message resembling this in your output:
WARNING - page-url: alias alias-name already defined in other-url, skipping.
Aliases must be unique. Ensure that you're not redefining the same alias for a different page. Rename one of them and the warning should go away.
Installing a local copy of the plugin:
pip install -e /path/to/mkdocs-alias-plugin/
Running unit tests after installing pytest from the root directory:
pytest -vv
Both unit test and linting:
pylint $(git ls-files '*.py') && pytest -vv
Bug Fix: fixes a bug where annotations would break older versions of Python 3. Bug report: #9.
This release adds functionality to replace the titles of aliases containing anchors with the text of the heading that defines them. Enable this feature by setting the plugin option use_anchor_titles
to true. Feature request: #8.
Bug Fix: fixes a bug where any alias with the word "text" would break the plugin due to faulty logic. Bug report: #7.
2024-02-01
This release removes support for the use_relative_link
option introduced in issue #3. As of version 1.5.0, MkDocs prefers relative links to absolute links, which was this package's default before. As of this version, all alias links generated are relative to the file from where they were linked.
2023-04-17
Adds support for page anchor links from within an alias. E.g.:
[[my alias#my anchor]]
2023-02-08
Adds the ability to use the use_relative_link
config flag, which causes the plugin to generate relative links to the aliased document rather than absolute ones. This flag is useful for those who host their wikis in subdirectories.
@SimonDelmas contributed this feature in PR #3. Thanks!
2022-07-10
Adds the ability to escape aliases so they won't be parsed by the plugin. Also adds more unit tests.
2022-04-27
Adds the ability to create multiple aliases for a single page (see the documentation for "Multiple Aliases" above). Improves the "alias not found" warning by listing the file attempting to use the alias.
2022-02-23
Allow strings as aliases instead of dictionaries, which allows for the use of page titles in the link text of the alias.
This version also makes the text
key optional in the alias dictionary configuration, using the same page title link text instead if it's not provided.
2022-02-12
Fixes a bunch of linter issues, but no new logic.
2022-02-12
Initial release with all of the base logic in place.