Exploring a Nav block at WordCamp US

At Core Contributor day in WCUS the Design team spent time thinking about the next phase of Gutenberg, and explored what a block interface would look like in more sites and across more parts of the entire site experience.

During the day we split into several teams, each tackling this problem from a separate angle. In my team we ended up diving more deeply into the navigation block, and what all it entails.

So, here’s some of our findings. We began by trying to figure out what a block with navigational elements would look like, and where it would fit in.

Our first sketch with a Navigation block

The first problem we were trying to think through was what settings and visual elements would be needed for a navigation block. Also, where should a navigation block go? What if you don’t just want it in the header?

From there we play with some further ideas. 

This definitely wouldn’t work as a solution, but we knew the direction was worth pursuing. If the Nav block could live in a container block (columns perhaps), then the settings for it could be tweaked in the sidebar.

A further problem comes up when you try to figure out how much of the design of the nav should be controlled by the theme vs the Gutenberg editor. A great problem to be considered at a future time!

Props to @amitrathik, @mikeselander, @hajjflemings, @Bridget Brown for the great thoughts and contributions!