Skip to content
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

[v14] Restructure docs menu pages #48151

Merged
merged 1 commit into from
Oct 30, 2024
Merged

Conversation

ptgott
Copy link
Contributor

@ptgott ptgott commented Oct 30, 2024

Backports #47797

Docusaurus sidebar
generation
expects category index pages to have one of three file path conventions:

  • section/index.mdx
  • section/README.mdx
  • section/section.mdx

This change standardizes category index paths on the third convention so Docusaurus sidebar generation succeeds. We can then add checks to the current docs site to prevent additional menu pages from violating this convention.

This change also adds redirects to the new category index pages, and updates internal links to pages that were moved.

Note that this change does not move all relevant menu pages. We still need to reorganize the reference/terraform-provider section. Since this section is automatically generated, we need another approach to restructuring it.

Backports #47797

Docusaurus [sidebar
generation](https://docusaurus.io/docs/next/sidebar/autogenerated)
expects category index pages to have one of three file path conventions:

- `section/index.mdx`
- `section/README.mdx`
- `section/section.mdx`

This change standardizes category index paths on the third convention so
Docusaurus sidebar generation succeeds. We can then add checks to the
current docs site to prevent additional menu pages from violating this
convention.

This change also adds redirects to the new category index pages, and
updates internal links to pages that were moved.

Note that this change does not move all relevant menu pages. We still
need to reorganize the `reference/terraform-provider` section. Since
this section is automatically generated, we need another approach to
restructuring it.
Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-48151.d3b94eevwi10ji.amplifyapp.com

@ptgott ptgott added the no-changelog Indicates that a PR does not require a changelog entry label Oct 30, 2024
@ptgott ptgott enabled auto-merge October 30, 2024 18:21
@ptgott ptgott added this pull request to the merge queue Oct 30, 2024
Merged via the queue into branch/v14 with commit e920977 Oct 30, 2024
30 of 31 checks passed
@ptgott ptgott deleted the paul.gottschling/47797-bp-v14 branch October 30, 2024 18:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport documentation no-changelog Indicates that a PR does not require a changelog entry size/sm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants