This post summarizes the weekly editor chat meeting (agenda here) held on 2020-08-19 14:00 UTC in Slack. Moderated by @get_dave.
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/ 8.8.0 release
- At the time of the meeting it had not been released but Gutenberg 8.8.0 is now available.
- Release lead The community member ultimately responsible for the Release. @itsjonq joined us and provided his highlights:
- Full site editing has progressed with updates to Global Styles, the Post Block 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. suite, and Template management.
- Initial work has begun on the new Widget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Screen – a project that’s part of a wider effort to add more block enabled sections to the WordPress experience.
- This release also saw important accessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) and mobile improvements to user-interfaces like the Toolbar, navigation menus, and Popovers.
Monthly Plan & Key Projects
Navigation screen, Navigation block and Widgets screen
@andraganescu provided the update:
Andrei also point us towards the Navigation screen and Widgets project boards where help for code review, testing and picking up issues is always welcome.
Global Styles & Editor focused APIs
@nosolosw provided the update on his two focuses for the month:
- Land an initial user-facing tool to set styles globally.
For people interested in this area of work, the tracking issue lists specific tasks to help with.
For people getting started, a good first Issue is to migrate core blocks to use the implicit style attribute for colors and/or font-size.
Full Site Editing
@michael-arestad provided the update:
- An iteration on the multi-entity saving flow is in the works!
- Several of the post blocks now have icons and descriptions.
- A mockup for a document-level grid has been proposed.
- I’m starting in on everything related to the block directory.
@annezazu also reminded us about:
Customizer 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.
No one was available to provide an update. If anyone would like to provide this async, then please leave an update in the comments.
- @sageshilling referenced the media block proposal (is there a link for this?).
- Merged a PR to add an option for adding link in featured image on the Latest Posts block.
- Work to hide the Preview menu on small viewports and fix regression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. for FSE preview.
- Work to fix
Pullquote text color after unsetting main color.
- Has been focused on Widgets and the Widgets Editor.
- Also working on the Accordion block iterating on style variations and add a few more settings.
- Puting together a design/flow together around Multi-Entity Saving.
- Continuing to explore Global Styles.
- Has added a new label on the repository:
- A new form of triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. for our team to raise early awareness to change that need or not, attention in the block editor end-user documentation (= not developers)
- Don’t be alarmed when we tag 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.) PRs with this label.
- There is no “todo”-item for developers.
- @tomjn (first question):
- @tomjn (second question):
- A proposal regarding PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher and FSE templates.
- Proposal: when listing template posts, also list the top level PHP templates, and provide a link to create a replacement FSE template post to override it.
- It was suggested that an Issue should be raised for this with a clear proposal.
- @zeb – would like to draw our attention to x2 Issues.
- “Global Styles” might also mean “Default Styles”. I wonder if “Global” is a developer-friendly word that has less meaning to end users than “Default”.
Global, am I travelling somewhere?.
- Flagged x2 important foundational items to get right for FSE:
Thanks to everyone who attended.
#core-editor, #core-editor-summary, #meeting-notes