Improve the block editor handbook table of content

docs/contributors/getting-started.md → docs/contributors/code/getting-started.md

@@ -1,12 +1,12 @@
 # Getting Started
 
-The following guide is for setting up your local environment to contribute to the Gutenberg project. There is significant overlap between an environment to contribute and an environment used to extend the WordPress block editor. You can review the [Development Environment tutorial](/docs/designers-developers/developers/tutorials/devenv/readme.md) for additional setup information.
+The following guide is for setting up your local environment to contribute to the Gutenberg project. There is significant overlap between an environment to contribute and an environment used to extend the WordPress block editor. You can review the [Development Environment tutorial](/docs/getting-started/tutorials/devenv/readme.md) for additional setup information.
 
 ## Development Tools (Node)
 
 Gutenberg is a JavaScript project and requires [Node.js](https://nodejs.org/). The project is built using the latest active LTS release of node, and the latest version of NPM. See the [LTS release schedule](https://github.com/nodejs/Release#release-schedule) for details.
 
-We recommend using the [Node Version Manager](https://github.com/nvm-sh/nvm) (nvm) since it is the easiest way to install and manage node for macOS, Linux, and Windows 10 using WSL2. See [our Development Tools guide](/docs/designers-developers/developers/tutorials/devenv/readme.md#development-tools) or the Nodejs site for additional installation instructions.
+We recommend using the [Node Version Manager](https://github.com/nvm-sh/nvm) (nvm) since it is the easiest way to install and manage node for macOS, Linux, and Windows 10 using WSL2. See [our Development Tools guide](/docs/getting-started/tutorials/devenv/readme.md#development-tools) or the Nodejs site for additional installation instructions.
 
 After installing Node, you can build Gutenberg by running the following from within the cloned repository:
 
@@ -34,7 +34,7 @@ The [wp-env package](/packages/env/README.md) was developed with the Gutenberg p
 
 By default, `wp-env` can run in a plugin directory to create and run a WordPress environment, mounting and activating the plugin automatically. You can also configure `wp-env` to use existing installs, multiple plugins, or themes. See the [wp-env package](/packages/env/README.md#wp-envjson) for complete documentation.
 
-If you don't already have it, you'll need to install Docker and Docker Compose in order to use `wp-env`. See the [Development Environment tutorial for additional details](/docs/designers-developers/developers/tutorials/devenv/readme.md).
+If you don't already have it, you'll need to install Docker and Docker Compose in order to use `wp-env`. See the [Development Environment tutorial for additional details](/docs/getting-started/tutorials/devenv/readme.md).
 
 Once Docker is installed and running: To install WordPress, run the following from within the cloned gutenberg directory:
 

docs/contributors/reference.md → docs/contributors/design/reference.md

@@ -1,9 +1,9 @@
 # Reference
 
--   [Glossary](/docs/designers-developers/glossary.md)
+-   [Glossary](/docs/getting-started/glossary.md)
 -   [Coding Guidelines](/docs/contributors/coding-guidelines.md)
 -   [Testing Overview](/docs/contributors/testing-overview.md)
--   [Frequently Asked Questions](/docs/designers-developers/faq.md)
+-   [Frequently Asked Questions](/docs/getting-started/faq.md)
 
 ## Logo
 
@@ -15,4 +15,4 @@ Released under GPL license, made by [Cristel Rossignol](https://twitter.com/cris
 
 ## Mockups
 
-Mockup Sketch files are available in [the Design section](/docs/designers-developers/designers/design-resources.md).
+Mockup Sketch files are available in [the Design section](/docs/howto-guides/designers/design-resources.md).

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

@@ -39,7 +39,7 @@ To update an existing page:
 
 ### Create a New Document
 
-To add a new documentation page requires a working JavaScript development environment to build the documentation, see the [JavaScript build setup documentation](/docs/designers-developers/developers/tutorials/javascript/js-build-setup.md):
+To add a new documentation page requires a working JavaScript development environment to build the documentation, see the [JavaScript build setup documentation](/docs/howto-guides/javascript/js-build-setup.md):
 
 1. Create a Markdown file in the [docs](https://github.com/WordPress/gutenberg/tree/HEAD/docs) folder, use lower-case, no spaces, if needed a dash separator, and .md extension.
 2. Add content, all documents require one and only H1 tag, using markdown notation.
@@ -73,7 +73,7 @@ An example, the link to this page is: `/docs/contributors/document.md`
 
 The code example in markdown should be wrapped in three tick marks \`\`\` and should additionally include a language specifier. See this [GitHub documentation around fenced code blocks](https://help.github.com/en/github/writing-on-github/creating-and-highlighting-code-blocks).
 
-A unique feature to the Gutenberg documentation is the `codetabs` toggle, this allows two versions of code to be shown at once. This is used for showing both `ESNext` and `ES5` code samples. For example, [on this block tutorial page](/docs/designers-developers/developers/tutorials/block-tutorial/block-controls-toolbar-and-sidebar.md).
+A unique feature to the Gutenberg documentation is the `codetabs` toggle, this allows two versions of code to be shown at once. This is used for showing both `ESNext` and `ES5` code samples. For example, [on this block tutorial page](/docs/howto-guides/block-tutorial/block-controls-toolbar-and-sidebar.md).
 
 Here is an example `codetabs` section:
 

docs/architecture/fse-templates.md → docs/explanations/full-site-editing-templates.md

@@ -2,7 +2,7 @@
 
 > This is the documentation for the current implementation of the block-based templates and template parts themes. This is part of the Full Site Editing project. These features are still experimental in the plugin. “Experimental” means this is just an early implementation that is subject to potential drastic and breaking changes in iterations based on feedback from users, contributors, and theme authors.
 
-This document will explain the internals of how templates and templates parts are rendered in the frontend and edited in the backend. For an introduction about block-based themes and Full site editing templates, refer to the [block-based themes documentation](/docs/designers-developers/developers/themes/block-based-themes.md).
+This document will explain the internals of how templates and templates parts are rendered in the frontend and edited in the backend. For an introduction about block-based themes and Full site editing templates, refer to the [block-based themes documentation](/docs/howto-guides/themes/block-based-themes.md).
 
 ## Storage
 

docs/readme.md → docs/getting-started/README.md

@@ -22,19 +22,19 @@ The Editor offers rich new value to users with visual, drag-and-drop creation to
 
 ### Create a Block Tutorial
 
-[Learn how to create your first block](/docs/designers-developers/developers/tutorials/create-block/readme.md) for the WordPress block editor. From setting up your development environment, tools, and getting comfortable with the new development model, this tutorial covers all what you need to know to get started with the block editor.
+[Learn how to create your first block](/docs/getting-started/tutorials/create-block/readme.md) for the WordPress block editor. From setting up your development environment, tools, and getting comfortable with the new development model, this tutorial covers all what you need to know to get started with the block editor.
 
 ### Develop for the block editor
 
-Whether you want to extend the functionality of the block editor, or create a plugin based on it, [see the developer documentation](/docs/designers-developers/developers/README.md) to find all the information about the basic concepts you need to get started, the block editor APIs and its architecture.
+Whether you want to extend the functionality of the block editor, or create a plugin based on it, [see the developer documentation](/docs/howto-guides/README.md) to find all the information about the basic concepts you need to get started, the block editor APIs and its architecture.
 
 - [Gutenberg Architecture](/docs/architecture/readme.md)
-- [Block Style Variations](/docs/designers-developers/developers/filters/block-filters.md#block-style-variations)
-- [Creating Block Patterns](/docs/designers-developers/developers/block-api/block-patterns.md)
-- [Theming for the Block Editor](/docs/designers-developers/developers/themes/readme.md)
-- [Block API Reference](/docs/designers-developers/developers/block-api/readme.md)
-- [Block Editor Accessibility](/docs/designers-developers/developers/accessibility.md)
-- [Internationalization](/docs/designers-developers/developers/internationalization.md)
+- [Block Style Variations](/docs/reference-guides/filters/block-filters.md#block-style-variations)
+- [Creating Block Patterns](/docs/reference-guides/block-api/block-patterns.md)
+- [Theming for the Block Editor](/docs/howto-guides/themes/readme.md)
+- [Block API Reference](/docs/reference-guides/block-api/readme.md)
+- [Block Editor Accessibility](/docs/reference-guides/accessibility.md)
+- [Internationalization](/docs/howto-guides/internationalization.md)
 
 ### Contribute to the block editor
 

docs/architecture/data-flow.md → docs/getting-started/architecture/data-flow.md

@@ -104,7 +104,7 @@ After running this through the parser, we're left with a simple object we can ma
 
 This has dramatic implications for how simple and performant we can make our parser. These explicit boundaries also protect damage in a single block from bleeding into other blocks or tarnishing the entire document. It also allows the system to identify unrecognized blocks before rendering them.
 
-_N.B.:_ The defining aspects of blocks are their semantics and the isolation mechanism they provide: in other words, their identity. On the other hand, where their data is stored is a more liberal aspect. Blocks support more than just static local data (via JSON literals inside the HTML comment or within the block's HTML), and more mechanisms (_e.g._, global blocks or otherwise resorting to storage in complementary `WP_Post` objects) are expected. See [attributes](/docs/designers-developers/developers/block-api/block-attributes.md) for details.
+_N.B.:_ The defining aspects of blocks are their semantics and the isolation mechanism they provide: in other words, their identity. On the other hand, where their data is stored is a more liberal aspect. Blocks support more than just static local data (via JSON literals inside the HTML comment or within the block's HTML), and more mechanisms (_e.g._, global blocks or otherwise resorting to storage in complementary `WP_Post` objects) are expected. See [attributes](/docs/reference-guides/block-api/block-attributes.md) for details.
 
 ### The Anatomy of a Serialized Block