Editor chat summary: 2nd December 2020

This post summarizes the weekly editor chat meeting (agenda here) held on 2020-12-02 14:00 UTC in Slack. Moderated by @andraganescu

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/ 9.5 Recap

• Full details on the release are available in the release post.
• Full Site Editing and Global styles were the main focus of this release and as always many bugs were fixed and some nice features were introduced.
• @youknowriad mentioned that during the release process an “undefined” tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) was temporarily temporarily created. It should be fixed now.

Preparation for WordPress 5.6

• Release candidate #2 (RC2) has been released.
• Make sure to take this release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). for spin and if you find any pesky bugs add them to Github
• The current editor must haves board is, as always in the 5.6 Project board

Monthly Plan & Key Project updates

• The December monthly plan is out (courtesy of @annezazu).
• We then requested updates on the key projects.

Global Styles & Editor focused APIs

Continued fixing the flows (tracking issue, label) and this week’s highlights are:

• Landed a fix for presets (they can now use other CSSCSS Cascading Style Sheets. variables defined as presets as well, i.e.: a gradiend defined based on a solid color).
• A few more PRs in the queue: padding control UI, preset internationalization.
• Conversation about how to control design tools visibility.

Full Site Editing

• Just in case that if you were previously following this project board for Full Site Editing, it has now been closed in order to use the milestones issues more consistently and to prevent people from needing to follow the progress in two places.
• The “template mode” in the post editor is close to landing. This is just a first iteration but I believe this might become an important way in which a lot of users might start interacting with FSE templates (PR: 26355)

Widgets screen, Navigation screen and CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.

For Widgets and the Customizer the updates are in the form of a renewed focus and also the current blocks in the customizer exploration phase.

Task Coordination

• @nosolosw
  • Main focus still is GlobalStyles: reviews, move forward my own PRs, triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. issues.
  • Started digging into FSE to add support for child themes.
• @ntsekouras
  • Add vertical layout to Buttons 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. with block variations (https://github.com/WordPress/gutenberg/pull/27297).
  • I’m working on block variations and a way to display the variation’s info in needed places, such as BlockCard, Navigation List view etc..
• @q
  • I’ve been focusing on the next iteration of the Gutenberg UIUI User interface (WordPress Components) – codenamed “G2 Components”.
  • I’ve been continuing my (almost) daily live streams covering design, development, architecture, and planning for this project :).
  • I recently published a blog post with progress updates and thoughts/details on how we’re planning the delivery of the project:
• @paaljoachim
  • Improving the Block Editor handbook intro page and improving Handbook design.
  • I also made a dev site for consolidating Handbooks into a kind of index page. 
  • I have also been running triages and design feedback sessions.
• @aristath
  • I continue working on splitting the block assets and only load them when a block is rendered (PR 25220)
  • Exploring how to remove auto-drafts for unedited templates and instead use the files directly (PR 27321)
  • Focusing on FSE & global-styles
• @annezazu
  • wrangled the What’s Next post for December
  • worked on some 5.6 related posts
  • helped triage the project management automation board with @noisysocks
  • shipped the core-editor welcome bot to send some fun links to new people when they join the channel

Open Floor

PR for move post/page title to the top bar needs discussion (PR 27093)

• @paaljoachim brought the issue up into the open again as it would be great to move the post/page title to the top bar so that we can get used to adding the post/page title block into the layout.

Thanks to everyone who attended!

#core-editor, #core-editor-summary, #meeting, #meeting-notes, #summary