We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any reason why not using feature avialable with docusaurus link
devs have too manual manage sidebar.json
No response
None
The text was updated successfully, but these errors were encountered:
Worth a shot!
I'd expect things to be reordered in ways that we might not want, but that can be fixed by adopting the numbering system we use in some places though, e.g. https://github.com/backstage/backstage/tree/master/docs/backend-system/architecture
It might also be worth waiting with this until more of the documentation restructure is complete, #21946
Sorry, something went wrong.
No branches or pull requests
馃敄 Feature description
Any reason why not using feature avialable with docusaurus
link
馃帳 Context
devs have too manual manage sidebar.json
鉁岋笍 Possible Implementation
No response
馃憖 Have you spent some time to check if this feature request has been raised before?
馃彚 Have you read the Code of Conduct?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: