Navigation sync notes

Today, 22nd July 2020, in the #core SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at channel the weekly navigation sync meeting was held. This is a CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. meeting about everything Navigation: 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. and the navigation screen.

The agenda for today was:

  • Navigation screen project triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.
  • Open floor

We triaged all the issues in the Inbox column of the Navigation screen project.

During the open floor the following items were raised:

  • @andraganescu highlighted the Navigation: Non-link blocks should be wrapped in a
  • issue
    • We discussed the idea of adding a ClassicMenu block to enable the Navigation block to manage blocks and classic menus easier in the Navigation screen.
    • @ashiishme offered to create an issue for a new ClassicMenu block
  • It was discussed that during this chat we should also triage issues labeled [Block] Navigation that were opened in the last week, to check for items to add to the Navigation screen project.

Lastly, if you want to get involved in any way – design, code, bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub, testing – check out: