Title: Navigation block exclusion from WP 5.4
Author: Mark Uraine
Published: February 7, 2020

---

 [  ](https://profiles.wordpress.org/mapk/) [Mark Uraine](https://profiles.wordpress.org/mapk/)
10:02 pm _on_ February 7, 2020     
Tags: [5.4 ( 53 )](https://make.wordpress.org/core/tag/5-4/),
[gutenberg ( 553 )](https://make.wordpress.org/core/tag/gutenberg/)   

# Navigation block exclusion from WP 5.4

After [plenty of great discussions](https://wordpress.slack.com/archives/C02RQBWTW/p1580937309153900)
about the Navigation blockBlock Block is the abstract term used to describe units
of markup that, composed together, form the content or layout of a webpage using
the WordPress editor. The idea combines concepts of what in the past may have achieved
with shortcodes, custom HTML, and embed discovery into a single consistent API and
user experience. recently, the GutenbergGutenberg The Gutenberg project is the new
Editor Interface for WordPress. The editor improves the process and experience of
creating new content, making writing rich content much simpler. It uses ‘blocks’
to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
Team, including Dev Lead [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/)
and me ( I’m the Design Lead), has decided not to include it in the WordPress 5.4
release.

We’ve been sharing this decision with the Release Squad for 5.4 and among many seasoned
contributors to get a perspective on how everyone felt about this. The general consensus:
people understand why the Gutenberg Team has made this call, and they support the
decision.

![](https://make.wordpress.org/core/files/2020/02/Nav-block.png)

Navigation block

## Historical context

The Navigation block was a [priority project for 2019](https://make.wordpress.org/core/2019/12/06/update-9-projects-for-2019/).
It was also [planned for the WordPress 5.4 release](https://make.wordpress.org/core/2020/01/14/wordpress-5-4-planning-roundup/).
So we absolutely did not make this decision lightly. Ultimately, we recognize that
although the block itself is ready to merge into CoreCore Core is the set of software
required to run WordPress. The Core Development Team builds WordPress., the Gutenberg
Team believes this move is premature.

## Why?

As I said, the Navigation block is _usable_ right now. But we don’t think it’s _useful_
yet – at least not until it has an intuitive place to live.

It’s hard to imagine cases where users would want to add a Navigation block to the
post or page content. It’s much more likely that a given user would want to add 
a Navigation block to HeaderHeader The header of your site is typically the first
thing people will experience. The masthead or header art located across the top 
of your page is part of the look and feel of your website. It can influence a visitor’s
opinion about your content and you/ your organization’s brand. It may also look 
different on different screen sizes. or Footer block areas – maybe even a SidebarSidebar
A sidebar in WordPress is referred to a widget-ready area used by WordPress themes
to display information that is not a part of the main content. It is not always 
a vertical column on the side. It can be a horizontal rectangle below or above the
content area, footer, header, or any where in the theme.. However, that functionality
in Gutenberg just isn’t ready.

Now, let me add this: if a user does want a set of links in a page, the new [Buttons block](https://github.com/WordPress/gutenberg/pull/17352)
in WordPress 5.4 can probably meet that need.

![](https://make.wordpress.org/core/files/2020/02/buttons-block.png)

Buttons block

As I look back at the WordPress Project’s to-do list for 2019, the Navigation block
didn’t exist in a vacuum. There was also the matter of Themes registering content
areas which is still in progress as we speak. Both of those should co-exist and 
be released together. To include the Navigation block without a proper home isn’t
really useful for users, and it doesn’t seem to justify a feature mention in the
5.4 release.

## Going forward

Our next steps include adding a few more features to the block:

 * Creating a new page from within the block ([19775](https://github.com/WordPress/gutenberg/pull/19775)).
 * Creating a Navigation block based on existing menu structures ([18869](https://github.com/WordPress/gutenberg/pull/18869)).
 * Indicating “current” menu items visually ([20076](https://github.com/WordPress/gutenberg/pull/20076)).

So that’s what’s happening with the Navigation Block and WordPress 5.4.

I want to ask you, personally, to join us in Core and in the Gutenberg Team discussions
and give us your thoughts. Please review this block, to help further testing around
it.

I’ll be picking up usability testing for this block again soon, and I’m looking 
forward to hearing from you how we can improve it.

And don’t forget to install the [Gutenberg plugin](https://wordpress.org/plugins/gutenberg/)
to test the Navigation block in near-real-world conditions. With your feedback, 
we can make this block a great success.

[#5-4](https://make.wordpress.org/core/tag/5-4/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/)

### Share this:

 * [  Threads ](https://make.wordpress.org/core/2020/02/07/navigation-block-exclusion-from-wp-5-4/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/core/2020/02/07/navigation-block-exclusion-from-wp-5-4/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/core/2020/02/07/navigation-block-exclusion-from-wp-5-4/?share=bluesky)
 * [  X ](https://make.wordpress.org/core/2020/02/07/navigation-block-exclusion-from-wp-5-4/?share=x)
 * [  Facebook ](https://make.wordpress.org/core/2020/02/07/navigation-block-exclusion-from-wp-5-4/?share=facebook)
 * [  LinkedIn ](https://make.wordpress.org/core/2020/02/07/navigation-block-exclusion-from-wp-5-4/?share=linkedin)

 1.  ![](https://secure.gravatar.com/avatar/ea8b05a71fdd554f4d9b8d4ae4633f11f347dc99b64221166ee22c94d9bdb066?
     s=32&d=mm&r=g)
 2.   Anonymous User  2:25 pm _on_ February 8, 2020
 3.  You guys made the correct decision 👍
 4.  ![](https://secure.gravatar.com/avatar/6cce48d5b3d8e19f5985ef7e189d6e98031d4059c73b9a2428f42a5b533c95a2?
     s=32&d=mm&r=g)
 5.   [Lenin Zapata ☄](https://profiles.wordpress.org/ilenstudio/)  7:14 pm _on_ February
     25, 2020
 6.  I am creating a customizable WordPress Theme with CSSCSS Cascading Style Sheets.
     variables, I hope it will be useful when I release it.
 7.  ![](https://secure.gravatar.com/avatar/4b78502505bab8a59e53f04cb5c12f824b5830566a22a4c716ee0a254031c46d?
     s=32&d=mm&r=g)
 8.   [wputler](https://profiles.wordpress.org/wputler/)  9:57 pm _on_ March 2, 2020
 9.  Today I needed to add a menu of pages to some page content. I knew I had read 
     about the GutenbergGutenberg The Gutenberg project is the new Editor Interface
     for WordPress. The editor improves the process and experience of creating new 
     content, making writing rich content much simpler. It uses ‘blocks’ to add richness
     rather than shortcodes, custom HTML etc.
      [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
     Navigation Link blockBlock Block is the abstract term used to describe units of
     markup that, composed together, form the content or layout of a webpage using 
     the WordPress editor. The idea combines concepts of what in the past may have 
     achieved with shortcodes, custom HTML, and embed discovery into a single consistent
     API and user experience. and looked for it, but now I see why it wasn’t there.
     I’m doing a site without sidebars and I want a menu of sub-pages, so there is 
     one imaginable case.
 10.  * ![](https://secure.gravatar.com/avatar/c5876422a37fd6194f1443154e5b8dc0920c99df2e3cc83f3d146bf34992abc5?
        s=32&d=mm&r=g)
      *  [Mark Uraine](https://profiles.wordpress.org/mapk/)  5:01 am _on_ March 3,
        2020
      * Thanks wputler. In that case, you can still access that blockBlock Block is
        the abstract term used to describe units of markup that, composed together,
        form the content or layout of a webpage using the WordPress editor. The idea
        combines concepts of what in the past may have achieved with shortcodes, custom
        HTML, and embed discovery into a single consistent API and user experience.
        by using the GutenbergGutenberg The Gutenberg project is the new Editor Interface
        for WordPress. The editor improves the process and experience of creating new
        content, making writing rich content much simpler. It uses ‘blocks’ to add 
        richness rather than shortcodes, custom HTML etc.
         [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
        pluginPlugin A plugin is a piece of software containing a group of functions
        that can be added to a WordPress website. They can extend functionality or 
        add new features to your WordPress websites. WordPress plugins are written 
        in the PHP programming language and integrate seamlessly with WordPress. These
        can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
        or can be cost-based plugin from a third-party.. For now, it’s just not merging
        into CoreCore Core is the set of software required to run WordPress. The Core
        Development Team builds WordPress..

Comments are closed.

# Post navigation

[← Release Model Working Group Chat Summary: February 5th, 2020](https://make.wordpress.org/core/2020/02/06/release-model-working-group-chat-summary-february-5th-2020/)

[Dev Chat summary – February 5, 2020 (5.4 week 4) →](https://make.wordpress.org/core/2020/02/08/dev-chat-summary-february-5-2020-5-4-week-4/)