-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
Relative markdown links between blog and docs does not work #9117
Comments
Yes, it does not work, because currently the relative link resolution is a plugin-specific feature and not a Docusaurus core feature. I'd like to support cross-plugin relative links but it would require the core engine to somehow maintain a "file path -> URL path" mapping, and we probably need additional plugin lifecycle hooks for that. Note: if you use Docs versioning, once your docs get versioned, the docs copy will be at a different location and it might break your relative links that are not linking to the same current version (I mean: a relative link from v1.3 to v1.3 won't break, but a v1.3 relative link to a blog post might break when the doc is moved from |
Hi @slorber, Thanks for confirming! I now see this is noted in the documentation here. Good to know regarding doc versioning. Fortunately, I do not have a need for versioned docs at this time. Seems like I might be able to workaround this by using regular expressions to remove the Very much appreciate your help. |
This comment was marked as spam.
This comment was marked as spam.
Integrate the tutorial with the docs to solve the issue that links between the docs and the tutorial had to be URL links which could not be resolved when the Markdown files were rendered on GitHub [1]. [1]: facebook/docusaurus#9117 Signed-off-by: Martin Nonnenmacher <[email protected]>
Integrate the tutorial with the docs to solve the issue that links between the docs and the tutorial had to be URL links which could not be resolved when the Markdown files were rendered on GitHub [1]. [1]: facebook/docusaurus#9117 Signed-off-by: Martin Nonnenmacher <[email protected]>
Integrate the tutorial with the docs to solve the issue that links between the docs and the tutorial had to be URL links which could not be resolved when the Markdown files were rendered on GitHub [1]. [1]: facebook/docusaurus#9117 Signed-off-by: Martin Nonnenmacher <[email protected]>
Integrate the tutorial with the docs to solve the issue that links between the docs and the tutorial had to be URL links which could not be resolved when the Markdown files were rendered on GitHub [1]. [1]: facebook/docusaurus#9117 Signed-off-by: Martin Nonnenmacher <[email protected]>
Have you read the Contributing Guidelines on issues?
Prerequisites
npm run clear
oryarn clear
command.rm -rf node_modules yarn.lock package-lock.json
and re-installing packages.Description
Hi Docusaurus team,
Love this library - thank you for your awesome work!
I'm looking to link a blog post to a docs page using a relative markdown link, but I receive the following error when I specify
[link to doc](../../docs/doc-page.md)
in the blog post:[WARNING] Blog markdown link couldn't be resolved: (../../docs/doc-page.md) in "/home/projects/github-dc5ygn/blog/blog-post.md
On the other hand, using link without the
.md
([link to doc](../../docs/doc-page)
) extension works fine.Is there a way I can prevent the broken link while preserving the
.md
extension? I'm using an Obsidian plugin to convert wikilinks to internal links and need to keep the.md
extension for it to work properly.Reproducible demo
https://stackblitz.com/edit/facebook-docusaurus-mx3fkh?file=blog%2Fblog-post.md
Steps to reproduce
[WARNING] Docs markdown link couldn't be resolved: (../../docs/doc-page.md) in "/home/projects/facebook-docusaurus-mx3fkh/docs/doc-page.md" for version current
[link to doc](../../docs/doc-page)
Expected behavior
The link
[link to doc](../../docs/doc-page)
should work regardless of whether or not.md
is specified.Actual behavior
The link
[link to doc](../../docs/doc-page)
only works when.md
is omitted.Your environment
Self-service
The text was updated successfully, but these errors were encountered: