Update slug for contributors/develop and contributors/document

CONTRIBUTING.md

@@ -6,11 +6,11 @@ Welcome to WordPress' Gutenberg project! We hope you join us in creating the fut
 
 To learn all about contributing to the Gutenberg project, see the [Contributor Guide](/docs/contributors/README.md). The handbook includes all the details you need to get setup and start shaping the future of web publishing.
 
-- Code? See the [developer section](/docs/contributors/code/develop.md).
+- Code? See the [developer section](/docs/contributors/code/code.md).
 
 - Design? See the [design section](/docs/contributors/design/design.md).
 
-- Documentation? See the [documentation section](/docs/contributors/documentation/document.md).
+- Documentation? See the [documentation section](/docs/contributors/documentation/documentation.md).
 
 - Triage? We need help reviewing existing issues to make sure they’re relevant and actionable. Triage is an important contribution because it allows us to work on the highest priority issues. To learn more, please see the [triaging issues section](docs/contributors/triage.md).
 

docs/contributors/README.md

@@ -8,11 +8,11 @@ Gutenberg is a sub-project of Core WordPress. Please see the [Core Contributor H
 
 Find the section below based on what you are looking to contribute:
 
-- **Code?** See the [developer section](/docs/contributors/code/develop.md).
+- **Code?** See the [developer section](/docs/contributors/code/code.md).
 
 - **Design?** See the [design section](/docs/contributors/design/design.md).
 
-- **Documentation?** See the [documentation section](/docs/contributors/documentation/document.md)
+- **Documentation?** See the [documentation section](/docs/contributors/documentation/documentation.md)
 
 - **Triage Support?** See the [triaging issues section](/docs/contributors/triage.md)
 

docs/contributors/documentation/document.md → docs/contributors/documentation/documentation.md

@@ -67,7 +67,7 @@ This way they will be properly handled in all three aforementioned contexts.
 
 Use the full directory and filename from the Gutenberg repository, not the published path; the Block Editor Handbook creates short URLs—you can see this in the tutorials section. Likewise, the `readme.md` portion is dropped in the handbook, but should be included in links.
 
-An example, the link to this page is: `/docs/contributors/documentation/document.md`
+An example, the link to this page is: `/docs/contributors/documentation/documentation.md`
 
 ### Code Examples
 

docs/manifest.json

@@ -1759,69 +1759,69 @@
 	},
 	{
 		"title": "Code Contributions",
-		"slug": "develop",
-		"markdown_source": "../docs/contributors/code/develop.md",
+		"slug": "code",
+		"markdown_source": "../docs/contributors/code/code.md",
 		"parent": "contributors"
 	},
 	{
 		"title": "Getting Started",
 		"slug": "getting-started",
 		"markdown_source": "../docs/contributors/code/getting-started.md",
-		"parent": "develop"
+		"parent": "code"
 	},
 	{
 		"title": "Git Workflow",
 		"slug": "git-workflow",
 		"markdown_source": "../docs/contributors/code/git-workflow.md",
-		"parent": "develop"
+		"parent": "code"
 	},
 	{
 		"title": "Coding Guidelines",
 		"slug": "coding-guidelines",
 		"markdown_source": "../docs/contributors/code/coding-guidelines.md",
-		"parent": "develop"
+		"parent": "code"
 	},
 	{
 		"title": "Testing Overview",
 		"slug": "testing-overview",
 		"markdown_source": "../docs/contributors/code/testing-overview.md",
-		"parent": "develop"
+		"parent": "code"
 	},
 	{
 		"title": "Block Grammar",
 		"slug": "grammar",
 		"markdown_source": "../docs/contributors/code/grammar.md",
-		"parent": "develop"
+		"parent": "code"
 	},
 	{
 		"title": "Scripts",
 		"slug": "scripts",
 		"markdown_source": "../docs/contributors/code/scripts.md",
-		"parent": "develop"
+		"parent": "code"
 	},
 	{
 		"title": "Managing Packages",
 		"slug": "managing-packages",
 		"markdown_source": "../docs/contributors/code/managing-packages.md",
-		"parent": "develop"
+		"parent": "code"
 	},
 	{
 		"title": "Gutenberg Release Process",
 		"slug": "release",
 		"markdown_source": "../docs/contributors/code/release.md",
-		"parent": "develop"
+		"parent": "code"
 	},
 	{
 		"title": "React Native based mobile Gutenberg",
 		"slug": "native-mobile",
 		"markdown_source": "../docs/contributors/code/native-mobile.md",
-		"parent": "develop"
+		"parent": "code"
 	},
 	{
 		"title": "Getting Started for the React Native based Mobile Gutenberg",
 		"slug": "getting-started-native-mobile",
 		"markdown_source": "../docs/contributors/code/getting-started-native-mobile.md",
-		"parent": "develop"
+		"parent": "code"
 	},
 	{
 		"title": "Design Contributions",
@@ -1843,15 +1843,15 @@
 	},
 	{
 		"title": "Documentation Contributions",
-		"slug": "document",
-		"markdown_source": "../docs/contributors/documentation/document.md",
+		"slug": "documentation",
+		"markdown_source": "../docs/contributors/documentation/documentation.md",
 		"parent": "contributors"
 	},
 	{
 		"title": "Copy Guidelines",
 		"slug": "copy-guide",
 		"markdown_source": "../docs/contributors/documentation/copy-guide.md",
-		"parent": "document"
+		"parent": "documentation"
 	},
 	{
 		"title": "Triage",

docs/toc.json

@@ -147,7 +147,7 @@
         ] }
     ] },
     { "docs/contributors/README.md": [
-        { "docs/contributors/code/develop.md": [
+        { "docs/contributors/code/code.md": [
             { "docs/contributors/code/getting-started.md": [] },
             { "docs/contributors/code/git-workflow.md": [] },
             { "docs/contributors/code/coding-guidelines.md": [] },
@@ -163,7 +163,7 @@
             { "docs/contributors/design/the-block.md": [] },
             { "docs/contributors/design/reference.md": [] }
         ] },
-        { "docs/contributors/documentation/document.md": [
+        { "docs/contributors/documentation/documentation.md": [
             { "docs/contributors/documentation/copy-guide.md": [] }
         ] },
         { "docs/contributors/triage.md": [] },

packages/components/src/CONTRIBUTING.md

@@ -37,7 +37,7 @@ Once the team has discussed and approved the change, it's time to start implemen
 
 1. **Provide a rationale**: Explain how your component will add value to the system and the greater product ecosystem. Be sure to include any user experience and interaction descriptions.
 2. **Draft documentation**: New components need development, design, and accessibility guidelines. Additionally, if your change adds additional behavior or expands a component’s features, those changes will need to be fully documented as well. Read through existing component documentation for examples. Start with a rough draft, and reviewers will help polish documentation.
-3. **Provide working code**: The component or enhancement must be built in React. See the [developer contribution guidelines](https://github.com/WordPress/gutenberg/blob/HEAD/docs/contributors/code/develop.md).
+3. **Provide working code**: The component or enhancement must be built in React. See the [developer contribution guidelines](https://github.com/WordPress/gutenberg/blob/HEAD/docs/contributors/code/code.md).
 4. **Create a design spec**: Create sizing and styling annotations for all aspects of the component. This spec should provide a developer with everything they need to create the design in code. [Figma automatically does this for you](https://help.figma.com/article/32-developer-handoff).
 5. **Create a Figma component**: Any new components or changes to existing components will be mirrored in the [WordPress Components Figma library](https://www.figma.com/file/ZtN5xslEVYgzU7Dd5CxgGZwq/WordPress-Components?node-id=735%3A0), so we’ll need to update the Figma library and publish the changes. Please follow the [guidelines](https://www.figma.com/file/ZtN5xslEVYgzU7Dd5CxgGZwq/WordPress-Components?node-id=746%3A38) for contributing to the Figma libraries.