-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
refactor: normalize Markdown linkification behavior, elaborate in doc…
…umentation
- Loading branch information
Showing
8 changed files
with
121 additions
and
46 deletions.
There are no files selected for viewing
2 changes: 1 addition & 1 deletion
2
...docusaurus-plugin-content-docs/src/markdown/__tests__/__fixtures__/docs/doc2.md
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
47 changes: 47 additions & 0 deletions
47
website/docs/guides/markdown-features/markdown-features-links.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,47 @@ | ||
--- | ||
id: links | ||
description: Links to other pages in Markdown | ||
slug: /markdown-features/links | ||
--- | ||
|
||
# Markdown links | ||
|
||
There are two ways of adding a link to another page: through a **URL path** and a **file path**. | ||
|
||
```md | ||
[URL path to another document](./installation) [file path to another document](./installation.md) | ||
``` | ||
|
||
URL paths are unprocessed by Docusaurus, and you can see them as directly rendering to `<a href="./installation">`, i.e. it will be resolved according to the page's URL location, rather than its file-system location. | ||
|
||
If you want to reference another Markdown file **included by the same plugin**, you could use the relative path of the document you want to link to. Docusaurus' Markdown loader will convert the file path to the target file's URL path (and hence remove the `.md` extension). | ||
|
||
For example, if you are in `docs/folder/doc1.md` and you want to reference `docs/folder/doc2.md`, `docs/folder/subfolder/doc3.md` and `docs/otherFolder/doc4.md`: | ||
|
||
```md title="docs/folder/doc1.md" | ||
I am referencing a [document](doc2.md). | ||
|
||
Reference to another [document in a subfolder](subfolder/doc3.md). | ||
|
||
[Relative document](../otherFolder/doc4.md) referencing works as well. | ||
``` | ||
|
||
Relative file paths are resolved against the current file's directory. Absolute file paths, on the other hand, are resolved relative to the **content root**, usually `docs/`, `blog/`, or [localized ones](../../i18n/i18n-tutorial.md) like `i18n/zh-Hans/plugin-content-docs/current`. Note that absolute paths are **not** resolved relative to the site directory, because that means you have to change all `/docs/` paths to their localized counterparts during localization. | ||
|
||
```md | ||
You can write [links](/otherFolder/doc4.md) relative to the content root (`/docs/`). | ||
``` | ||
|
||
Using relative _file_ paths (with `.md` extensions) instead of relative _URL_ links provides the following benefits: | ||
|
||
- Links will keep working on the GitHub interface and many Markdown editors | ||
- You can customize the files' slugs without having to update all the links | ||
- Moving files around the folders can be tracked by your editor, and some editors may automatically update file links | ||
- A [versioned doc](../docs/versioning.md) will link to another doc of the exact same version | ||
- Relative URL links are very likely to break if you update the [`trailingSlash` config](../../api/docusaurus.config.js.md#trailing-slash) | ||
|
||
:::warning | ||
|
||
Markdown file references only work when the source and target files are processed by the same plugin instance. This is a technical limitation of our Markdown processing architecture and will be fixed in the future. If you are linking files between plugins (e.g. linking to a doc page from a blog post), you have to use URL links. | ||
|
||
::: |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters