Tag Archives: gutenberg

Jorge Costa 7:04 pm on May 3, 2021
Tags: , , , , gutenberg,   

Editor chat summary: Wednesday, 28 April 2021

This post summarizes the weekly editor chat meeting on Wednesday, 28 April 2021, 14:00 UTC held in Slack.

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/ 10.5 RC release.

The first topic was the Gutenberg 10.5 release. The RC was already shipped a week before the chat https://github.com/WordPress/gutenberg/releases/tag/v10.5.0-rc.1. @jorgefilipecosta said that we had some PR’s that were cherry-picked since the RC.

The final release was scheduled for the day of the chat. @jorgefilipecosta gave public congratulations to @ajitbohra for the first RC release!

Posts requiring feedback and insights.

@jorgefilipecosta said that we have two important posts published recently that deserve wide attention:

In case anyone has some insights or thoughts to share please leave a comment on the posts! Your insights are appreciated!


Monthly Plan and key project updates.

Global Styles

Shipped this week

theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML.

block.json / 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. supports

  • duotone #26752
  • padding: fix to allow units other than px #31057
  • font-size: can be used in nodes other than the wrapper #30879
  • border-color: fix for dynamic blocks #31020
  • blocks
    • padding for site title #31125
    • padding and letter casing for site tagline #31042
    • link color for post date #30791
    • table uses now background/text colors from the theme #30791

Internationalization

  • custom templates can be translated via theme.json #29828

KSES

  • fix to sanitizing user styles #30888

Site editor:

  • fixes for preset classes in the site editor #31218 #31217 #31204
  • fix for color selector in the UIUI User interface color panel #31015

Ongoing

theme.json

  • Changes to format #29891 are ready #30541 we’re now testing and polishing. It also includes versioning (aka migrate the older formats to the new one).
  • Improve APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. to take data from the theme directly #31267

block.json / block supports

  • typography (line-height, font-weight, etc) can be used in nodes other than the wrapper #30880
  • border and color (background, text) to the pull quote block #30951

New style properties

  • Add support for letter-spacing #31118

Misc

  • Add a new endpoint that exposes block editor settings through the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. (by mobile to access global styles data) #29969
  • standardize capabilities of wp_template, wp_template_part and wp_global_styles #30893

Priorities

The priority continues to be shipping #29891 as soon as possible to unblock related work.

#28913 is a good issue to look at if you can lend a hand (help with reviews, migrate more blocks, more properties, etc).

Block based WidgetWidget 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. and Navigation Editor.

@andraganescu provided the following update:

The legacy widget got an UXUX User experience upgrade and now the default view is the preview while the embedded widget editor in the 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. had a performance overhaul. The focus on back combat continued with more testing with legacy widgets from various plugins. As expected a lot of new issues were opened.

On navigation editor the steady pace of improvements continued last week. Many thanks for the many welcome contributions!

Navigation block.

@joen provided the following update:

For the navigation block, we recently merged a padding change and I’m doing some followups (submenu gap, placeholder items, nav screen). Also looking at small separate improvements, and hope to get back to patterns now that the padding change is merged  — thank you for reviews.

Full Site Editing/Page templates

@youknowriad provided the following update regarding page templates:

I’ve spent some time iterating on that on the last days. We now merged the UIs for templates under a single “template” panel in the sidebarSidebar A 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., we iterated a bit on the design of the “frame” to distinguish properly between template and post modes and simplified the save flow a bit. There are a number of iterations we could make, I don’t expect all of them to happen before 5.8, at some point, we’d make a final decision about whether it’s good enough to include.

@ntsekouras made a heads up regarding the query block:

Query block has now a wrapper element which for now is div (and will be the default when more tags will be supported) here: https://github.com/WordPress/gutenberg/pull/30804I’ve added a deprecation so everything will work as before but it will be good to update any block themes you have that use Query.

Task Coordination

@aristath

This past week:

  • Continued working on PR to autogenerate anchors for headings – #30825
  • Continued on @nosolosw‘s existing PR to allow inner blocks in quotes – #25892
  • Sustainability: PR to split theme.css styles and only load the ones for rendered blocks – #31239
  • Smaller PRs, mostly to improve code quality & linting errors
  • Lots and lots of PR reviews

Next week: Continue working on all the things mentioned above

@mamaduka

Helping out with the new Navigation Editor screen:

  • Sync menu name updates.
  • Introduce useMenuEntityProp hook.
  • Better handling of unsaved changes. PRs one and two.

Continued my work on the “Most Used Terms” feature and got great feedback about improvements. Thanks, everyone.Planning to continue working on Navigation Editor tasks.

@paaljoachim

@ntsekouras

@annezazu

Continued FSE Program work with the fifth call for testing, publishing a schedule of upcoming plans, reviewing/adding to a brief FSE doc, and launched a second round of questions. I’m planning to likely do a hallway hangout tomorrow on FSE issues/prs/designs in #fse-outreach-experiment for anyone interested!

@poena

Plans to continue on the site block changes but also I want to test the theme.json format and update the tutorial for creating block themes. Awaiting review of the letter-spacing.

@vdwijngaert

Will be working on a PR for moving the post/page title to the top bar. Current PR: #31240, but going to close that in favor of a new one based on a branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch".

@jffng

@jorgefilipecosta

The main goal for next week is to review https://github.com/WordPress/gutenberg/pull/30541 and help it be merged. Plans on reviewing other Global Styles PR that are opened (e.g: https://github.com/WordPress/gutenberg/pull/30880). Wants to fix https://github.com/WordPress/gutenberg/issues/27478, which is probably very simple but may have a considerable impact and should be done ASAP.

Open floor

Post title moving in site editor

@bobbingwide said that there’s a problem moving the post title in the Site Editor. Adding that it’s tricky editing the topmost block if one does not have the toolbar set to top. @joen said @ellatrix is working on a fix https://github.com/WordPress/gutenberg/pull/31134.

G2 Components

@aristath asked the status of “G2 components” and if there is any plan on removing them. @youknowriad said that G2 is not removed but while reviewing some of the integration PRs, he noticed that G2 reimplements a lot of things we already have in Gutenberg in its own way. So the plan is still to integrate it but aligning with Gutenberg practices.

#block-editor, #chats, #core-editor, #core-editor-summary, #gutenberg, #meeting-notes

Ajit Bohra 12:22 am on April 30, 2021
Tags: , , gutenberg,   

What’s New In Gutenberg 10.5? (28 April)

Two weeks have passed since the last 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/ release, which means a new version is already available! Gutenberg 10.5 introduces many new 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. patterns, embedded PDFs, enhancements to the Template Editing Mode, improvements to Widgets in the 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., and many 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. fixes as well.

New block patterns and pattern transformations

Gutenberg 10.5 puts the focus on bringing several new block patterns, revisiting the bundled block patterns as well as adding more opinionated Query Block ones. It also enables block pattern transformations that are contextual to the currently selected simple block, without inner blocks.

Enhancements to the Template Editing Mode

With the goal of editing templates with blocks, a “Template Editing Mode” was introduced in recent Gutenberg versions so that users can edit a template directly from the post editor, switching between post and template editing. This release provides several flow and interface enhancements to this feature, including the possibility to create custom block templates in classic themes. Other improvements include unifying the saving flow between Template Mode and Default Mode, moving the Template Mode Edit and New links to a dedicated new panel, and replacing the Document tab with a Template tab in Template Mode.

Embedded PDFs with File Block

The File Block now supports embedding PDFs in most major browsers. This option can be enabled or disabled through a sidebarSidebar A 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. toggle.

Improvements to Widgets in the Customizer

While Gutenberg 10.4 enabled Block Widgets in the Customizer, this new iteration enhances the experience by enabling upload capabilities for media and Richtext formats.

No more auto-scrolling when selecting blocks

Before 10.5, when any block that was slightly out of view was selected, the page would automatically scroll so that the top of the selected block was visible, potentially disorienting the user. From 10.5 onwards, the scroll will only happen if the block is not selected directly by the user.

10.5

Enhancements

  • Buttons Block:
    • Add Typography support. (30394)
    • Explicitly add text-align-center to legacy buttons. (30525)
    • Update to use color support utils to retrieve classes and styles. (30870)
  • Columns Block: Add column count to the column block label. (30248)
  • File Block: Add support for embedding PDFs. (30857)
  • List Block: Add placeholder attribute. (30958)
  • Post Comments Link Block: New block added. (29564)
  • Site Logo Block:
    • Update the site logo description to be more illustrative. (30909)
    • Add a default width value. (30907)
  • Site Title Block:
    • Normalize the toolbar. (30999)
    • Normalize the toolbar (II). (31032)
  • Social Links Block:
    • Add text placeholder next to the appender. (29851)
    • Remove obsolete hardcoded focus style from Social Links. (30721)
  • Template Part Block: Add active block variation information in Block Parent Selector. (30731)
  • Term Description Block: Don’t output if there’s no description. (30564)
  • Verse Block: Add support for custom colors. (27736)
  • Video Block: Add uploading state. (30837)
  • Block Patterns:
    • Revisit the bundled block patterns. (29973)
    • Suggest block pattern transformations that are contextual to the currently selected ‘simple’ blocks (no InnerBlocks). (30469)
    • Small adjustments to bundled block patterns. (31105)
    • Query Patterns:
      • Try more opinionated query block patterns. (30763)
      • Add the small image and title pattern back in, fix excerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. length.. (30817)
  • Components: Add create-styles. (30509)
  • Design Tools:
    • Add border color, style, and width support. (30124)
    • BoxControl: Allow configurable sides. (30606)
    • Color Block Support: Add utilities to retrieve color classes and styles. (30869)
  • General Interface:
    • Animate the canvas transitions. (30802)
    • Include block title into block switcher label. (30808)
    • Inspector Controls: Rephrase, polish, and make consistent color labels. (30075)
    • Update design of the resize handles. (30339)
    • Icons: Update icons for text overlay and crop. (30673)
  • i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.: Add resetLocaleData method. (30419)
  • Publishing Flow: Show post events in the post schedule calendar. (29716)
  • Template Editing Mode:
    • Allow creating custom block templates in classic themes. (30438)
    • Move the template mode edit and new links to a dedicated template panel. (30900)
    • Replace the document tab with a template tab in template mode. (30860)
    • Unify saving flow between template mode and default mode. (30793)
    • Update the template mode canvas padding and adds a backlinkBacklink Incoming links to a web page. Search engines view backlinks as a reputation builder. The more quality (as determined by the search engine) incoming backlinks a site has usually helps a site to rank better in search engine results.. (30658)
  • Site Editor:
    • Add ‘area’ selection to convert to template part flow. (30395)
    • Add do_block_template_part function. (30345)
    • Add skip link to block templates. (30336)
    • Remove single-post from the default templates set. (29668)
    • Themes: Fix template-hierarchy fallbacks. (30599)
  • Writing Flow: Scroll selected block only if it has no focus. (30924)

Bug Fixes

  • Apply a StyleProvider around fills that can be used inside the iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser.. (31073)
  • APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. Fetch: Make preloaded OPTIONS requests use parse setting. (28862)
  • Block Library:
    • Duplicate media types to avoid bad imports. (30973)
    • Image Block: Disable media buttons in the uploading state. (30863)
    • Query: Fix max-height to query pattern preview. (30757)
    • Post Title: Fix warnings for RichText in inline containers. (30666)
    • Site Title: Add default block after pressing enter at the end of Site Title. (30996)
  • Block Editor:
    • Bring back imageDefaultSize shim for WP 5.7. (30955)
    • Fix the position of vertical add a new block in RTL mode. (31035)
    • Template part: Fix PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher notice for placeholder block. (30928)
  • Components:
    • Add a StyleProvider to support CSSCSS Cascading Style Sheets.-in-JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. components inside iframes. (31010)
    • Fix “RadioControl: checked” style outside of Gutenberg. (30670)
    • Fix Post Date component. (30790)
    • Fix Post Publishing Popover moving when certain dates are clicked. (30298)
    • Fix useForceUpdate Memory Leak: Only setState if the component is still mounted. (30667)
  • General Interface: Fix is-link style to take colors from wp-adminadmin (and super admin) theme. (30823)
  • Inserter: Stop event propagation for the select element’s onBlur to fix the behavior in iOSiOS The operating system used on iPhones and iPads. when selecting a pattern categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging.. (30717)
  • Site Editor:
    • Focus save button when entities save states panel is opened. (30873)
    • Remove call to wpautop that unintentionally alters block markup in template parts. (30552)
  • Template Editing Mode: Hide the template selector and template mode from non-viewable post types. (30861)

Experiments

  • Block-based Widgets:
    • API:
      • Don’t use deprecated widget_class property. (30429)
      • Fix null instance property when instance settings are empty. (30713)
      • Remove deprecated properties. (30853)
    • Customizer Integration:
      • Add media uploader capabilities to block-based widgetWidget 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. customize screen. (30954)
      • Add move to widget area dropdown in customizer. (30896)
      • Add rich text formats. (30952)
      • Fix editing performance in Widgets Customizer. (30654)
      • Fix block-based widget customizer initializing too soon. (30864)
      • Refactor the inspector in Widgets Customizer to use coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. controls. (30431)
    • Legacy Widget: Improve backward compatibility. (30709)
    • Widget editor:
      • Add a toolbar button to move between widget areas. (30826)
      • Fix the undo/redo buttons in the standalone block-based widgets editor. (30989)
  • Navigation Editor and Block:
    • Fix navigation placeholder height issue. (30824)
    • Fix alignment issue on the nav screen manage locations buttons. (30441)
    • Limit navigation nesting depth to 5. (30199)
    • Nav-created drafts should not render on the frontend. (29692)
    • Page List: Add ability to convert to navigation links. (30390)
    • Show justification controls for vertical variant. (30351)
    • Use theme locations description instead of the slug for navigation screen location labels. (30797)
  • Global Styles:
    • Absorb editor settings transformation in WP_Theme_JSON. (30610)
    • Clean cached data when switching themes. (30830)
    • Extract sanitize method. (30809)
    • Fix: CSS variable reference mechanism regressionregression 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.. (31015)
    • Make the dependency of the star matcher explicit when translating theme.json. (30604)
    • Only remove the default font family in the editor from themes with theme.json file. (30895)
    • Refactor how we iterate over the tree. (30801)
    • Remove no longer needed translations handled in PHP for settings. (30605)
    • theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML.: Add util to transform from a v0 schema to the latest. (30600)

Documentation

  • docgen:
    • Add support for TS exported static non-function variables. (30971)
    • Add support for assignment patterns. (30681)
    • Add support for object-destructuring. (30675)
    • Find parameters by index rather than name and handle array destructuring. (29945)
  • Handbook:
    • Add documentation for border block supports. (31039)
    • Add documentation for border styles. (31040)
    • Add fix to suggested prefixes of the branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch".. (30953)
    • Change references from Block Style Variations to Block Styles. (30911)
    • Fix Block Editor AccessibilityAccessibility 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) link. (30569)
    • Fix more examples for register_block_type – apiVersion to api_version. (30819)
    • Fix PHP example for register_block_type – apiVersion to api_version. (30818)
    • Fixed a type and made the whole explanation more clear. (30487)
    • Fixes broken GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ links to commonly used labels. (30875)
    • Improve semantics in the block-based theme guide. (30946)
    • Include a note about is_default property for register_block_style. (30792)
    • Organize Block API Reference. (30980)
    • Packages: Further clarify the npm publishing process. (30733)
    • Update getting started with code. (30447)
  • Libs:
    • Blocks: Fix PHPDocs of gutenberg_block_has_support. (31050)
    • Query Utils: Fix return type of construct_wp_query_args(). (30611)
  • License: Interim dual license of future contributions. (30383)
  • Packages:
    • Block Library – Social Links: Update param type. (30652)
    • Components: Add documentation for the text prop on the Button component. (30796)
    • Core Data: Fixes return type for getEntitiesByKind. (30639)
    • Block Editor: Update import statement of ImageSizeControl component. (30704)
    • HooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same.: Add namespace param clarification. (30501)

Code Quality

  • Block Editor:
    • Simplify focus capture. (31036)
    • Standardize loading default block editor settings. (30245)
  • Block Library:
    • Button Block: Use hook-based border support. (30194)
    • Cover: Rename isBlogUrl to isUploadingMedia. (30435)
    • Cover: Use ALLOWED_MEDIA_TYPES shared constant. (30977)
  • Block Patterns: Clean up bundled pattern titles & categories. (30998)
  • Components: Remove create-styles in favor of vanilla emotion. (31048)
  • dom:
    • Add types to caret placement functions. (30750)
    • Add types to document-has-selection. (30386)
    • Add types to is-edge and dependencies. (30546)
    • Add types to miscellaneous files. (30774)
    • Add types to removeInvalidHTML and stripHTML. (30752)
    • Only assert defined in development. (30807)
    • Type the remaining files. (30841)
  • Drop zone: Rewrite without provider. (30310)
  • Gutenberg PluginPlugin 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:
    • Account for editor styles file removal on WP trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.. (30894)
    • Format all markdown files using Prettier formatter. (30715)
    • Format all JSON files using Prettier formatter. (30714)
    • Updated .editorconfig files to work with automatic file formatting. (30794)
    • Update WP compatibility check in gutenberg_pre_init(). (29938)
  • Improve get_merged_data() code. (30612)
  • Remove unnecessary semicolons in PHP. (30780)
  • Replace older-style PHP type conversion functions with typecasts. (30531)

Tools

  • Testing:
    • Cover Block:
      • Add edit media integration tests. (30270)
      • Replace media end-to-end test. (30306)
    • Fix end-to-end test failure screenshots not capturing at the right time. (28449)
    • Fixture regeneration: Infer tabs use from the prettier configuration. (30813)
    • Skip unstable template part end-to-end test. (30748)
    • Trim block fixture HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. when generating other test fixture files. (30981)
    • Wire PHP tests for block editor settings. (30984)
  • wp-env:
  • Build Tooling:
    • Add comments to the webpack entry point function. (30629)
    • Create frontend entry points for block-library, outputting code loadable from the browser. (30341)
    • Perf Workflow: Trigger upon release publishing. (30628)
    • Pull trunk before pushing. (30615)
    • Remind about required cherry-picks after npm publishing. (30868)
    • Update development tools to work with PostCSS (try 2). (30347)
    • Use consistently the latest keyword for npm publishing. (30866)
  • Scripts:
    • Allow CSS modules in the build commands. (29182)
    • Include YAML files in prettification. (30240)

Performance Benchmark

The following benchmark compares performance for a particularly sizeable post (~36,000 words, ~1,000 blocks) over the last releases. Such a large post isn’t representative of the average editing experience but is adequate for spotting variations in performance.

VersionLoading TimeKeyPress Event (typing)
Gutenberg 10.57.86s55.86ms
Gutenberg 10.47.25s42.51ms
WordPress 5.76.86s37.1ms

Kudos to all the contributors that helped with the release! 👏

Thanks @youknowriad and @priethor for helping with the release and the release post, respectively.

#core-editor, #editor, #gutenberg, #gutenberg-new

Ajit Bohra 1:55 pm on April 26, 2021
Tags: , , , gutenberg,   

Editor chat summary: Wednesday, 21 April 2021

This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held in the #core-editor SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, on Wednesday, April 21, 2021, 14:00 UTC.

Thank you to all of the contributors who tested the BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. releases and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.

Full Site Go/No Go

The Full Site Editing Go/No Go demo took place a few days ago, where project leadership determined what new features should be included in WordPress 5.8 based on their current status, feedback gathered in calls for testing, and the prospect of achieving a solid implementation before the feature freeze.

As a next step high-level overview of the focuses to attend to before the feature freeze is defined. WordPress 5.8 FSE must-haves project board is available to trace individual items.

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/ 10.4

Gutenberg 10.4 was released on 14th April introducing cool features like 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. widgets in the 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., enhancements to the Site Editor, improvements to rich text placeholders, and, as always, many 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. fixes as well.

Gutenberg 10.5 RC

Gutenberg 10.5 RC 1 was released last week test and report bugs.

FSE Outreach

Two weeks remaining to go on a Query (block) Quest with the fse outreach expirement.

Monthly Plan

The monthly update containing the high-level items that Gutenberg contributors are focusing on for January are:

  • Global Styles.
  • Block-based WidgetWidget 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. Editor.
  • Navigation block.
  • Full Site Editing.

For detailed plan check out monthly priorities post.

Updates on the key projects

@andraganescu

A brief update on Widgets and Navigation:

  • Focus on figuring out the best approach for backward compatibility and see how much can the block based editor offer.
  • Navigation editor progressed with bug fixes, but still hanging around the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. issues of how to best reuse the navigation block.

@nosolosw

This week in global styles:

  • Landed theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. with elements #29891.
  • extract sanitization method #30809.
  • Added block support & theme.json support for: border-color, border-style, and border-width #30124.
  • Clean cached data when switching themes #30830.
  • Standarize block editor settings load #30245.
  • Fix regressionregression 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. in color panel of global styles sidebarSidebar A 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. #31015.
  • Add utility to retrieve classes and styles in color hook #30869 #30870.
  • Polish color labels #30075.
  • changes to shape (working in all editors & front-end) #30541.
  • Allow skipping serialization for typography attributes #30880.
  • Conversation about “overlay” colors #29963 (comment).
  • Migrate more blocks using the skipSerialization mechanism as well as adding more properties #2891.
  • kses filtering (approved) #30888.


The priority continues to be shipping #29891 as soon as possible to unblock related work.
#28913 is a good issue to look at if you can lend a hand (help with reviews, migrate more blocks, more properties, etc).

@mkaz

Navigation block improvements follow all the details in the tracking issue here.

  • Responsive menu is close and got delayed due to external priorities, but I’d expect in 10.6.
  • Home Link has started new since last time.

Task Coordination

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

@mamaduka

@joen

Focusing on the navigation block, looking into patterns.

@paaljoachim

  • Working on a few issues for Learn.
  • VVV/Vagrant setup a local dev environment tutorial.
  • Exploring improvements to the Page templates UIUI User interface.

@hypest

Quick update from the native mobile folks: 

  • Block transforms, Interim dual-license for new contributions merged, media insertion flow simplification.
  • Gallery Block Refactor Resumed, Editor Onboarding implementation started.
  • Fixes in Stepper a11yAccessibility 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), Unsupported Block Editor start, Quote block citation newlines.
  • Refined media progress error notice.
  • In Progress: GSS, Reusable blocks, Search block, Block Picker Search, Embed block, Slash inserter.

@nerrad

Published a PR with a proposal introducing a document defining some Gutenberg Principles for the project to adopt. Would be good to get more eyes on it (especially from the coreteam).

@ntsekouras

@mkaz

@get_dave

  • Work on the Navigation editor/screen.
  • Focused on ensuring wp nav menu items are mapped to the correct block types/variations #31004.
  • Exploring a clearer “close” UX for the Site Editor navigation sidebar that appears when you click the `W` icon.

@annezazu

  • Focused on the FSE Outreach Program (responding to feedback, amplifying, testing, writing up the latest summary).
  • Alongside a work in progress core editor improvement post and a post on the role of the Gutenberg pluginPlugin 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/when to .use Gutenberg for /news to help guide people.

@aristath

Open Floor

@get_dave

  • Block Transforms: deprecating `transform` APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. in favour of `convert` for block transforms.
  • When the group block was introduced we had to create a new experimental API `convert` to allow us to group a block/selection of blocks via the “Block Transform” UI in the block toolbar.
  • This was because the existing `transform` API only provided access to a limited set of data about the block(s) being transformed, whereas we needed the blocks themselves.
  • In many cases it is more useful to simply receive the block(s) being transformed – this provides access to all data about the block (including `attributes` and `innerBlocks`). This is (for the most part) a “blocks in, blocks out” mindset which feels quite natural.
  • @aduth proposed we promote the `convert()` API and deprecate `transform`. `transform` would remain in place for backwards compatibility so there would be no breakage. The API has been in use for over a year but is not standardised or documented. Also, it cannot easily be removed as the Group block is dependent on it.
  • The PR has fallen dormant and needs a decision to take it forward. I’m happy to help do the work to get it over the line if we can wrangle a decision.

@paaljoachim

  • I am working on the flow of the Page template and I am seeing a few things here and there that needs adjusting. One issue I have met a few times is the lack of ability to discard a save. I made this issue showing how one gets stuck. 
  • There are explorations going on in relation to discarding saves but it is more complex.

@mamaduka

  • I would love to get UXUX User experience feedback on this issue and if it’s okay to hide block controls while an image is uploading.

@aristath

  • Right now I can’t use any non-px values. We can’t say that font-size should be 2em and I suspect that’s from g2. Things that were supposed to work don’t (paddings). If anyone is able to use non-px values for paddings in latest trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision., please let me know how… Right now I can’t see how it could possibly work, it looks like units is always an empty array and I can’t figure out how/why it was working in the old days

@annezazu

Read complete transcript

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

annezazu 8:41 pm on April 23, 2021
Tags: , , gutenberg   

Core Editor Improvement: Refining the Block Toolbar

With a growing amount of customization features being unlocked, the toolbar for each coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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. is being transformed one at a time to make it more intuitive and predictable to use. Since the block toolbar contains the most important block tools, this could help improve your workflow as you’re creating content.

In the same way you might organize tools in a toolbox so you can quickly grab and go, the toolbar is on that same path: grouping related tools based on which level of a block an option impacts. To get a sense of what this actually means, and how it’ll improve your workflows here’s a before and after photo showing the changes in the Image Block:

Before:

Image showing the block toolbar on an Image Block with the tooling before the update occurred.

After:

Image showing the block toolbar on an Image Block with the tooling after the update occurred.

Keep in mind that not all blocks have been revamped just yet, but you can follow this issue to keep track. For now, if you’re using the 10.4.1 release of the 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/ pluginPlugin 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, you can expect to see this update in the following blocks, with more on the way: 

  • Image 
  • Cover
  • Button
  • Buttons
  • List
  • Heading
  • Paragraph
  • Quote
  • Audio
  • File
  • List
  • Video
  • Media & Text
  • Site Logo
  • Post Featured ImageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts.

The goal of the effort is to simplify the hierarchy of the block, to make it more predictable what goes where. Here’s a visual outlining the groupings:

The visual is taken from recently updated documentation: 

  • Block surfaces properties of the block itsef..
  • Tools surfaces tools that affect the whole content of the block, such as alignments or positition.
  • Inline formatting refers mostly to in-text transformations such as bold or italic on a text selection. 
  • Other contains any additional features that do not fit in the other groups.

As each core block gets updated, there will hopefully be a cascading effect, making it predictable to adjust any block how you need to, whether that’s changing block alignment or bolding a specific piece of text.  

Thank you to @joen for helping edit this post (including providing the visuals) and for the excellent guidance throughout.

#core-editor, #core-editor-improvement, #gutenberg

Héctor Prieto 9:10 pm on April 20, 2021
Tags: , , gutenberg   

Full Site Editing Go/No Go: Next steps

The Full Site Editing Go/No Go demo took place a few days ago, where project leadership determined what new features should be included in WordPress 5.8 based on their current status, feedback gathered in calls for testing, and the prospect of achieving a solid implementation before the feature freeze.

This post aims to provide a high-level overview of the focuses to attend to before the feature freeze; linked individual actionable GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ items further develop lower-level requirements to complete. Individual items are also being tracked in the WordPress 5.8 FSE Must Haves project board.

Schedule

According to the WordPress 5.8 pre-planning schedule, the feature freeze will take place on May 25th, leaving room for the following 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/ pluginPlugin 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 releases to be merged:

Gutenberg versionRC release dateStable release date
10.5April 21stApril 28th
10.6May 5thMay 12th
10.7May 19thMay 26th

To align with this schedule, the last version to be merged in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. before the feature freeze will be 10.7-RC, with any future bugfix applied before or after the stable 10.7.0 being ported as well. Moreover, to ease new feature testing with more frequent merges, as suggested in a recent dev chat, Gutenberg 10.4 -without experimental features- is already available in WordPress core.

Next steps

Apart from all the incremental improvements included by merging up to 9 plugin releases, from Gutenberg 9.9 to 10.7, the following work-in-progress features are targeted for 5.8 and should become stable by Gutenberg 10.7. 

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. theme building

Block themes might arguably represent one of the biggest core theme-building paradigm changes in the last decade. As such, a huge effort is being done to achieve a future-proof, evolvable foundation. With most of the infrastructure ready, the focus remains on the theme.json configuration file, and the “block supports” mechanism:

A list of detailed requirements to meet before the feature freeze can be found at the Block Styles Breakdown overview issue.

Once released in 5.8, theme developers will be able to create block themes and provide quality feedback to iterate over these mechanisms.

Introducing Theme blocks

As part of the implementation of Full Site Editing, a number of theme blocks have been developed to cover theme/site features similar to how classic template tags worked. The next steps are to finish determining which of these blocks should be included in 5.8 and enabled for classic themes, and polish them, including:

These blocks should display a badge in the inserter, denoting they are new blocks that, while completely stable and functional, might still need some UXUX User experience polishing and are meant to experiment and tinker around.

Template editing within the post editor

With one of the targets for 5.8 being to introduce block templates, users will be able to create custom block templates for posts and pages in classic themes. Although this feature mostly relies on the existing site editing infrastructure already available in the plugin, these improvements will be focused on to provide a great user experience. User testing is planned in coordination with @annezazu from the FSE Outreach program during the WordPress 5.8 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. phase. Users are encouraged to join this program as it provides invaluable feedback that helps drive the projects’ focus and determine feature usability.

Widgets Editor & Block Widgets in the 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.

The Widgets Editor project aims to bring the power of blocks to classic theme with two major milestones:

  • Adding support for blocks in widgetWidget 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. areas
  • Embedding a block editor in the customizer

Once these milestones have been completed, the remaining efforts towards 5.8 focus on providing stellar stability and backward compatibility, with an upcoming call for testing to be launched in the near future; if this is of interest to you, please keep an eye out for a future post on this blogblog (versus network, site). A detailed list of the next actions can be found at the Widgets Editor tracking issue.

Persistent List view in the post editor

The Persistent List View provides an improved overview of the inserted blocks and has greatly enriched the way users navigate the block tree in the Site Editor. Therefore, the goal is to bring the Persistent List View to the post editor as well in 5.8.

Duotone block supports

WordPress 5.8 aims to introduce the new duotone design tool as a “block supports” feature, available by default in the core image and cover blocks. The PR introducing this feature is currently in its last polishing iterations and should be expected to land in the plugin soon.

Gallery block refactor

Last, but not least, work and a round of testing continue on the Gallery block refactor which seeks to be a wrapper around Image block rather than a separate block entirely. This will allow the Gallery block to benefit by default from all design tools and improvements made to the Image block. Feedback collected is addressed as part of the PR efforts; users are welcome to test and submit their feedback as early as possible so that it can be acted upon in the upcoming weeks.

#5-8, #core-editor, #gutenberg

Héctor Prieto 9:46 pm on April 14, 2021
Tags: , , gutenberg,   

What’s new in Gutenberg 10.4? (14 April)

Two weeks have passed since the last 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/ release, which means a new version is already available! Gutenberg 10.4 introduces cool features like 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. widgets in the 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., enhancements to the Site Editor, improvements to rich text placeholders, and, as always, many 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. fixes as well.

Block widgets in the Customizer

As part of the Block-based WidgetWidget 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. Editor project, one goal is to enable block widgets in the Customizer, with Gutenberg 10.4 introducing the first iteration of this feature.

List View design updates

This release brings us a set of design updates to the Site Editor List View, including updates to icon sizes and spaces and new colors for hover, focus, and select states.

More descriptive publishing UIUI User interface

The publishing content UI found in block editors now includes the site icon and name so that it’s clearer in certain cases, such as full-screen or mobile, where you are publishing to.

Revert template to theme defaults within the Site Editor

Until now, to revert a template to the default provided by a theme, it had to be done outside the Site Editor. Thanks to this new feature, it is now possible to revert template customizations directly in the editor.

Rich text placeholder enhancements

To improve the editing experience, rich text block placeholders have seen a few tweaks in this release. Starting in Gutenberg 10.4, blocks containing rich text will display a shorter placeholder text that will remain shown even when being focused.

Improvements to Navigation Block

The Navigation Block has good momentum and has received many improvements in this release, including a new “Post Format Link” variation, a clearer placeholder state, and more style polishing. 

Editor and frontend parity refinement

Providing a consistent markup between the editor and the frontend is key to deliver a smooth editing experience. Gutenberg 10.4 iterates towards this goal by ensuring a frontend-editor parity in blocks such as Quote, Separator, and Archives, among others.

10.4

Enhancements

  • Ensure Frontend/Editor block styles parity:
  • Block Library:
    • Latest Comments: Remove list padding and margin. (29402)
    • Post Date: Add option to make it a link. (30499)
    • Post ExcerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox.: Fix toolbar for post excerpt warning. (30280)
    • Post Title: Fix “‘length’ of undefined” error. (30208)
    • Preformatted: Add color controls. (28396)
    • Query: Use a WordPress loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. for the query block. (30405)
    • Search: Add border radius support. (30227)
    • Site Logo: Style polishing. (30526)
    • Template Part: Add padding support to template parts. (29779)
    • Update placeholder text across blocks. (30404)
  • RichText:
    • Add min width to show caret for empty inline container. (30224)
    • Always show placholder on focus. (30393)
  • General Interaface:
    • Add site icon and name to the publish flow. (30231)
    • Use a darker canvas color. (30282)
    • Update the save button label in the site editor. (30439)
  • Icons:
    • Polish media & text icons. (30239)
    • Update “close small” icon so that its shape matches the “add” icon dimensionally. (30014)
    • Update site-logo block icon. (30211)
  • Inserter: Clarify that when the Inserter is open clicking the + button in the top bar will close it again. (29759)
  • Writing Flow: Use a shorter writing prompt. (29611)
  • List View: Improve the spacing, colors and icons (30455) (30303)
  • Block Themes: Clarify the empty block templates message. (30145)
  • Site Editor:
    • Allow reverting custom templates to their original theme-provided files. (28141)
    • Use “Custom Styles” label to signal there are global styles changes in the saving panel. (30521)

Bug Fixes

  • Inserter: Show only the patterns that use allowed blocks. (30300)
  • Block Library:
    • Buttons: Prevent overlapping button blocks in the frontend. (30253)
    • Columns: Prevent having a width > 100%. (30229)
    • Cover: Add ‘object-position’ to allowed inline style attributes list. (30243)
    • Gallery: Avoid adding all media items in galleries using external URLs. (30122)
    • Image: Do not preserve custom sizes when replacing images. (29919)
    • Query:
      • Fix undo trap during creation. (30203)
      • Pagination Numbers: Print nothing if content is empty. (30554)
    • RichText: Fix arrow navigation around emoji. (30206)
    • Search block: Fix alignment issues. (30444)
    • Site Logo: Delete sitelogo option when custom logo does not exist or was removed. (30427)
  • Block List: Fix mover position in the docked toolbar. (30242)
  • Code Editor: Revert save editors value on change (#27717). (30524)
  • Post Editor:
    • Avoid focus attempt on a non-existent post title in code editor. (29922)
    • Fix the post author selector for contributor roles. (30218)
  • Gutenberg PluginPlugin 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: Ensure that plugin does not error with older versions of WordPress. (30230)
  • Inner blocks: Memoize allowedBlocks to prevent needlessly updating settings. (30311)
  • Server side renderer: Fix errors in template part editor context. (29246)
  • Writing Flow:
    • Fix copy pasting non textual blocks. (30225)
    • Fix horizontal caret placing for empty editable with placeholder. (30463)
    • Fix multi-selection copying in Safari. (30202)
  • Site Editor:
    • Fix nested template parts. (30416)
    • Fix media upload behaviour and error state. (30436)
    • Select the block inspector top upon selection. (30387)
  • Components: Stop matching autocompleter upon mismatch. (30649)

APIs:

  • Add padding server-side block support. (30332)
  • Remove small APIs deprecated in WordPress 5.2. (30283)
  • Block Patterns: Remove scope from Query patterns and introduce blockTypes. (30471)

Experiments

  • Customizer
    • Add customize widgets inserter. (29549)
    • Add Legacy Widget block. (30321)
    • Fix adding blocks in the widgets customizer. (30221)
  • Navigation Editor and Block
    • Apply mover tweaks to navigation and widgets. (30284)
    • Add src/navigation-link/index to side effect whitelist. (30200)
    • Add post format variation to navigation link block. (30403)
    • Avoid creating a new array/object on every render. (30374)
    • De-emphasize “Link” block. (30172)
    • Fix arrow inheritance, polish. (30287)
    • Fix hardcoded color in navigation submenu icon. (30385)
    • Fix Navigation Link block constantly updating its inner block list settings. (30274)
    • Fix navigation link block dragging error. (30219)
    • Fix snackbar list component blocking clicks to UI it overlaps. (30381)
    • Flip orientation of submenus that are towards the right of the viewport. (30342)
    • Indicate when a menu is deleted and show the menu switcher afterwards. (29201)
    • Make the navigation placeholder clearer. (30281)
    • Polish navigation menuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site. submenus. (30335)
    • Replace arrow with chevron. (30180)
    • Save theme location on button click. (30340)
    • Use same default implementation of __experimentalFetchLinkSuggestions in post, site, navigation, widget editor. (29993)
  • Widgets Editor
    • Add manage with live preview link. (29839)
    • Handle when $instance is empty and use str_replace instead of sprintf in the Widget block. (30217)
    • Iterate on Legacy Widget block. (29960)

Documentation

  • Handbook:
    • Add description for templateParts in theme jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML.. (30118)
    • Add instructions for finding attributes for use in templates. (30258)
    • Added a practical example of adding a component to the sidebarSidebar A 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.. (30379)
    • Clarify what is meant by “block wrapper”. (30315)
    • Fix broken links to typescript documentation. (30188)
    • Fix code snippet for disabling the block directory. (30365)
    • Fix formatting. (30309)
    • Fix typos in block-controls-toolbar-and-sidebar.md. (30513)
    • Rename, changed URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org Link. (30483)
    • Rich Text: Add section for disabling specific format types. (29383)
    • Updated documentation to reflect the output created currently by npx wordpress/create-block gutenpride. (30353)
    • Update feature deprecation guide. (30220)
  • Packages:
    • Api-fetch: Fix example code for apiFetch middlewares. (30534)
    • Block supports: Fix typos in layout supports comment. (30537)
    • Block Editor: Fix block-editor typo. (30401)
    • Components:
      • Remove references to __experimental* in the DateTimePicker component documentation. (29322)
      • Update CustomSelectControl component README.md. (29854)
  • docgen:
    • Components: Add types to Draggable. (29792)
    • Add types to clean-node-list. (30412)
    • Add types progressively to dom modules. (30103)
    • Add types to phrasing-content. (30102)
    • Export all types from api-fetch. (30539)
    • Fix arrow functions and TS index module support. (30028)
    • deprecated: Export DeprecatedOptions to align with DefinitelyTyped. (30677)
    • api-fetch: Align exported type names with DefinitelyTyped types. (30570)

Code Quality

  • Block Editor: Use proper insertion point for drop. (29933)
  • Block Library: Fix Post Excerpt warnings for RichText in inline containers. (30498)
  • Components: Simplify ScrollLock, adding types. (29634)
  • Gutenberg Plugin:
    • Prettify YAML scripts. (30409)
    • Remove deprecations planned for 10.3 release. (30417)
    • Update the objectFitPolyfill vendor library. (30507)
  • PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher Coding Standards fixes. (30346)

Tools

  • Add /packages/stylelint-config to CODEOWNERS. (30264)
  • Build: Ensure non-JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. changes are processed in the watch mode. (30343)
  • Testing:
    • Added end-to-end tests for navigation menu name editor. (29774)
    • GHA workflow improvements when setting up NodeJS. (29078)
    • Include NodeJS version in the cache key. (30512)
    • Remove button from forbidden elements. (30223)
    • Remove cache restore-keys. (30510)
    • Skip flaky end-to-end tests. (30344)

Performance Benchmark

The following benchmark compares performance for a particularly sizeable post (~36,000 words, ~1,000 blocks) over the last releases. Such a large post isn’t representative of the average editing experience but is adequate for spotting variations in performance.

VersionLoading TimeKeyPress Event (typing)
Gutenberg 10.45.94s35.14ms
Gutenberg 10.35.98s32.58ms
WordPress 5.75.05s31.34ms

Kudos to all the contributors that helped with the release! 👏

Thanks @youknowriad for managing the release and @critterverse for helping with the release post assets.

#core-editor, #editor, #gutenberg, #gutenberg-new

Andrei Draganescu 6:09 pm on April 14, 2021
Tags: , , gutenberg   

Editor chat summary: 14 April, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on 2021-04-14 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/ 10.4 release.

  • @youknowriad shared that the release post will be coming shortly (later today or tomorrow). It’s a release with a lot of work related to FSE, FSE Blocks, editor/frontend parity and many other updates.

Full Site Editing Scope for WP5.8

The post was shared during the chat and attention directed towards the outline of the 5.8 plans for FSE, and @annezazu shared that there is a new call for testing available. Also we now have a board with WordPress 5.8 FSE Must Haves.

Monthly Priorities & Key Project Updates

Global Styles

@nosolosw shared in his GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ tracking issue:

Landed:

  • Parts of theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. with elements PR:29891
  • preparations to make changes easier PR:30801 PR:30610
  • i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill. process: make it not depend on a particular path PR:30604
  • add mechanism to migrate from a v0 schema to the latest PR:30600
  • clean-ups PR:30605 PR:30612
  • border radius for the button 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. PR:30194
  • font size & font family for the button block PR:30394
  • colors for the verse block PR:27736
  • border radius for the search block PR:30227

Ongoing

Mobile team updates

@chipsnyder shared the following updates:

Landed

  • Generic embed block behind the DEV flag, actual functionality in progress
  • Interim dual-license license in place (PR:30383)
  • Error notice improvements (PR:30383)
  • Various fixes 

In Progress:

  • Dual licensing Gutenberg: planning to merge PR with interim license this week
  • Global Style Support (PR:29969)
  • Reusable blocks
  • Search block
  • Adding search to the block inserter
  • Embed block
  • Simplification of media insertion flow
  • Slash inserter (PR:29772)

Block based widgets and navigation editors

@andraganescu shared some updates:

For the Block based WidgetWidget 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. Editor the main focus these days is improving the performance of the block editor in the 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. and moving our attention to testing the level of back compat existing and achievable.

Navigation block

@andraganescu, @joen and @mkaz shared updates:

  • Progress continues, responsive menus expected this week
  • One notable merge since last is converting Page List block to menu items
  • Justification controls added to vertical
  • Working through extensibility for allowing additional block types in Social and Navigation blocks
  • preparing for patterns. Notably, looking at submenu colors, small glitches, removing menu item padding when there’s no background. The last one should open up a great deal of nice minimalist patterns.
  • ongoing discussion about  the block’s markup and the work on adding a Links List block

Update on the post schedule component

@retrofox shared an update about a couple of enhancements in the post-schedule component. Now, it shows calendar events with a small blue bullet. Events are scheduled and published posts.

Task Coordination

@ntsekouras

  • Landed patterns suggestion for transforming simple selected blocks (no InnerBlocks) (PR:30469)
  • Add active block variation information in Block Parent Selector (PR:30731)

@youknowriad

I’m iterating on the “template mode” of the post editor. (Creating and editing block templates in the post editor)

@joen

In addition to the navigation block, I had these two, one is a work in progress, the other could use your eyes:

@mamaduka

I mainly worked on enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. issues:

@annezazu

Working on all things FSE Outreach Program — responding to feedback for the fourth call for testing/opening lots of issues, held a hallway hangout about FSE, still testing FSE everyday, and am going to ship a fifth call for testing today with a summary post of the fourth call for testing to follow later this week.

Open Floor

Contributor dayContributor Day Contributor 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/. at Yoast

@poena announced that last week there was a contributor day at Yoast with user testing and code contributions to FSE. A large amount of feedback issues were open and some that are already being solved.

Issues and PRs needing eyes and contributions

  • Discussion: documentation handbook plans for site editing and beyond: Issue:30637
  • FSE: Finalizing the name and menu item placement Issue: 29630
  • Post and site editor title placement: Issue:27093
  • Shared block editor settings PR, which requires some updates to the existing PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. and could use some eyes for sanity checks and reviews PR: 1118

Status of the existing Block Template APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.

@itsjusteileen asked about the future of the Block Template API in the context of FSE developments and noted that the code examples in the handbook don’t work anymore. It doesn’t appear that the block template API will go away and we should have some issues open if the documentation is outdated or the API broken.

Feedback needed on several widgets/blocks discussions

  • a discussion about allowing users to insert a Classic Block in a SidebarSidebar A 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. on the Widgets (betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.) screen
  • a discussion about reconstructing Widgets Screen to use the Customize API. This is a fancy way to say that we should or could remove the standalone editor as the new block based widgets editor lands in a future WP release.
  • a question: assuming the block based widgets editor is an opt out feature what is the preferred way to opt out

Design process for the widgets updates

@Anthony Nolan brought up a question around where can one find the process that led up to the current state in the block based widgets editor project, and was guided towards going through closed issues such as this one or this one, which cover updating the customizer or look at the open project to see how the stand alone widgets editor progresses.

#core-editor, #core-editor-summary, #gutenberg

Héctor Prieto 7:52 pm on April 8, 2021
Tags: , gutenberg,   

What’s next in Gutenberg? (April 2021)

This monthly update contains the high-level items that 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/ contributors are focusing on for April. Please join us in our efforts and let us know in the comments if anything is blocking you from doing so.

How to follow along with Gutenberg:

Here’s an overview of different ways to keep up with Gutenberg and the Full Site Editing project. There is also an index page of Gutenberg development-related posts and a Site Editing Milestone overview issue that breaks down the upcoming work into more concrete next steps. 

Widgets Editor

Work on the 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.-based WidgetWidget 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. Editor is a continued focus for the month ahead. This effort aims to bring the flexibility of block editing to the widgets 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. screens. The current efforts include:

Follow along:

You can find more information about the current work in progress in this tracking issue, as well as on this project board. Moreover, you can join #feature-widgets-block-editor in WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. for future Widget Editor-focused meetings.

Navigation Editor

Like the Widgets Editor, the Navigation Editor aims to help expand what’s possible with menus while bringing block functionality to yet another part of WordPress to allow for more adoption and offer a more modern experience. Because the Navigation Editor needs to work nicely with the Navigation block (and vice versa), much of the current effort from contributors focus on the Navigation block. With this in mind, current efforts include:

Follow along:

You can follow the progress of this project on this project board or review the new Navigation Editor tracking issue and join #feature-navigation-block-editor in WordPress.org Slack.

Full Site Editing

As with the prior months, work on this major focus for phase 2 is ongoing and is expected to continue as a big-picture goal for 2021. Work this month will include the following focus areas:

Milestone 1 – Site Editing Infrastructure and UI

Milestone 3 – Global Styles

Milestone 4 – Block Themes

Milestone 5 – Query Block

Milestone 6 – Navigation Block

Follow along:

You can follow the progress of this project with this overview issue showing key milestones for site editing. For each major milestone, there are related issues you can follow if you want a more granular look at each next step.

If you’re interested in testing Full Site Editing, check out the FSE Outreach Program to learn more. If you have questions about Full Site Editing, check out this recent effort to offer answers.

Areas to be aware of

Full Site Editing Roadmap:

Block & PluginPlugin 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 Developers:

Calls for testing:

Design:

A number of design explorations regarding improvements to reusable blocks are in the works, including:

Theme Developers:

Ways to Get Involved

While the above items are our focuses, don’t forget that you can always help with triage, needs testing issues, good first issues, and reviewing PRs. In particular, if you’re interested in helping with triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. but don’t know where to start, there’s a course on Learn WordPress for how to do triage in GitHub! Check it out and join us.

If there’s anything we can do to make contributing easier, let us know in the comments or in #core-editor chats. While we can’t promise to fix everything, we’d appreciate being aware of any blockers.

Meetings to join:

While you can view all meetings here, here are specific meetings to join depending on your interest. Remember that you need a WordPress.org slack account to participate:

  • Core Editor weekly Wednesdays @ 14:00 UTC in #core-editor focused on all things Gutenberg.
  • Block Themes meeting twice monthly on Wednesday @ 16:00 UTC in #themereview focused on preparing for Full Site Editing.

#core-editor #gutenberg-next #gutenberg

annezazu 5:28 pm on April 7, 2021
Tags: , , gutenberg   

Editor chat summary: 7 April, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on 2021-04-7 14:00 UTC in Slack. Moderated by @annezazu.

Announcements

Monthly Priorities & Key Project Updates

Full Site Editing from @youknowriad

  • Making the margins the same between frontend and backend (no opinionated margins provided by the 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. editor by default).
  • Working on adding a way to use block templates in classic themes as well which should provide a nice transition point.

Global Styles from @nosolosw

Shipped:

  • Block Supports: added a gutenberg_block_has_support helper function and support for padding in dynamic blocks 30322, border for search block #30227.
  • Fixes: title in the save panel of the site editor 30521, fix for themes without theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. support but with experimental link color support 30452.

Ongoing

  • Block supports: border for button block #30194, add border color/style/width properties #30124, spacing #30333 #30371.
  • Theme.json: Update format #29891, there’s now a draft PR at #30541, conversation about whether and how to expand the use of CSSCSS Cascading Style Sheets. Custom Properties #29714

Navigation Block from @mkaz and @andraganescu

Updates and improvements keep chugging along! The dependency on responsive nav will likely get merged today, and then the responsive PR can move forward. A new update attempts to fix the HTML produced by the block. This is blocked by the lack of advancement in the discussions opened by @talldanwp (Issue30007 and Issue30006). Any help moving those points forward would be greatly appreciated! Plenty of other refinements and updates continue too, for example the placeholder state was updated. The best way to follow along is by labels in GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ PRs or this tracking issue.

Navigation Editor from @andraganescu

The Block based Navigation editor is advancing with a host of PRs aimed at polishing various functionality (PR30374, PR30403, PR30524 , PR30340) and some that could use a review and testing (PR30446, PR30440, PR30349).

WidgetWidget 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. Editor from @andraganescu

Block based Widget Editor work is focused on tidying up blocks in 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 better accessibilityAccessibility 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 various bugs.

Mobile Gutenberg from @mattchowning

Landed

  • Block transforms
  • Removing ability to switch to the Classic editor when editing a post
  • Significantly the number of blocks that are tested on native by CI on each PR (relevant PR)

New In Progress

  • Slash inserter

Still In Progress

  • Dual licensing Gutenberg: planning to merge the PR with interim license this week
  • Global Style Support
  • Reusable blocks
  • Search block
  • Adding search to the block inserter
  • Embed block
  • Simplification of media insertion flow

Task Coordination

@mkaz

@ntsekouras

@mamaduka

  • Still working on the “Most used tags” feature.
  • Fixed “the same key” prop issue for gallery list items.
  • Started doing PR reviews by testing and adding comments. Hopefully, this can help the “Gutenberg CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.” team a little bit.
  • Currently figuring out the best way to filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. PRs for reviews.

@mikeschroder

  • I’d love feedback on the approach in this PR for 24337, please. If it seems appropriate, I can built it out for the rest of the existing blocks that support the feature, but thinking it’s possible this change should happen higher up somewhere so that blocks don’t have to adjust for it.

@annezazu

  • I’ve mainly focused on the FSE Outreach Program responding to the current call for testing and pausing to get some feedback for how to improve the program.
  • I plan to ship another call for testing shortly after this current one ends alongside a summary post.
  • I want to experiment tomorrow too with holding a friendly, casual zoom call for about 30-45 min to talk through some fun FSE issues/designs/PRs that have caught my attention! Join #fse-outreach-experiment to stay tuned if that’s of interest.

@aristath

  • I’ve been working on ways to make hybrid themes a reality. Among other things, there’s a PR to allow loading a block-based header & footer in classic themes which should help theme-authors to slowly start transitioning parts of their themes to FSE.
  • Other than that, lots of PR reviews.
  • Next week I will probably keep working on the same things: FSE MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia & hybrid-themes.

@joen

  • I’ve been continuing on the Navigation block, polishing and polishing. While it’s in a good place, it’s opening up some grand questions about the next steps, all exciting ones. And I’m excited to delve into patterns for it as soon as I can.

Open Floor

Are there any updates for a home/name for Site Editor Documentation? Raised by @poena.

Carolina brought up a previous post from early February asking whether there was an update around the name and place for documentation as currently it’s causing blockers/confusion for how to proceed. Currently, the documentation in the block editor handbook that’s related to FSE is in several places and pretty difficult to find. At the same time, as interest grows around FSE, people are seeking out more information. For example, one of the concerns that Carolina shared was around how if the documentation is in the theme developer handbook or the block editor handbook, it will be difficult to find and likely not visible enough for when a large number of people are first introduced to FSE. Carolina then passed along a suggestion to have a “front page” with basic explanations of the key concepts that then guides visitors to user or developer docs depending on their interests.

After some back and forth discussion, a loose consensus was reached on the following:

  • The lack of a decision around name and placement shouldn’t stop us from creating docs and organizing them properly when these things get clarified.
  • The go/no go dates should provide clarification this month around what needs to be documented first.
  • An introduction page that can guide people curious about FSE likely needs to be created or at least explored.
  • Exploring renaming the “Block Editor Handbook” to something more general might help alleviate some of these concerns by making the Handbook more flexible to allow for FSE items.

Next steps: @mkaz will kick off a discussion for renaming the handbook and create an issue for an initial intro FSE page to direct people.

#core-editor, #core-editor-summary, #gutenberg

Paal Joachim Romdahl 10:44 pm on April 5, 2021
Tags: , gutenberg, ,   

Editor chat summary: 31 March, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, March 31, 2021, 04:00 PM GMT+1 in Slack. Moderated by @paaljoachim.

WordPress 5.7.1

WordPress 5.7.1 maintenance release.
The following release schedule is being proposed:
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).: Wednesday 7 April, 2021 around 23:00 UTC.
Final release: Wednesday 14 April, 2021 around 23:00 UTC.

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/ 10.3

What’s new in Gutenberg 10.3.

5.8 Pre-planning

5.8 schedule

Monthly Priorities

March monthly priorities. Along with Key Project updates.

Global Style

Update from @nosolosw

Navigation Editor

Update from @grzegorz

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.

Update from @mkaz

Mobile

Update from @hypest

Full Site Editing

Update from @annezazu

Task Coordination

@annezazu

  • Mainly focused on FSE Outreach program (daily fse testing, reporting issues, writing up summaries, writing tests, amplifying!) and a few CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Improvement post ideas in the pipeline.

@aristath

  • Focus FSE and getting things ready for our MVP for inclusion in core.
  • Past week focused on implementations for hybrid themes, and also adding skip-links to FSE themes.
  • Focus on reviewing PRs.

@ntsekouras

@mamaduka

@poena

  • Reviews.
  • Testing Full Site Editing.
  • Reporting issues and creating pull requests toward the FSE MVP.

Open Floor

Discussing the Full Site Editing MVP.
To summarize the discussion that happened during the meeting and after, here are the top takeways:

  • There is confusion of what MVP for Full Site Editing consists of.
  • As has been previously shared, the MVP should make it possible to build a version of the Twenty Twenty-One theme, using only blocks, without any coding knowledge.
  • Widgets & Navigation work are not included in FSE but they are seen as complementary projects to help with adoption.
  • At the moment we have two targets: the full site editing MVP & what would be introduced in 5.8.

A link to the full discussion on Slack.

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