Move backward compatibility docs under Contributors Guide (#37654)

* Move backward-compat and deprec docs under contributors/code * Update table of contents and manifest to new locations * Update link to backward-compat doc
WordPress · Feb 5, 2022 · 5ad99f5 · 5ad99f5
1 parent 0fb3492
commit 5ad99f5
Show file tree

Hide file tree

Showing 5 changed files with 16 additions and 22 deletions.
diff --git a/...o-guides/backward-compatibility/README.md → ...ntributors/code/backward-compatibility.md b/...o-guides/backward-compatibility/README.md → ...ntributors/code/backward-compatibility.md
diff --git a/...es/backward-compatibility/deprecations.md → docs/contributors/code/deprecations.md b/...es/backward-compatibility/deprecations.md → docs/contributors/code/deprecations.md
diff --git a/docs/manifest.json b/docs/manifest.json
@@ -95,18 +95,6 @@
  "markdown_source": "../docs/how-to-guides/accessibility.md",
  "parent": "how-to-guides"
  },
- {
- "title": "Backward Compatibility",
- "slug": "backward-compatibility",
- "markdown_source": "../docs/how-to-guides/backward-compatibility/README.md",
- "parent": "how-to-guides"
- },
- {
- "title": "Deprecations",
- "slug": "deprecations",
- "markdown_source": "../docs/how-to-guides/backward-compatibility/deprecations.md",
- "parent": "backward-compatibility"
- },
  {
  "title": "Blocks",
  "slug": "block-tutorial",
@@ -2027,6 +2015,18 @@
  "markdown_source": "../docs/contributors/code/react-native/internationalization-guide.md",
  "parent": "react-native"
  },
+ {
+ "title": "Backward Compatibility",
+ "slug": "backward-compatibility",
+ "markdown_source": "../docs/contributors/code/backward-compatibility.md",
+ "parent": "code"
+ },
+ {
+ "title": "Deprecations",
+ "slug": "deprecations",
+ "markdown_source": "../docs/contributors/code/deprecations.md",
+ "parent": "code"
+ },
  {
  "title": "Design Contributions",
  "slug": "design",

diff --git a/docs/toc.json b/docs/toc.json
@@ -43,14 +43,6 @@
  {
  "docs/how-to-guides/README.md": [
  { "docs/how-to-guides/accessibility.md": [] },
-
- {
- "docs/how-to-guides/backward-compatibility/README.md": [
- {
- "docs/how-to-guides/backward-compatibility/deprecations.md": []
- }
- ]
- },
  {
  "docs/how-to-guides/block-tutorial/README.md": [
  {
@@ -311,7 +303,9 @@
  "docs/contributors/code/react-native/internationalization-guide.md": []
  }
  ]
- }
+ },
+ { "docs/contributors/code/backward-compatibility.md": [] },
+ { "docs/contributors/code/deprecations.md": [] }
  ]
  },
  {

diff --git a/packages/components/CONTRIBUTING.md b/packages/components/CONTRIBUTING.md
@@ -32,7 +32,7 @@ In these situations, one possible approach is to "soft-deprecate" a given legacy
 
 When adding new components or new props to existing components, it's recommended to prefix them with `__unstable` or `__experimental` until they're stable enough to be exposed as part of the public API.
 
-Learn more on [How to preserve backward compatibility for a React Component](/docs/how-to-guides/backward-compatibility/README.md#how-to-preserve-backward-compatibility-for-a-react-component) and [Experimental and Unstable APIs](/docs/contributors/code/coding-guidelines.md#experimental-and-unstable-apis).
+Learn more on [How to preserve backward compatibility for a React Component](/docs/contributors/code/backward-compatibility.md#how-to-preserve-backward-compatibility-for-a-react-component) and [Experimental and Unstable APIs](/docs/contributors/code/coding-guidelines.md#experimental-and-unstable-apis).
 
 <!-- ## Polymorphic Components (i.e. the `as` prop)