Comments (6)
Our use case is our install instructions; the linked example is the Windows instructions redirecting to Linux for WSL.
Stand-alone pages seem more useful than docs for this purpose, as the install instructions are mostly version-agnostic. And if a new install method becomes available, then there are no duplicates to forget to sync.
from docusaurus.
I see. Maybe you should use https://docusaurus.io/docs/docs-multi-instance instead? Pages are mostly useful for marketing instead of informative purposes. Nevertheless we should probably implement feature parity for this.
from docusaurus.
Yes, that would be nice to support relative md paths in pages, but also the blog plugin.
And to allow one plugin to reference files of another. For that we probably need new plugin lifecycle hooks to allow one plugin to resolve a file path to the final url/pathname of another plugin.
from docusaurus.
Yes, that would be nice to support relative md paths in pages, but also the blog plugin.
Right, I suppose it's only implemented in the docs plugin, then? IMO, an immediate action would be to mention that in the documentation, to reduce astonishment for people like me. (I'll admit, though, that I've been sitting on this for a while... 😅)
Hmmm, I was wrong, it seems we also implemented it in the blog plugin 😅 so only the page plugin doesn't have it.
If you find a good place to add it to the page docs, don't hesitate to send a PR. Although I'm not sure it's necessary since we want to implement it and nobody apart you complained so far 😅
And to allow one plugin to reference files of another. For that we probably need new plugin lifecycle hooks to allow one plugin to resolve a file path to the final url/pathname of another plugin.
Right; this seems to already be requested in #9117. I think it'd be best to avoid duplicating discussion between issues?
Agree, let's keep #9117 for inter-plugin file path links resolution.
from docusaurus.
Yes we never added this support. Curious what your use case is? I think most people just use docs anyway, with navigation disabled if necessary. I haven't seen much demand for standalone Markdown pages at all, let alone cross-linking ones.
from docusaurus.
Yes, that would be nice to support relative md paths in pages, but also the blog plugin.
Right, I suppose it's only implemented in the docs plugin, then? IMO, an immediate action would be to mention that in the documentation, to reduce astonishment for people like me. (I'll admit, though, that I've been sitting on this for a while... 😅)
And to allow one plugin to reference files of another. For that we probably need new plugin lifecycle hooks to allow one plugin to resolve a file path to the final url/pathname of another plugin.
Right; this seems to already be requested in #9117. I think it'd be best to avoid duplicating discussion between issues?
from docusaurus.
Related Issues (20)
- Dark mode not sticking on Brave Browser HOT 1
- Code block no longer show syntax highlight HOT 8
- how to create code blocks new design HOT 1
- Mermaid not displaying correctly in mdx HOT 2
- Reference link to source path introduce extra ) HOT 1
- Issues with npm run build with custom calendar component HOT 2
- End-of-line CRLF sequence causes TabItem compilation error HOT 4
- Math equations do not work when imported from another file HOT 3
- Unable to import type for `SidebarItemConfig` in a typescript Docusaurus project. HOT 1
- Table of contents should scroll with content HOT 7
- Invalid hook call when using react class component in MDX HOT 12
- RangeError: Invalid string length when building with a very large number of blogs HOT 7
- Broken link in a-tag not detected HOT 7
- Navbar: Menu Item: Caret / Arrow Is Invisible When Deployed On Azure SWA (using MSAL) HOT 2
- Duplicated whole page when accessing site by your-domain.com/index.html HOT 4
- [Accessibility]: Page looses focus after Search modal gets closed HOT 1
- Please Block the "Bruce's Wiki" at show case since contain the Malicious links HOT 2
- Place screenshots in the themes documentation page in the site HOT 3
- Passing custom props to IdealImage HOT 2
- Spaces are no longer valid in links HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from docusaurus.