From 0de466ccdb44ecdc409e96c9f67c4b14ead8fc7f Mon Sep 17 00:00:00 2001 From: Dave Smith Date: Mon, 17 May 2021 15:15:32 +0100 Subject: [PATCH 1/8] Document different editor save and render modes --- packages/edit-navigation/README.md | 43 ++++++++++++++++++++++++++++++ 1 file changed, 43 insertions(+) diff --git a/packages/edit-navigation/README.md b/packages/edit-navigation/README.md index 08afd5dae7a813..08fb8ebfa6620e 100644 --- a/packages/edit-navigation/README.md +++ b/packages/edit-navigation/README.md @@ -20,6 +20,49 @@ import blockEditorSettings from './block-editor-settings'; initialize( '#navigation-editor-root', blockEditorSettings ); ``` +## Purpose + +By default, the Navigation Editor screen creates block based representations of menus allows users to create and edit complex menus using block-based UI. + +In addition to this the Navigation Editor has two "modes" for _persistence_ ("saving" navigations) and _rendering_: + +1. Default - navigations are saved to the _existing_ (post type powered) Menus system and rendered using standard Walker classes. +2. Block-based - navigations continue to be _saved_ using the existing post type system, but non-link blocks are saved (see technical implementation) and _rendered_ as blocks to provide access to the full power of the Navigation block (with some tradeoffs in terms of backwards compatibility). + +### Default Mode + +In this mode, navigations created in the Navigation Editor are stored using the _existing Menu post type_ (`nav_menu_item`) system. As this method matches that used in the _existing_ Menus screen, there is a smooth upgrade path to using new Navigation Editor screen to edit navigations. + +Moreover, when the navigation is rendered on the front of the site the system continues to use [the classic Navigation "Walker" class](https://developer.wordpress.org/reference/classes/walker_nav_menu/), thereby ensuring the HTML markup remains the same when using a classic Theme. + +### Block-based Mode + +If desired, themes are able to opt into _rendering_ complete block-based menus. This allows for arbitrarily complex Navigation block structures to be used in an existing theme whilst still ensuring the navigation data is still _saved_ to the existing (post type powered) Menus system. + +Themes can opt into this by declaring: + +```php +add_theme_support( 'block-nav-menus' ); +``` + +This unlocks significant additional capabilities in the Navigation Editor. For example, by default, the Navigation Editor screen only allows link blocks to be inserted into a navigation. When a theme opts into `block-nav-menus` however, users are able to add non-link blocks to a navigation using the Navigation Editor screen, including: + +- `core/navigation-link`. +- `core/social`. +- `core/search`. + +These are persisted as a `nav_menu_item` post with a type of `block` and when rendered on the frontend these are parsed and rendered as _blocks_. + +#### Technical Implementation details + +By default, `core/navigation-link` items are serialized and persisted as `nav_menu_item` posts. No serialized block HTML is stored for link blocks. + +Non-link navigation items however, are persisted as `nav_menu_items` with a special `type` of `block`. These items have an _additional_ `content` field which is used to store the serialized block markup. + +When rendered on the front-end, the blocks are `parse`d from the `content` field and rendered as blocks. + +If the user switches to a theme that does not support block menus, or disables this functionality, non-link blocks are no longer rendered on the frontend. Care is taken, however, to ensure that users can still see their data on the existing Menus screen. + ## Hooks `useMenuItems` and `useNavigationBlock` hooks are the central part of this package. They bridge the gap between the API and the block editor interface: From ec063563a34c56e7444b8e4337ca698004bbad64 Mon Sep 17 00:00:00 2001 From: Dave Smith Date: Mon, 17 May 2021 15:38:53 +0100 Subject: [PATCH 2/8] Add code references and correct grammar --- packages/edit-navigation/README.md | 28 ++++++++++++++++++---------- 1 file changed, 18 insertions(+), 10 deletions(-) diff --git a/packages/edit-navigation/README.md b/packages/edit-navigation/README.md index 08fb8ebfa6620e..f13b3b73140a59 100644 --- a/packages/edit-navigation/README.md +++ b/packages/edit-navigation/README.md @@ -22,12 +22,14 @@ initialize( '#navigation-editor-root', blockEditorSettings ); ## Purpose -By default, the Navigation Editor screen creates block based representations of menus allows users to create and edit complex menus using block-based UI. +By default, the Navigation Editor screen allows users to create and edit complex navigations using a block-based UI. The aim is to supercede the current Menus screen by providing a superior experience whilst retaining backwards compatibility. -In addition to this the Navigation Editor has two "modes" for _persistence_ ("saving" navigations) and _rendering_: +## Modes -1. Default - navigations are saved to the _existing_ (post type powered) Menus system and rendered using standard Walker classes. -2. Block-based - navigations continue to be _saved_ using the existing post type system, but non-link blocks are saved (see technical implementation) and _rendered_ as blocks to provide access to the full power of the Navigation block (with some tradeoffs in terms of backwards compatibility). +The Navigation Editor has two "modes" for _persistence_ ("saving" navigations) and _rendering_: + +1. **Default** - navigations are saved to the _existing_ (post type powered) Menus system and rendered using standard Walker classes. +2. **Block-based** (opt _in_) - navigations continue to be _saved_ using the existing post type system, but non-link blocks are saved (see technical implementation) and _rendered_ as blocks to provide access to the full power of the Navigation block (with some tradeoffs in terms of backwards compatibility). ### Default Mode @@ -37,15 +39,15 @@ Moreover, when the navigation is rendered on the front of the site the system co ### Block-based Mode -If desired, themes are able to opt into _rendering_ complete block-based menus. This allows for arbitrarily complex Navigation block structures to be used in an existing theme whilst still ensuring the navigation data is still _saved_ to the existing (post type powered) Menus system. +If desired, themes are able to opt into _rendering_ complete block-based menus using the Navigation Editor. This allows for arbitrarily complex navigation block structures to be used in an existing theme whilst still ensuring the navigation data is still _saved_ to the existing (post type powered) Menus system. -Themes can opt into this by declaring: +Themes can opt into this behaviour by declaring: ```php add_theme_support( 'block-nav-menus' ); ``` -This unlocks significant additional capabilities in the Navigation Editor. For example, by default, the Navigation Editor screen only allows link blocks to be inserted into a navigation. When a theme opts into `block-nav-menus` however, users are able to add non-link blocks to a navigation using the Navigation Editor screen, including: +This unlocks significant additional capabilities in the Navigation Editor. For example, by default, [the Navigation Editor screen only allows _link_ (`core/navigation-link`) blocks to be inserted into a navigation](https://github.com/WordPress/gutenberg/blob/7fcd57c9a62c232899e287f6d96416477d810d5e/packages/edit-navigation/src/filters/disable-inserting-non-navigation-blocks.js). When a theme opts into `block-nav-menus` however, users are able to add non-link blocks to a navigation using the Navigation Editor screen, including: - `core/navigation-link`. - `core/social`. @@ -55,11 +57,11 @@ These are persisted as a `nav_menu_item` post with a type of `block` and when re #### Technical Implementation details -By default, `core/navigation-link` items are serialized and persisted as `nav_menu_item` posts. No serialized block HTML is stored for link blocks. +By default, `core/navigation-link` items are serialized and persisted as `nav_menu_item` posts. No serialized block HTML is stored for these standard link blocks. -Non-link navigation items however, are persisted as `nav_menu_items` with a special `type` of `block`. These items have an _additional_ `content` field which is used to store the serialized block markup. +_Non_-link navigation items however, are [persisted as `nav_menu_items` with a special `type` of `block`](https://github.com/WordPress/gutenberg/blob/7fcd57c9a62c232899e287f6d96416477d810d5e/packages/edit-navigation/src/store/utils.js#L159-L166). These items have an [_additional_ `content` field which is used to store the serialized block markup](https://github.com/WordPress/gutenberg/blob/7fcd57c9a62c232899e287f6d96416477d810d5e/lib/navigation.php#L71-L101). -When rendered on the front-end, the blocks are `parse`d from the `content` field and rendered as blocks. +When rendered on the front-end, the blocks are [`parse`d from the `content` field](https://github.com/WordPress/gutenberg/blob/7fcd57c9a62c232899e287f6d96416477d810d5e/lib/navigation.php#L191-L203) and [rendered as blocks](https://github.com/WordPress/gutenberg/blob/7fcd57c9a62c232899e287f6d96416477d810d5e/lib/navigation.php#L103-L135). If the user switches to a theme that does not support block menus, or disables this functionality, non-link blocks are no longer rendered on the frontend. Care is taken, however, to ensure that users can still see their data on the existing Menus screen. @@ -102,6 +104,12 @@ return ( ); ``` +## Glossary + +- Link block - refers to the basic `core/navigation-link` block which is the standard block used to add links within navigations. +- Navigation block - refers to the root `core/navigation` block which can be used both with the Navigation Editor and outside (eg: Post / Site Editor). +- Navigation Editor screen - the new screen provided by Gutenberg to allow the user to edit navigations using a block-based UI. + _This package assumes that your code will run in an **ES2015+** environment. If you're using an environment that has limited or no support for ES2015+ such as IE browsers then using [core-js](https://github.com/zloirock/core-js) will add polyfills for these methods._

Code is Poetry.

From e2dfc0babdfee52bc624a37d162739078931b823 Mon Sep 17 00:00:00 2001 From: Dave Smith Date: Mon, 17 May 2021 15:42:25 +0100 Subject: [PATCH 3/8] Tidy unrequired sentances --- packages/edit-navigation/README.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/packages/edit-navigation/README.md b/packages/edit-navigation/README.md index f13b3b73140a59..45c3604dd810d2 100644 --- a/packages/edit-navigation/README.md +++ b/packages/edit-navigation/README.md @@ -53,8 +53,6 @@ This unlocks significant additional capabilities in the Navigation Editor. For e - `core/social`. - `core/search`. -These are persisted as a `nav_menu_item` post with a type of `block` and when rendered on the frontend these are parsed and rendered as _blocks_. - #### Technical Implementation details By default, `core/navigation-link` items are serialized and persisted as `nav_menu_item` posts. No serialized block HTML is stored for these standard link blocks. @@ -106,9 +104,9 @@ return ( ## Glossary -- Link block - refers to the basic `core/navigation-link` block which is the standard block used to add links within navigations. -- Navigation block - refers to the root `core/navigation` block which can be used both with the Navigation Editor and outside (eg: Post / Site Editor). -- Navigation Editor screen - the new screen provided by Gutenberg to allow the user to edit navigations using a block-based UI. +- **Link block** - the basic `core/navigation-link` block which is the standard block used to add links within navigations. +- **Navigation block** - the root `core/navigation` block which can be used both with the Navigation Editor and outside (eg: Post / Site Editor). +- **Navigation Editor screen** - the new screen provided by Gutenberg to allow the user to edit navigations using a block-based UI. _This package assumes that your code will run in an **ES2015+** environment. If you're using an environment that has limited or no support for ES2015+ such as IE browsers then using [core-js](https://github.com/zloirock/core-js) will add polyfills for these methods._ From 04f049d664a7cbfcc2d4c538973ff8023fdd4612 Mon Sep 17 00:00:00 2001 From: Dave Smith Date: Mon, 17 May 2021 16:01:30 +0100 Subject: [PATCH 4/8] Document menu item to block attribute mapping --- packages/edit-navigation/README.md | 34 +++++++++++++++++++++++++++++- 1 file changed, 33 insertions(+), 1 deletion(-) diff --git a/packages/edit-navigation/README.md b/packages/edit-navigation/README.md index 45c3604dd810d2..876618a9a6225b 100644 --- a/packages/edit-navigation/README.md +++ b/packages/edit-navigation/README.md @@ -63,6 +63,38 @@ When rendered on the front-end, the blocks are [`parse`d from the `content` fiel If the user switches to a theme that does not support block menus, or disables this functionality, non-link blocks are no longer rendered on the frontend. Care is taken, however, to ensure that users can still see their data on the existing Menus screen. +## Block to Menu Item mapping + +The Navigation Editor needs to be able to map navigation items in two directions: + +1. `nav_menu_item`s to Blocks - when displaying an existing navigation. +2. Blocks to `nav_menu_item`s - when _saving_ an navigation being editing in the Navigation screen. + +To understand this fully, one must first appreciate that WordPress maps raw `nav_menu_item` posts to Menu item _objects_. These have various properties which map to block attributes as follows: + +| Property | Description | Equivalent Block Attribute | +| :----------------- | :-------------------------------------------------------------------------------------------------------: | :----------------------------------------------------: | +| `ID` | The term_id if the menu item represents a taxonomy term. | Not mapped. | +| `attr_title` | The title attribute of the link element for this menu item. | `title` | +| `classes` | The array of class attribute values for the link element of this menu item. | `classNames` | +| `db_id` | The DB ID of this item as a nav_menu_item object, if it exists (0 if it doesn't exist). | Not mapped. | +| `description` | The description of this menu item. | `description` | +| `menu_item_parent` | The DB ID of the nav_menu_item that is this item's menu parent, if any. 0 otherwise. | Not mapped.[1](#menu_item_menu_item_parent) | +| `object` | The type of object originally represented, such as 'category', 'post', or 'attachment'. | `type` | +| `object_id` | The DB ID of the original object this menu item represents, e.g. ID for posts and term_id for categories. | `id` | +| `post_parent` | The DB ID of the original object's parent object, if any (0 otherwise). | Not mapped. | +| `post_title` | A "no title" label if menu item represents a post that lacks a title. | Not mapped. | +| `target` | The target attribute of the link element for this menu item. | `opensInNewTab`[2](#menu_item_target) | +| `title` | The title of this menu item. | `label` | +| `type` | The family of objects originally represented, such as 'post_type' or 'taxonomy'. | `kind` | +| `type_label` | The singular label used to describe this type of menu item. | Not mapped. | +| `url` | The URL to which this menu item points. | `url` | +| `xfn` | The XFN relationship expressed in the link of this menu item. | `rel` | +| `\_invalid` | Whether the menu item represents an object that no longer exists. | Not mapped. | + +- [1] - the parent -> child relationship is expressed in block via the `innerBlocks` attribute and is therefore not required as a explicit block attribute. +- [2] - applies only if the value of the `target` field is `_blank`. + ## Hooks `useMenuItems` and `useNavigationBlock` hooks are the central part of this package. They bridge the gap between the API and the block editor interface: @@ -106,7 +138,7 @@ return ( - **Link block** - the basic `core/navigation-link` block which is the standard block used to add links within navigations. - **Navigation block** - the root `core/navigation` block which can be used both with the Navigation Editor and outside (eg: Post / Site Editor). -- **Navigation Editor screen** - the new screen provided by Gutenberg to allow the user to edit navigations using a block-based UI. +- **Navigation editor / screen** - the new screen provided by Gutenberg to allow the user to edit navigations using a block-based UI. _This package assumes that your code will run in an **ES2015+** environment. If you're using an environment that has limited or no support for ES2015+ such as IE browsers then using [core-js](https://github.com/zloirock/core-js) will add polyfills for these methods._ From 164314c26e6bdd03a9d37b6bde1b4d606132054f Mon Sep 17 00:00:00 2001 From: Dave Smith Date: Mon, 17 May 2021 16:15:46 +0100 Subject: [PATCH 5/8] Bring mappings adjacent to each other. Improve documenting inconsistencies. --- packages/edit-navigation/README.md | 62 ++++++++++++++++++++---------- 1 file changed, 41 insertions(+), 21 deletions(-) diff --git a/packages/edit-navigation/README.md b/packages/edit-navigation/README.md index 876618a9a6225b..1371be3a44a72c 100644 --- a/packages/edit-navigation/README.md +++ b/packages/edit-navigation/README.md @@ -70,31 +70,51 @@ The Navigation Editor needs to be able to map navigation items in two directions 1. `nav_menu_item`s to Blocks - when displaying an existing navigation. 2. Blocks to `nav_menu_item`s - when _saving_ an navigation being editing in the Navigation screen. -To understand this fully, one must first appreciate that WordPress maps raw `nav_menu_item` posts to Menu item _objects_. These have various properties which map to block attributes as follows: - -| Property | Description | Equivalent Block Attribute | -| :----------------- | :-------------------------------------------------------------------------------------------------------: | :----------------------------------------------------: | -| `ID` | The term_id if the menu item represents a taxonomy term. | Not mapped. | -| `attr_title` | The title attribute of the link element for this menu item. | `title` | -| `classes` | The array of class attribute values for the link element of this menu item. | `classNames` | -| `db_id` | The DB ID of this item as a nav_menu_item object, if it exists (0 if it doesn't exist). | Not mapped. | -| `description` | The description of this menu item. | `description` | -| `menu_item_parent` | The DB ID of the nav_menu_item that is this item's menu parent, if any. 0 otherwise. | Not mapped.[1](#menu_item_menu_item_parent) | -| `object` | The type of object originally represented, such as 'category', 'post', or 'attachment'. | `type` | -| `object_id` | The DB ID of the original object this menu item represents, e.g. ID for posts and term_id for categories. | `id` | -| `post_parent` | The DB ID of the original object's parent object, if any (0 otherwise). | Not mapped. | -| `post_title` | A "no title" label if menu item represents a post that lacks a title. | Not mapped. | -| `target` | The target attribute of the link element for this menu item. | `opensInNewTab`[2](#menu_item_target) | -| `title` | The title of this menu item. | `label` | -| `type` | The family of objects originally represented, such as 'post_type' or 'taxonomy'. | `kind` | -| `type_label` | The singular label used to describe this type of menu item. | Not mapped. | -| `url` | The URL to which this menu item points. | `url` | -| `xfn` | The XFN relationship expressed in the link of this menu item. | `rel` | -| `\_invalid` | Whether the menu item represents an object that no longer exists. | Not mapped. | +The Navigation Editor has two dedicated methods for handling mapping between these two expressions of the data: + +- [`menuItemToBlockAttributes()`](https://github.com/WordPress/gutenberg/blob/7fcd57c9a62c232899e287f6d96416477d810d5e/packages/edit-navigation/src/store/utils.js#L261-L313). +- [`blockAttributestoMenuItem()`](https://github.com/WordPress/gutenberg/blob/7fcd57c9a62c232899e287f6d96416477d810d5e/packages/edit-navigation/src/store/utils.js#L184-L253) + +To understand these fully, one must appreciate that WordPress maps raw `nav_menu_item` posts to [Menu item _objects_](https://core.trac.wordpress.org/browser/tags/5.7.1/src/wp-includes/nav-menu.php#L786). These have various properties which map as follows: + +| Menu Item object property | Equivalent Block Attribute | Description | +| :------------------------ | :----------------------------------------------------: | :-------------------------------------------------------------------------------------------------------: | +| `ID` | Not mapped. | The term_id if the menu item represents a taxonomy term. | +| `attr_title` | `title` | The title attribute of the link element for this menu item. | +| `classes` | `classNames` | The array of class attribute values for the link element of this menu item. | +| `db_id` | Not mapped. | The DB ID of this item as a nav_menu_item object, if it exists (0 if it doesn't exist). | +| `description` | `description` | The description of this menu item. | +| `menu_item_parent` | Not mapped.[1](#menu_item_menu_item_parent) | The DB ID of the nav_menu_item that is this item's menu parent, if any. 0 otherwise. | +| `object` | `type` | The type of object originally represented, such as 'category', 'post', or 'attachment'. | +| `object_id` | `id` | The DB ID of the original object this menu item represents, e.g. ID for posts and term_id for categories. | +| `post_parent` | Not mapped. | The DB ID of the original object's parent object, if any (0 otherwise). | +| `post_title` | Not mapped. | A "no title" label if menu item represents a post that lacks a title. | +| `target` | `opensInNewTab`[2](#menu_item_target) | The target attribute of the link element for this menu item. | +| `title` | `label` | The title of this menu item. | +| `type` | `kind` | The family of objects originally represented, such as 'post_type' or 'taxonomy'. | +| `type_label` | Not mapped. | The singular label used to describe this type of menu item. | +| `url` | `url` | The URL to which this menu item points. | +| `xfn` | `rel` | The XFN relationship expressed in the link of this menu item. | +| `\_invalid` | Not mapped. | Whether the menu item represents an object that no longer exists. | - [1] - the parent -> child relationship is expressed in block via the `innerBlocks` attribute and is therefore not required as a explicit block attribute. - [2] - applies only if the value of the `target` field is `_blank`. +### Inconsistencies + +#### Mapping + +For historical reasons, the following properties display some inconsistency in their mapping from Menu Item Object to Block attribute: + +- `type` -> `kind` - the family of objects is stored as `kind` on the block and so must be mapped accordingly. +- `object` -> `type` - the type of object is stored as `type` on the block and so must be mapped accordingly. +- `object_id` -> `id` - the block stores a reference to the original object's ID as the `id` _attribute_. This should not be confused with the block's `clientId` which is unrelated. +- `attr_title` -> `title` - the HTML `title` attribute is stored as `title` on the block and so must be mapped accordingly. + +#### Object Types + +- Menu Item objects which represent "Tags" are stored in WordPress as `post_tag` but the block expects their `type` attribute to be `tag` (omiting the `post_` suffix). This inconsistency is accounted for in [the mapping utilities methods](https://github.com/WordPress/gutenberg/blob/7fcd57c9a62c232899e287f6d96416477d810d5e/packages/edit-navigation/src/store/utils.js#L279-L281). + ## Hooks `useMenuItems` and `useNavigationBlock` hooks are the central part of this package. They bridge the gap between the API and the block editor interface: From 24e92b7545ab6984e3ba472fb680db8f74127a98 Mon Sep 17 00:00:00 2001 From: Dave Smith Date: Mon, 17 May 2021 16:18:10 +0100 Subject: [PATCH 6/8] Add helpful links --- packages/edit-navigation/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/packages/edit-navigation/README.md b/packages/edit-navigation/README.md index 1371be3a44a72c..0480905faef4cc 100644 --- a/packages/edit-navigation/README.md +++ b/packages/edit-navigation/README.md @@ -22,7 +22,7 @@ initialize( '#navigation-editor-root', blockEditorSettings ); ## Purpose -By default, the Navigation Editor screen allows users to create and edit complex navigations using a block-based UI. The aim is to supercede the current Menus screen by providing a superior experience whilst retaining backwards compatibility. +By default, the Navigation Editor screen allows users to create and edit complex navigations using a block-based UI. The aim is to supercede [the current Menus screen](https://codex.wordpress.org/WordPress_Menu_User_Guide) by providing a superior experience whilst retaining backwards compatibility. ## Modes @@ -159,7 +159,7 @@ return ( - **Link block** - the basic `core/navigation-link` block which is the standard block used to add links within navigations. - **Navigation block** - the root `core/navigation` block which can be used both with the Navigation Editor and outside (eg: Post / Site Editor). - **Navigation editor / screen** - the new screen provided by Gutenberg to allow the user to edit navigations using a block-based UI. - -_This package assumes that your code will run in an **ES2015+** environment. If you're using an environment that has limited or no support for ES2015+ such as IE browsers then using [core-js](https://github.com/zloirock/core-js) will add polyfills for these methods._ +- **Menus screen** - the current/existing [interface/screen for managing Menus](https://codex.wordpress.org/WordPress_Menu_User_Guide) in WordPress WPAdmin. + _This package assumes that your code will run in an **ES2015+** environment. If you're using an environment that has limited or no support for ES2015+ such as IE browsers then using [core-js](https://github.com/zloirock/core-js) will add polyfills for these methods._

Code is Poetry.

From 9be12e7e6ac2dfaae8be91bbf31d54a04044ca82 Mon Sep 17 00:00:00 2001 From: Dave Smith Date: Mon, 17 May 2021 16:25:40 +0100 Subject: [PATCH 7/8] Quick ref to the block --- packages/edit-navigation/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/packages/edit-navigation/README.md b/packages/edit-navigation/README.md index 0480905faef4cc..359d5629719eec 100644 --- a/packages/edit-navigation/README.md +++ b/packages/edit-navigation/README.md @@ -24,6 +24,8 @@ initialize( '#navigation-editor-root', blockEditorSettings ); By default, the Navigation Editor screen allows users to create and edit complex navigations using a block-based UI. The aim is to supercede [the current Menus screen](https://codex.wordpress.org/WordPress_Menu_User_Guide) by providing a superior experience whilst retaining backwards compatibility. +The editing experience is provided as a block editor wrapper around the core functionality of the **Navigation _block_**. Features of the block are disabled/enhanced as necessary to provide an experience appropriate to editing a navigation outside of a Full Site Editing context. + ## Modes The Navigation Editor has two "modes" for _persistence_ ("saving" navigations) and _rendering_: From b7441f4e6ef23c99e03987b95a5cb98dac30e970 Mon Sep 17 00:00:00 2001 From: Dave Smith Date: Mon, 17 May 2021 16:28:37 +0100 Subject: [PATCH 8/8] Seperate out the colophon --- packages/edit-navigation/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/packages/edit-navigation/README.md b/packages/edit-navigation/README.md index 359d5629719eec..1ee150967f8697 100644 --- a/packages/edit-navigation/README.md +++ b/packages/edit-navigation/README.md @@ -162,6 +162,7 @@ return ( - **Navigation block** - the root `core/navigation` block which can be used both with the Navigation Editor and outside (eg: Post / Site Editor). - **Navigation editor / screen** - the new screen provided by Gutenberg to allow the user to edit navigations using a block-based UI. - **Menus screen** - the current/existing [interface/screen for managing Menus](https://codex.wordpress.org/WordPress_Menu_User_Guide) in WordPress WPAdmin. - _This package assumes that your code will run in an **ES2015+** environment. If you're using an environment that has limited or no support for ES2015+ such as IE browsers then using [core-js](https://github.com/zloirock/core-js) will add polyfills for these methods._ + +_This package assumes that your code will run in an **ES2015+** environment. If you're using an environment that has limited or no support for ES2015+ such as IE browsers then using [core-js](https://github.com/zloirock/core-js) will add polyfills for these methods._

Code is Poetry.