Our vision is to be the go-to resource for design for other teams across the WordPress open sourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project.
At CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.Contributor dayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. in WCUS the Design team spent time thinking about the next phase of GutenbergGutenbergThe 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/, and explored what a blockBlockBlock 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. 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.
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 headerHeaderThe 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.?
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 sidebarSidebarA 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..
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!