Is this a bug report?
✖️No
✅ Yes
Feature request
Currently, Docusaurus hardcodes the URL param for the pre-release master branch as next. The version link in the header and the URLs use the word next. I'd like to be able to configure this field in siteConfig.js, because I'd like to be able to use the URL value master instead.
For example, instead of localhost:3000/docs/next/installation.html, I'd like to be able to use master 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, like master, instead of the default, next.
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
masterbranch 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 valuemasterinstead.For example, instead of
localhost:3000/docs/next/installation.html, I'd like to be able to usemasterinstead: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.jsvariable that would allow users to set a custom name, likemaster, instead of the default,next.