Backport of docs: Fixing path for autoscaling/agent/source nav item into stable-website #12168
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #12166 to be assessed for backporting due to the inclusion of the label backport/website.
The below text is copied from the body of the original PR.
What/Why
While working on a project consuming these docs, I found a sidebar nav item with a different path than its siblings. Confirmed it with some Nomad folks via Slack that the nav item should have a matching path so this PR makes that change and also:
website/content/docs/autoscaling/agent/source.mdx
towebsite/content/tools/autoscaling/agent/source.mdx
, so that it is in the same place as its siblingswebsite/data/tools-nav-data.json
, so it shows up in the Tools docs page sidebar/tools
, updates the nav item object to pass that value ashref
instead ofpath
inwebsite/data/docs-nav-data.json
Testing