-
-
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
Allow configurable URL value for "next" #718
Allow configurable URL value for "next" #718
Comments
@JoelMarcey @yangshun If it's alright with y'all, I'd love to work on this 🤓 |
I would love a PR on this. Thanks! As long as it doesn't break existing functionality, then I think we could consider this. |
Hi @machikoyasuda 😁 |
@endiliey I was able to get around this issue with Netlify redirects, so I'm not working on this anymore! Someone else can claim if if interested, or close it :) |
I am closing this then. Trying to avoid extra feature (especially in siteConfig) before v2. |
@endiliey Thank you for your vigilant maintainership <3 |
Is this a bug report?
✖️No
Have you read the Contributing Guidelines on issues?
✅ Yes
Feature request
Currently, Docusaurus hardcodes the URL param for the pre-release
master
branch asnext
. The version link in the header and the URLs use the wordnext
. I'd like to be able to configure this field insiteConfig.js
, because I'd like to be able to use the URL valuemaster
instead.For example, instead of
localhost:3000/docs/next/installation.html
, I'd like to be able to usemaster
instead:localhost:3000/docs/master/installation.html
. This naming better aligns with the naming convention we already currently use in our docs and GitHub branch naming conventions.Proposal:
Add an optional
siteConfig.js
variable that would allow users to set a custom name, likemaster
, instead of the default,next
.The text was updated successfully, but these errors were encountered: