On Wednesday Aug 19, 7 AM UTC the weekly core navigation sync chat was held in the core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel on Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..
The format followed the same script:
During triage a few issues were removed from the Navigation editor project (not closed) as they are not critical for the Navigation editor’s functionality.
During open floor, @noisysocks shared the link to last week’s demo of the Navigation editor in a hallway hangout in Zoom.
@andraganescu brought up removing the experimental flag for the Navigation editor. Removing the experimental flag of the navigation editor makes it visible by default, without enabling it, if one has the Gutenberg 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/ plugin 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/ or can be cost-based plugin from a third-party running on the website.
After some discussion the consensus was that since the Navigation editor is “architecturally stable” we can show it as an optional screen in the Gutenberg plugin, but it’s not ready yet to replace the current screens.
@noisysocks announced he and @isabel_brison triaged the Widgets editor project board and that there are lots of actionable tasks there!
Thank you for reading, see you next time on Wednesday Aug 26, 7 AM UTC