Title: 2021 – Page 47 – Make WordPress Core --- # Yearly Archives: 2021 [ ](https://profiles.wordpress.org/bernhard-reiter/) [Bernie Reiter](https://profiles.wordpress.org/bernhard-reiter/) 7:26 pm _on_ March 17, 2021 Tags: [core-editor ( 757 )](https://make.wordpress.org/core/tag/core-editor/), [editor ( 223 )](https://make.wordpress.org/core/tag/editor/), [gutenberg ( 547 )](https://make.wordpress.org/core/tag/gutenberg/), [gutenberg-new ( 217 )](https://make.wordpress.org/core/tag/gutenberg-new/)    # 󠀁[What’s new in Gutenberg 10.2? (17 March)](https://make.wordpress.org/core/2021/03/17/whats-new-in-gutenberg-10-2-17-march/)󠁿 It’s that time of the fortnight again: We’ve just published a new release of 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/](https://wordpress.org/gutenberg/)! Version 10.2 brings to you a number of additions to Full-Site Editing (FSE) and Global Styles, and a sizeable list of improvements to the editing experience, as well as 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. ## Offering Patterns on 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. setup Introducing some initial explorations on how specific patterns can be better surfaced from a block’s placeholder state. Upon inserting a Query block there’s now a setup step that allows picking a block pattern for it to use. This allows users to start with a good design basis. Note that this goes beyond what block variations afford, as it’s an 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. that can directly connect with a block pattern categoryCategory The' category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging.. The candidate block patterns are fetched via a new API that allows querying for patterns that include a given block type. Alternatively, the user has the option to “start empty”, in which case they’ll be able to choose from the existing CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. block _variations_ (e. g. Title & Date, Title & 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., etc). [[ ## Spacer Block width can be adjusted (in Navigation Block) When inserted into a parent block that dictates a horizontal orientation (such as the Navigation Block), the spacer block’s _width_ (rather than height) can now be adjusted. This makes some new cool customizations possible on horizontally-stacked blocks. [[ ## Transform Media & Text to Columns It has been possible for a while to transform any single block into a Columns block( with a single column). For the Media & Text block, that behavior is unlikely to produce the desired outcome. Thus, when transforming a Media & Text block into a Columns block, it will now result in _two_ columns (and all the relevant fixings from the original block). ## Hide writing prompt from subsequent empty paragraphs Rather than showing the “Start writing or type / to choose a block” prompt in each of a number of subsequent empty paragraphs, we now only show it in the first one. [[ ## 10.2 ### Features * Template part block: Add category panel. ([29159](https://github.com/WordPress/gutenberg/pull/29159)) ### Enhancements * Add check for button text before rendering button block. ([29717](https://github.com/WordPress/gutenberg/pull/29717)) * Skip CSSCSS Cascading Style Sheets. minification via PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher. ([29624](https://github.com/WordPress/gutenberg/pull/29624)) * Restore the margins of blocks relying on the figure element. ([29517](https://github.com/WordPress/gutenberg/pull/29517)) * Add Columns transform from Media & Text. ([29415](https://github.com/WordPress/gutenberg/pull/29415)) * Fix: Invert gallery gravity. ([29367](https://github.com/WordPress/gutenberg/pull/29367)) * Components: Try to make the order of fills stable in regular slots. ([29287](https://github.com/WordPress/gutenberg/pull/29287)) * Add expandOnFocus, showHowTo and validateInput experimental props to FormTokenField.( [29110](https://github.com/WordPress/gutenberg/pull/29110)) * Hide writing prompt from subsequent empty paragraphs. ([28275](https://github.com/WordPress/gutenberg/pull/28275)) ### New APIs * Plugins: Add scoping functionality to the Plugins API. ([27438](https://github.com/WordPress/gutenberg/pull/27438)) The `registerPlugin()` function (in the `@wordpress/plugins` package) now accepts a `scope` argument that will limit that 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. to be displayed only by `` components with a matching `scope` prop. See [#27438](https://github.com/WordPress/gutenberg/pull/27438) for more details. ### Bug Fixes * Reusable Blocks: - Fix editor crash when converting block with visible styles to reusable (after a save and page reload). ([29059](https://github.com/WordPress/gutenberg/pull/29059)) - Fix reusable block crash when converting a just created reusable block to blocks. ([29292](https://github.com/WordPress/gutenberg/pull/29292)) * Buttons Block: - Buttons: Fix links inside links. ([29273](https://github.com/WordPress/gutenberg/pull/29273)) - Fix legacy button center alignments inside the buttons block. ([29281](https://github.com/WordPress/gutenberg/pull/29281)) * Cover Block: - Fix cover block content position not migrating correctly from deprecated version.( [29542](https://github.com/WordPress/gutenberg/pull/29542)) - Fix solid-color only cover has small gray border in the editor only. ([29499](https://github.com/WordPress/gutenberg/pull/29499)) * Social Icons and Links: - Fix social icons vertical spacing issue. ([29657](https://github.com/WordPress/gutenberg/pull/29657)) - Yelp: Fix foreground color, make background transparent. ([29660](https://github.com/WordPress/gutenberg/pull/29660)) - Social Links: Replace CSS variables with block context approach. ([29330](https://github.com/WordPress/gutenberg/pull/29330)) * Table of Contents block: - Fix links when in archive 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](https://codex.wordpress.org/The_Loop) or when using “Plain” permalink structure. ([29394](https://github.com/WordPress/gutenberg/pull/29394)) - Fix class attribute. ([29317](https://github.com/WordPress/gutenberg/pull/29317)) * Add theme styles in the site editor. ([29704](https://github.com/WordPress/gutenberg/pull/29704)) * Fix broken links to the block editor developer handbook. ([29663](https://github.com/WordPress/gutenberg/pull/29663)) * Fix in between inserter edge case. ([29625](https://github.com/WordPress/gutenberg/pull/29625)) * Fix the button component styles when used with a dashicon. ([29614](https://github.com/WordPress/gutenberg/pull/29614)) * Revert moving is-typing class. ([29608](https://github.com/WordPress/gutenberg/pull/29608)) * Fix inline block styles minification issues with calc(). ([29554](https://github.com/WordPress/gutenberg/pull/29554)) * Packages: Update the publishing command for npm with next dist tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.). ([29379](https://github.com/WordPress/gutenberg/pull/29379)) * Ignore build folders when native unit tests. ([29371](https://github.com/WordPress/gutenberg/pull/29371)) * Fix mobile issue template label. ([29344](https://github.com/WordPress/gutenberg/pull/29344)) * Interface: Fix ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. [https://reactjs.org](https://reactjs.org/) warnings triggered in ActionItem component. ([29340](https://github.com/WordPress/gutenberg/pull/29340)) * Search block: Add missing space to provide valid HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers.. ([29314](https://github.com/WordPress/gutenberg/pull/29314)) * Blocks: Ensure that metadata registered on the server for core block is preserved on the client (try 2). ([29302](https://github.com/WordPress/gutenberg/pull/29302)) * Fix off-center appender in some themes. ([29290](https://github.com/WordPress/gutenberg/pull/29290)) * Add enableCustomSpacing to block editor settings. ([29277](https://github.com/WordPress/gutenberg/pull/29277)) * Border Radius Support: Fix application of zero radius values. ([28998](https://github.com/WordPress/gutenberg/pull/28998)) * Fix Document Outline mouse click. ([28589](https://github.com/WordPress/gutenberg/pull/28589)) * Fix typos in template part area tags. ([29937](https://github.com/WordPress/gutenberg/pull/29937)) * Gallery Block: Fix the crop images setting. ([29823](https://github.com/WordPress/gutenberg/pull/29823)) * Fix Error: Could not process the ‘wp-config.php’ transformation. ([29800](https://github.com/WordPress/gutenberg/pull/29800)) ### Performance * Revert “Block edit: Avoid memoized block context in favour of useSelect”. ([29621](https://github.com/WordPress/gutenberg/pull/29621)) ### Experiments * Global Styles: - Do not add padding sub-properties if there’s no values 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.. ([29712](https://github.com/WordPress/gutenberg/pull/29712)) - Fix specificity conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered _stale_, and will require a _refresh_ of the changes before it can be applied, or the conflicts will need to be _resolved_. of blocks with single classes as selectors. ([29378](https://github.com/WordPress/gutenberg/pull/29378)) - Fix specificity issue between theme and user styles. ([29533](https://github.com/WordPress/gutenberg/pull/29533)) - Custom Link Color: Do not apply to buttons. ([29557](https://github.com/WordPress/gutenberg/pull/29557)) - Implement skip serialization for color key in style att. ([29253](https://github.com/WordPress/gutenberg/pull/29253)) * Full-Site Editing: - Site Title: Add text decoration and text transform controls. ([29622](https://github.com/WordPress/gutenberg/pull/29622)) - Make border work on the site editor. ([29618](https://github.com/WordPress/gutenberg/pull/29618)) - Prevent clicking on tag and category links in the site editor. ([29583](https://github.com/WordPress/gutenberg/pull/29583)) - Print nothing in the front end if there are no results in Query block. ([29521](https://github.com/WordPress/gutenberg/pull/29521)) - [Query block] Remove exclusion of current page id. ([29432](https://github.com/WordPress/gutenberg/pull/29432)) - Handle missing categories/tags in Query block. ([29424](https://github.com/WordPress/gutenberg/pull/29424)) - Query block setup with block patterns integration. ([28891](https://github.com/WordPress/gutenberg/pull/28891)) - Update template descriptions for clarity and humanity. ([29531](https://github.com/WordPress/gutenberg/pull/29531)) - i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see [localization](https://make.wordpress.org/core/2021/page/47/?output_format=md#l10n). Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.: Fix the template area unassigned type string. ([29617](https://github.com/WordPress/gutenberg/pull/29617)) - Template Part: Prevent infinite recursion. ([28456](https://github.com/WordPress/gutenberg/pull/28456)) - Update title, description, and icon of Post Categories. ([29400](https://github.com/WordPress/gutenberg/pull/29400)) - Show Site Logo’s block toolbar when selected, after the editor loads. ([29336](https://github.com/WordPress/gutenberg/pull/29336)) - Remove delete toolbar option from Site Logo. ([29331](https://github.com/WordPress/gutenberg/pull/29331)) * Navigation Editor and Block: - Allow very thin menus. ([29555](https://github.com/WordPress/gutenberg/pull/29555)) - Refactor and simplify navigation block CSS. ([29465](https://github.com/WordPress/gutenberg/pull/29465)) - Make navigation placeholder state visible in dark themes. ([29366](https://github.com/WordPress/gutenberg/pull/29366)) - Update navigation editor menu selection dropdown. ([29202](https://github.com/WordPress/gutenberg/pull/29202)) - Make Spacer block width adjustable and add it to Navigation block. ([29133](https://github.com/WordPress/gutenberg/pull/29133)) - Navigation: Try adding navigation link variants via server. ([29095](https://github.com/WordPress/gutenberg/pull/29095)) - Navigation Editor: Allow menu renaming. ([29012](https://github.com/WordPress/gutenberg/pull/29012)) * Group Block: Add support for custom border settings. ([29591](https://github.com/WordPress/gutenberg/pull/29591)) * Pass block settings to the client for all blocks. ([29474](https://github.com/WordPress/gutenberg/pull/29474)) * Button block: Add color support via block.json. ([29382](https://github.com/WordPress/gutenberg/pull/29382)) * Add/new nav link icon. ([29369](https://github.com/WordPress/gutenberg/pull/29369)) * Temporary hack to render 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.. ([29365](https://github.com/WordPress/gutenberg/pull/29365)) * Fix shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. not showing in the widgets screen. ([29282](https://github.com/WordPress/gutenberg/pull/29282)) * Fix: More resilient appender CSS. ([28908](https://github.com/WordPress/gutenberg/pull/28908)) ### Documentation * Add block variations page to Block API summary. ([29725](https://github.com/WordPress/gutenberg/pull/29725)) * Update Readme of Animate Component to remove todo comment. ([29702](https://github.com/WordPress/gutenberg/pull/29702)) * Docs; Organize contributors section using READMEs. ([29688](https://github.com/WordPress/gutenberg/pull/29688)) * Remove mid-paragraph newlines. ([29674](https://github.com/WordPress/gutenberg/pull/29674)) * Update Versions in WordPress to include release notes. ([29532](https://github.com/WordPress/gutenberg/pull/29532)) * Extract block variations API into its own handbook page. ([29515](https://github.com/WordPress/gutenberg/pull/29515)) * Docs: Fix deprecation message to be clear. ([29451](https://github.com/WordPress/gutenberg/pull/29451)) * Fix typo in block-based-themes.md. ([29410](https://github.com/WordPress/gutenberg/pull/29410)) * Fix typo in modularity. ([29405](https://github.com/WordPress/gutenberg/pull/29405)) * Fix typos in git workflow documentation. ([29324](https://github.com/WordPress/gutenberg/pull/29324)) * Docs: Table of contents – fix typos. ([29319](https://github.com/WordPress/gutenberg/pull/29319)) * Add NVDA instructions to the 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) testing documentation. ([29312](https://github.com/WordPress/gutenberg/pull/29312)) * Component Systems: Update references to external module. ([29233](https://github.com/WordPress/gutenberg/pull/29233)) * Docs: Add info about npm release types and their schedule. ([29028](https://github.com/WordPress/gutenberg/pull/29028)) * Docs: Update slug for block-based theme tutorial. ([25839](https://github.com/WordPress/gutenberg/pull/25839)) ### Code Quality * Rename load_separate_block_styles to load_separate_block_assets. ([29703](https://github.com/WordPress/gutenberg/pull/29703)) * Update the minimum WordPress version required by the gutenberg plugin too 5.6.( [29701](https://github.com/WordPress/gutenberg/pull/29701)) * Components: Ensure that SlotFill does not use portals in React Native. ([29631](https://github.com/WordPress/gutenberg/pull/29631)) * Remove the subheading block. ([29627](https://github.com/WordPress/gutenberg/pull/29627)) * useFocusFirstElement: Include useRef. ([29435](https://github.com/WordPress/gutenberg/pull/29435)) * Include PHP: Replace `dirname( __FILE__ )` with `__DIR__`. ([29404](https://github.com/WordPress/gutenberg/pull/29404)) * Run phpcbf to fix PHP CS issues. ([29368](https://github.com/WordPress/gutenberg/pull/29368)) * Register style attribute when any color property is supported. ([29349](https://github.com/WordPress/gutenberg/pull/29349)) * Block context: - Remove unused onFocus block context. ([29318](https://github.com/WordPress/gutenberg/pull/29318)) - Reduce memoized block context: Class names. ([29186](https://github.com/WordPress/gutenberg/pull/29186)) - Remove obsolete block context. ([29313](https://github.com/WordPress/gutenberg/pull/29313)) - Block edit: Avoid memoized block context in favour of useSelect. ([29333](https://github.com/WordPress/gutenberg/pull/29333)) ### Tools * Scripts: - Fork jest-environment-puppeteer to use puppeteer-core directly. ([29418](https://github.com/WordPress/gutenberg/pull/29418)) - Add TypeScript support to linting command. ([27143](https://github.com/WordPress/gutenberg/pull/27143)) * Needs Info / Stale bot - Add stale issues bot to help triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. efforts.( [29321](https://github.com/WordPress/gutenberg/pull/29321)) - Do not automatically close message, update stale message. ([29310](https://github.com/WordPress/gutenberg/pull/29310)) * Tests: - Temporary skip flaky test. ([29601](https://github.com/WordPress/gutenberg/pull/29601)) - Paragraph block: Add test to ensure unwrapped editable paragraph. ([29299](https://github.com/WordPress/gutenberg/pull/29299)) - Testing: Use snapshot-diff serializer to remove noise in snapshots. ([29270](https://github.com/WordPress/gutenberg/pull/29270)) - Inserter: Add end-to-end test to make sure last inserted block is being focused.( [29187](https://github.com/WordPress/gutenberg/pull/29187)) * Blocks: Preprocess validation log with util.format instead of sprintf. ([29334](https://github.com/WordPress/gutenberg/pull/29334)) * Docs: Update release.md. ([29091](https://github.com/WordPress/gutenberg/pull/29091)) * Docs/Tools/CI: Update references from `master` to `trunk`. ([28433](https://github.com/WordPress/gutenberg/pull/28433)) ### Various * Full-Site Editing - Site Editor: Browsing 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. templates menu restructure. ([28291](https://github.com/WordPress/gutenberg/pull/28291)) - Site Editor: Persistent List View. ([28637](https://github.com/WordPress/gutenberg/pull/28637)) - Template part block: Add variations based on areas. ([29122](https://github.com/WordPress/gutenberg/pull/29122)) - Template Part: Update switching trigger. ([29257](https://github.com/WordPress/gutenberg/pull/29257)) - Template part ‘area’ term – reword confusing ‘type’ terminology. ([29679](https://github.com/WordPress/gutenberg/pull/29679)) - Add i18n support for template part variations’ descriptions. ([29612](https://github.com/WordPress/gutenberg/pull/29612)) - Multi entity save panel – remove dynamic copy. ([29637](https://github.com/WordPress/gutenberg/pull/29637)) * Table of Contents block - Add Table of Contents block (dynamic rendering + 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. version). ([21234](https://github.com/WordPress/gutenberg/pull/21234)) - Deregister TOC block until issues are resolved. ([29718](https://github.com/WordPress/gutenberg/pull/29718)) * Components: - Add next Button, ButtonGroup. ([29230](https://github.com/WordPress/gutenberg/pull/29230)) - Add Card. ([29350](https://github.com/WordPress/gutenberg/pull/29350)) - Add Divider. ([29433](https://github.com/WordPress/gutenberg/pull/29433)) - Add Popover. ([29084](https://github.com/WordPress/gutenberg/pull/29084)) - Add TooltipButton. ([29523](https://github.com/WordPress/gutenberg/pull/29523)) - Add Tooltip and Shortcut. ([29385](https://github.com/WordPress/gutenberg/pull/29385)) - Do not use ViewOwnProps for Portal. ([29345](https://github.com/WordPress/gutenberg/pull/29345)) - Update Elevation story. ([29454](https://github.com/WordPress/gutenberg/pull/29454)) * Component System: - Add basic tests for style system. ([29320](https://github.com/WordPress/gutenberg/pull/29320)) - Add tests for color utils. ([29301](https://github.com/WordPress/gutenberg/pull/29301)) * Types - api-fetch: Add incremental type checking. ([29685](https://github.com/WordPress/gutenberg/pull/29685)) - docgen: Add TypeScript support. ([29189](https://github.com/WordPress/gutenberg/pull/29189)) - docgen: Incrementally add types. ([29684](https://github.com/WordPress/gutenberg/pull/29684)) - Dom: Add type-checking to data-transfer. ([29682](https://github.com/WordPress/gutenberg/pull/29682)) - Components: Add types to Shortcut. ([29633](https://github.com/WordPress/gutenberg/pull/29633)) * Button Block: Removes “Link settings” panel. ([29664](https://github.com/WordPress/gutenberg/pull/29664)) * Add regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or [blockers](https://make.wordpress.org/core/2021/page/47/?output_format=md#blocker). 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. test for editor JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. crash caused by rtlcss parsing exception, take 2. ([29598](https://github.com/WordPress/gutenberg/pull/29598)) * Reset all WP Adminadmin (and super admin) styles in the wrapper of the editor styles. ([29590](https://github.com/WordPress/gutenberg/pull/29590)) * Revert “[Mobile] – Fix splitting/merging of Paragraph and Heading”. ([29587](https://github.com/WordPress/gutenberg/pull/29587)) * Try updating the minimum required WordPress version for the plugin. ([29579](https://github.com/WordPress/gutenberg/pull/29579)) * Documents how the widgets editor works. ([29572](https://github.com/WordPress/gutenberg/pull/29572)) * Drop zone: Fix media lib duplicate issue. ([29567](https://github.com/WordPress/gutenberg/pull/29567)) * Update the category icons. ([29553](https://github.com/WordPress/gutenberg/pull/29553)) * Try: Remove important on disabled switcher state. ([29552](https://github.com/WordPress/gutenberg/pull/29552)) * Remove base control negative help text margin. ([29550](https://github.com/WordPress/gutenberg/pull/29550)) * Navigation: Re-enable navigation block end-to-end tests. ([29543](https://github.com/WordPress/gutenberg/pull/29543)) * Accessibility improvement on [#29530](https://core.trac.wordpress.org/ticket/29530) issue. ([29534](https://github.com/WordPress/gutenberg/pull/29534)) * Pin SHA values as version numbers for 3rd party GHAs. ([29485](https://github.com/WordPress/gutenberg/pull/29485)) * Update the visual design of the Sidebar Menu. ([29476](https://github.com/WordPress/gutenberg/pull/29476)) * Focus on block selection: Skip inner blocks. ([29434](https://github.com/WordPress/gutenberg/pull/29434)) * Use correct classname for nested Navigation Link container. ([29380](https://github.com/WordPress/gutenberg/pull/29380)) * Integrate AztecEditor-iOSiOS The operating system used on iPhones and iPads. 1.19.4. ([29355](https://github.com/WordPress/gutenberg/pull/29355)) * Block context: Separate native context. ([29315](https://github.com/WordPress/gutenberg/pull/29315)) * Focus input when InputControl spinner arrows are pressed. ([29305](https://github.com/WordPress/gutenberg/pull/29305)) * WP Block Styles: Only load in the editor if a theme opts in. ([29252](https://github.com/WordPress/gutenberg/pull/29252)) * Add new overlay text icon, and use for image. ([29215](https://github.com/WordPress/gutenberg/pull/29215)) * Add Missing URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org state to Navigation Link Block. ([28861](https://github.com/WordPress/gutenberg/pull/28861)) * Improve dropcap behavior. ([28685](https://github.com/WordPress/gutenberg/pull/28685)) * Improve the block editor handbook table of content. ([28665](https://github.com/WordPress/gutenberg/pull/28665)) * RN: Add Bottom Sheet Select Control component. ([28543](https://github.com/WordPress/gutenberg/pull/28543)) * RichText: Bypass paste filters for internal paste. ([27967](https://github.com/WordPress/gutenberg/pull/27967)) * Block Directory: Update search results list UIUI User interface. ([25521](https://github.com/WordPress/gutenberg/pull/25521)) ## 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. | Version | Loading Time | KeyPress Event (typing) | | Gutenberg 10.2 | 5.25s | 25.8ms | | Gutenberg 10.1 | 5.01s | 23.1ms | | WordPress 5.7 | 5.13s | 22.3ms | Kudos to all the contributors that helped with the release! 👏 [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#editor](https://make.wordpress.org/core/tag/editor/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/), [#gutenberg-new](https://make.wordpress.org/core/tag/gutenberg-new/) [ ](https://profiles.wordpress.org/danfarrow/) [Dan Farrow](https://profiles.wordpress.org/danfarrow/) 1:44 pm _on_ March 17, 2021 Tags: [core-css ( 191 )](https://make.wordpress.org/core/tag/core-css/), [summary ( 975 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[CSS Chat Summary: 11 March 2021](https://make.wordpress.org/core/2021/03/17/css-chat-summary-11-march-2021/)󠁿 [The meeting took place here on Slack](https://wordpress.slack.com/archives/CQ7V4966Q/p1615500244188900). [@danfarrow](https://profiles.wordpress.org/danfarrow/) facilitated and wrote up these notes. ## Housekeeping * [@ryelle](https://profiles.wordpress.org/ryelle/) noted that daylight savings comes into effect in the US on March 13th and asked if we should change the meeting time * [@danfarrow](https://profiles.wordpress.org/danfarrow/) agreed that it would be good to move the meeting time but maybe not until UK daylight savings has come into effect at the end of the month, as otherwise the meeting would be at 11pm in the UK * We agreed that the [next meeting should stay as 22:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?msg=WordPress+CSS+Core+Chat&iso=20210318T22&p1=136&ah=1) and we can discuss the change then – if you have a preference please let us know! ## Discussion: Ideas for custom property naming * [@danfarrow](https://profiles.wordpress.org/danfarrow/) shared his [_custom property naming for buttons_ mock-up](https://ggm4x.csb.app/) which, with a little cheating, reduces the custom properties to `--button-color`, ` button-contrast-color` and `--button-active-color` * [@ryelle](https://profiles.wordpress.org/ryelle/) liked the use of the word ` contrast` to clarify the intent of the custom property * [@ryelle](https://profiles.wordpress.org/ryelle/)’s `--color-$n` approach received support from [@audrasjb](https://profiles.wordpress.org/audrasjb/) & [@danfarrow](https://profiles.wordpress.org/danfarrow/), however it still has the issue of a lack of context. When defining the numbered colour values it’s not clear what the contrast relationships should be between them * We concluded by following up [@notlaura](https://profiles.wordpress.org/notlaura/)’ s idea from last week of having people mock-up another UIUI User interface component of their choice with custom properties. **It would be great if people could bring their mock-ups to the March 25th meeting!** ## Project updates * There were no project updates this week ## Open floor / CSSCSS Cascading Style Sheets. link share * [@sabernhardt](https://profiles.wordpress.org/sabernhardt/) shared a link to ticketticket Created for both bug reports and feature development on the bug tracker. **[#52760](https://core.trac.wordpress.org/ticket/52760): Color not 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) for AA** which [@ryelle](https://profiles.wordpress.org/ryelle/) offered to look at * [@sabernhardt](https://profiles.wordpress.org/sabernhardt/) also asked for anyone with good flexbox knowledge to join the discussion on **[#28983](https://core.trac.wordpress.org/ticket/28983): Adminadmin (and super admin) bar length or Admin bar on two line** With that our time was up. Thanks everyone! [#core-css](https://make.wordpress.org/core/tag/core-css/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/desrosj/) [Jonathan Desrosiers](https://profiles.wordpress.org/desrosj/) 11:01 pm _on_ March 16, 2021   # 󠀁[Trial run: Consistent minor release squad leaders for each major branch](https://make.wordpress.org/core/2021/03/16/trial-run-consistent-minor-release-squad-leaders-for-each-major-branch/)󠁿 Minor releases (X.Y.Z+1) are WordPress releases that fall between major releases( X.Y+1) providing 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, small, self contained enhancements, and security fixes when appropriate. Minor versions are released as necessary. The current cadence is one every 4-6 weeks. Since WordPress 3.2, minor releases have been released (on average) every 5 weeks after another major or minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.. This cadence has increased slightly since WordPress 5.0 to an average of roughly every 4.5 weeks. ## **Pain points** With the minor release cycle, there are currently several pain points that make planning and executing difficult. ### **(Much) Shorter release cycle** The shorter release timelines for minor releases enable faster iteration on features included in major releases, and allows important bug fixes to be delivered to users faster. Which is great! However, it makes other parts of the release cycle, such as compiling a release team, much more difficult (this process can sometimes take up to 2 weeks). The real work for a release does not fully commence until after a release team is assembled. This results in minor releases having even less time for actual work than they should (2-4 weeks instead of 4-6). ### **Unknown scope** While minor releases focus only on bug fixes and small, self contained enhancements, some have a smaller, more targeted scope aimed at a more specific area of the code base. For example, if Feature A is included in the X.Y major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope., the scope for the X.Y.1 minor release may be aimed at polishing the user experience of Feature A. It can sometimes take 1-2 weeks to determine whether a more targeted scope is required (this is dictated by the incoming support and ticketticket Created for both bug reports and feature development on the bug tracker. volume). ### **Contributor focus** Oftentimes, minor releases are organized and executed by contributors that are also working on tickets, tasks, and features for the next major release. This can lead to divided attention and focus spread out between too many items. Additionally, when the date of an upcoming major release is nearing, it can cause a longer than usual gap when the attention of these contributors shifts fully to the next major release. For example, 5.4 was released nearly 15 weeks after 5.3.2. While this is the longest gap since 5.0, it’s not uncommon for a major release to be released 8-12 weeks after the last minor from the previous 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". ( the average since 5.0 is nearly 8 weeks). Though as many contributors as possible should focus on testing the next major release, there should not be a huge gap. Having a small team focused solely on minor releases will hopefully help shrink that gap while allowing other contributors continue to focus on the next major release. ### **Security** Occasionally, a minor release will include fixes for security vulnerabilities. These releases happen under a few different conditions: * There are enough security fixes to push out a minor release solely containing security fixes. * There is a minor release already planned and the security team is able to have fixes for known issues prepared. However, it’s difficult for the security team to plan and coordinate when minor releases will occur and, due to the issues mentioned above, know who to coordinate with. ## **Consistent minor release leads** **For the upcoming 5.7.x releases, a release leadRelease Lead The community member ultimately responsible for the Release. and release deputy will be named for all 5.7.x releases, and will serve until 5.8 is released.** These two contributors will be responsible for: * Publishing timelines and plans for each minor release. * Executing these plans through release day. * Coordinating with the Security Team lead to improve the flow of fixes from the team to users. * Assembling and requesting help from other volunteers for each release as deemed necessary (docs, test, specific focus areas, etc.). Ideally, one of these two contributors has a technical background (with the abilities to identify, confirm, test, and approve bug fixes and changes), and the other has a project manager or coordinator background (with the abilities to create release timelines, coordinate contributors, and help unblock efforts). One additional (potentially optional) criteria would be that either the lead or deputy be a part of the previous major release’s squad, or be very familiar with the changes that were introduced in that major release. This would further increase the speed at which the minor releases are able to fix related bugs, as they are already “up to speed” on the changes. In recent years, the gap between major releases has been, on average, 3 to 5 months. If necessary, contributors can tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) in and out of the role should circumstances change and it becomes necessary. The hope is that by eliminating the need to plan each and every minor release from scratch, the actual time contributors have to work on active bug fixing, triaging, testing, etc. will be increased, allowing minor releases to deliver fixes to users more quickly and effectively. If this works and the decision is made to continue this practice into the 5.8.x releases, the next two contributors should be named prior to 5.8’s final release to ensure a smooth transition. ## Volunteering If this is something you are interested in and you anticipate having the bandwidth for the next 3-4 months, or if you will be available to help our for the 5.7.x minor releases in other ways (triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., documentation, etc.), please feel free to comment below! And of course, questions and feedback are always welcome! _Props [@chanthaboune](https://profiles.wordpress.org/chanthaboune/), [@jeffpaul](https://profiles.wordpress.org/jeffpaul/), [@cbringmann](https://profiles.wordpress.org/cbringmann/), and [@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/) for peer reviewing._ [ ](https://profiles.wordpress.org/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/) 10:05 pm _on_ March 16, 2021 Tags: [5.7.1 ( 20 )](https://make.wordpress.org/core/tag/5-7-1/), [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/), [agenda ( 1,142 )](https://make.wordpress.org/core/tag/agenda/), [dev chat ( 922 )](https://make.wordpress.org/core/tag/dev-chat/)    # 󠀁[Dev Chat Agenda for March 17, 2021](https://make.wordpress.org/core/2021/03/16/dev-chat-agenda-for-march-17-2021/)󠁿 Here is the agenda for this week’s meetings to occur at the following times: [March 17, 2021 at 5:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210317T0500) and [March 17, 2021 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210317T2000). ## Announcements * Last week WordPress 5.7 “[Esperanza](https://wordpress.org/news/2021/03/esperanza/)” was release, in case you missed it ## Blogblog (versus network, site) Post Highlights * [[[[[A Week in Core – March 15, 2021](https://make.wordpress.org/core/2021/03/15/a-week-in-core-march-15-2021/) * [High level feedback from the FSE Program (March 2021)](https://make.wordpress.org/core/2021/03/16/high-level-feedback-from-the-fse-program-march/) * [Q2 Listening Hours: April 7th, 2021](https://make.wordpress.org/core/2021/03/12/q2-listening-hours-april-7th-2021/) * [Early Thoughts on WP5.8 Planning](https://make.wordpress.org/core/2021/03/12/early-thoughts-on-wp5-8-planning/) * [Block Editor Handbook: restructuring project update (March 12)](https://make.wordpress.org/core/2021/03/12/block-editor-handbook-restructuring-project-update-march-12/) ## Blog posts that need feedback * [Proposal: A WordPress Project Contributor Handbook](https://make.wordpress.org/updates/2021/03/16/proposal-a-wordpress-project-contributor-handbook/) * [WP Notify Office Hours Change](https://make.wordpress.org/core/2021/03/15/wp-notify-office-hours-change/)( Deadline March 22, 2021) ## Components check-in and status updates * Check-in with each component for status updates. * Poll for components that need assistance. ## Open Floor Do you have something to propose for the agenda, or a specific item relevant to our standard list above? Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you, accordingly. This meeting happens in the [#core](https://wordpress.slack.com/messages/C02RQBWTW) channel. To join the meeting, you’ll need an account on the [Making WordPress Slack](https://make.wordpress.org/chat/). [#5-7-1](https://make.wordpress.org/core/tag/5-7-1/), [#5-8](https://make.wordpress.org/core/tag/5-8/), [#agenda](https://make.wordpress.org/core/tag/agenda/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/) [ ](https://profiles.wordpress.org/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/) 7:37 pm _on_ March 16, 2021 Tags: [make.wordpress.org/updates ( 33 )](https://make.wordpress.org/core/tag/make-wordpress-orgupdates/), [p2-xpost ( 213 )](https://make.wordpress.org/core/tag/p2-xpost/)    # 󠀁[X-post: Proposal: A WordPress Project Contributor Handbook](https://make.wordpress.org/core/2021/03/16/xpost-proposal-a-wordpress-project-contributor-handbook/)󠁿 X-comment from [+make.wordpress.org/updates](https://make.wordpress.org/updates/): Comment on [Proposal: A WordPress Project Contributor Handbook](https://make.wordpress.org/updates/2021/03/16/proposal-a-wordpress-project-contributor-handbook/#comment-5141) [ ](https://profiles.wordpress.org/kjellr/) [Kjell Reigstad](https://profiles.wordpress.org/kjellr/) 7:02 pm _on_ March 16, 2021 Tags: [make.wordpress.org/themes ( 26 )](https://make.wordpress.org/core/tag/make-wordpress-org-themes/), [p2-xpost ( 213 )](https://make.wordpress.org/core/tag/p2-xpost/)    # 󠀁[X-post: Block-based Themes Meeting Agenda: Mar 17, 2021](https://make.wordpress.org/core/2021/03/16/xpost-block-based-themes-meeting-agenda-mar-17-2021/)󠁿 X-post from [+make.wordpress.org/themes](https://make.wordpress.org/themes/): [Block-based Themes Meeting Agenda: Mar 17, 2021](https://make.wordpress.org/themes/2021/03/16/block-based-themes-meeting-agenda-mar-17-2021/) [ ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/) 12:38 am _on_ March 16, 2021 Tags: [core-editor ( 757 )](https://make.wordpress.org/core/tag/core-editor/), [fse-outreach-program ( 5 )](https://make.wordpress.org/core/tag/fse-outreach-program/), [full-site editing ( 15 )](https://make.wordpress.org/core/tag/full-site-editing/), [gutenberg ( 547 )](https://make.wordpress.org/core/tag/gutenberg/)    # 󠀁[High level feedback from the FSE Program (March 2021)](https://make.wordpress.org/core/2021/03/16/high-level-feedback-from-the-fse-program-march/)󠁿 [After a few months](https://make.wordpress.org/core/2020/12/11/the-fse-outreach-program-is-officially-starting/) and [a few rounds of testing](https://make.wordpress.org/test/tag/fse-testing-call/) for the Full Site Editing Outreach Program, this post summarizes the top pieces of feedback of the current experience to help inform ongoing efforts for an 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](https://en.wikipedia.org/wiki/Minimum_viable_product). Keep in mind that this post is simply a snapshot in time and is inherently going to leave out aspects of the experience that haven’t been the subject of calls for testing yet, for example, Global Styles. If you want a more in-depth look at feedback across the testing calls and a full summary of all issues rather than a sampling, please [review the summary posts](https://make.wordpress.org/test/tag/fse-testing-summary/). If you want to help give feedback, join the [calls for testing](https://make.wordpress.org/test/tag/fse-testing-call/) or [test whenever you’d like.](https://make.wordpress.org/test/handbook/full-site-editing-outreach-experiment/how-to-test-fse/) **Previewing content** Across both calls for testing, it quickly became clear that previewing changes is a workflow people rely upon and miss deeply in the current experience, whether it was a desire to [preview changes to a template](https://github.com/WordPress/gutenberg/issues/28208) or to preview the entire site. A [“Preview Site” option is currently under discussion](https://github.com/WordPress/gutenberg/issues/29398), along with [exploring a possible browsing mode](https://github.com/WordPress/gutenberg/issues/23328) allowing a user to browse around their site within the editor.  **Saving Process** While the saving experience was reliable technically and generally intuitive, it has left a lot to be desired and resulted in a fair bit of confusion around expected behavior. This is likely because multi-entity saving (saving multiple aspects at once) is a new WordPress concept and one that underpins every interaction in the Site Editor. Whether it was mentioning [desired features](https://github.com/WordPress/gutenberg/issues/29577), [finding bugs](https://github.com/WordPress/gutenberg/issues/29803), or[ confusion around how to accomplish a task](https://github.com/WordPress/gutenberg/issues/27898), this proved to be a robust area of feedback.  **The distinction between editing the entire site vs. specific content** Similar to the saving process feedback, this is another area where features technically work but are difficult to distinguish across the experience. For example, one can edit a template directly, but it’s not always clear when one is editing a template or editing an item of content. Beyond just clarity in what one is editing, there needs to be the right amount of friction when switching between content that impacts the entire site vs. content on an individual post/page. This is an area of active iteration and exploration to get the right amount of friction in place, as you can see in open issues like [this one around clarifying template vs. content editing](https://github.com/WordPress/gutenberg/issues/27849), and this one around [refining the experience of editing a template part in isolation](https://github.com/WordPress/gutenberg/issues/29148). **Rethinking Width/Alignment** Currently, alignment in Full Site Editing works to optimize traditional themes that provide their own alignment styles. This approach has served the project well until this point, but it’s a key area to reconsider to ensure a true and reliable WYSIWYGWhat You See Is What You Get What You See Is What You Get. Most commonly used in relation to editors, where changes made in edit mode reflect exactly as they will translate to the published page. experience. Thankfully, work is already underway in [an important PR](https://github.com/WordPress/gutenberg/pull/29335) by [@youknowriad](https://profiles.wordpress.org/youknowriad/) to reimagine how this dynamic should allow for more control over alignments/widths when using the Site Editor.  **General Usability Improvements** As this work moves into a place of refinement, there are numerous enhancements to consider to improve overall usability of the Site Editor. This is a “catch-all” categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. but an important one nonetheless, as it will help the Site Editor experience move from functional to delightful. What follows is a sampling of items both to get a sense of the kinds of issues raised and the spread:  * [Add ability to set the Site Icon](https://github.com/WordPress/gutenberg/issues/29126)( also known as the favicon). * [Enable two+ word block searches](https://github.com/WordPress/gutenberg/issues/29495) with the slash command to make it easier to add Site Editing blocks.  * Selecting the [Top Toolbar Setting doesn’t stick in Site Editor](https://github.com/WordPress/gutenberg/issues/29386). * [Create a category specific to Site Editing blocks](https://github.com/WordPress/gutenberg/issues/26639) in the Inserter.  * [Add a “Revert to default” option](https://github.com/WordPress/gutenberg/issues/23421) for templates and template parts. * [Make it easier to add a background image](https://github.com/WordPress/gutenberg/issues/29238) to a template part.  * Make it clearer [how to get back into post/page editing mode](https://github.com/WordPress/gutenberg/issues/27899). * [Confirm changes are captured](https://github.com/WordPress/gutenberg/issues/29846) after updating design.  **Improving Placeholders** Placeholders for some of the newer blocks in the site editing experience prove to be both a powerful way to guide people and a point of confusion. This feedback mainly came into play with blocks like the [Query Block](https://github.com/WordPress/gutenberg/issues/27302)( including 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. variations like Posts Lists), [Social Icon Block](https://github.com/WordPress/gutenberg/issues/29505), [Featured Image Block](https://github.com/WordPress/gutenberg/issues/27617), and the [Navigation Block](https://github.com/WordPress/gutenberg/issues/24007). Each currently gets users started in different ways. In the long run, it seems that users will benefit from a standardized, consistent way to interact with placeholder content across all blocks. This is particularly important when viewed through the context of editing a template [where you might mostl](https://cloudup.com/c5XYFZ9AFhu)[y](https://cloudup.com/c5XYFZ9AFhu) [ see placeholder content.](https://cloudup.com/c5XYFZ9AFhu)  [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#fse-outreach-program](https://make.wordpress.org/core/tag/fse-outreach-program/), [#full-site-editing](https://make.wordpress.org/core/tag/full-site-editing/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 9:42 pm _on_ March 15, 2021 Tags: [5.7 ( 67 )](https://make.wordpress.org/core/tag/5-7/), [week in core ( 245 )](https://make.wordpress.org/core/tag/week-in-core/)    # 󠀁[A Week in Core – March 15, 2021](https://make.wordpress.org/core/2021/03/15/a-week-in-core-march-15-2021/)󠁿 Welcome back to a new issue of _Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress._. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between March 8 and March 15, 2021. * 12 commits * 17 contributors * 63 tickets created * 9 tickets reopened * 70 tickets closed There has been a low activity this week, as WordPress 5.7 was released last week. Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the [Trac timeline for the period above](https://core.trac.wordpress.org/timeline?from=02%2F15%2F2021&daysback=7&authors=&ticket=on&sfp_email=&sfph_mail=&update=Update). The following is a summary of commits, organized by component. ## Code changes ### Administration * 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): Use a darker color for post dates in the Activity and Quick Draft dashboard widgets – [#52760](https://core.trac.wordpress.org/ticket/52760) ### Bundled Themes * Twenty Seventeen: Remove extra space around post editor – [#52816](https://core.trac.wordpress.org/ticket/52816) Site Health: Use a singular string in dashboard 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. if there is only one critical issue or recommendation – [#52521](https://core.trac.wordpress.org/ticket/52521) Docs: Correct `unregister_block_style` param for `$block_name` – [#52795](https://core.trac.wordpress.org/ticket/52795) ### Coding Standards * Consistently format `opendir()` calls in `get_plugins()` – [#44250](https://core.trac.wordpress.org/ticket/44250) ### Docs * Improve spelling in [[50516]](https://core.trac.wordpress.org/changeset/50516)– [#52628](https://core.trac.wordpress.org/ticket/52628), [#34564](https://core.trac.wordpress.org/ticket/34564) * Improve compatibility comment in `WP_List_Table` – [#52628](https://core.trac.wordpress.org/ticket/52628), [#34564](https://core.trac.wordpress.org/ticket/34564) ### Editor * Make 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. type aware of variations – [#52688](https://core.trac.wordpress.org/ticket/52688) * Classic Editor: Make sure word count is hidden if JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. [https://www.javascript.com](https://www.javascript.com/) is disabled – [#52662](https://core.trac.wordpress.org/ticket/52662) ### Help/About * Run image comparison script after all assets have loaded – [#52758](https://core.trac.wordpress.org/ticket/52758) * Use absolute URLs for inline images on About pages – [#52743](https://core.trac.wordpress.org/ticket/52743) * Correct the WebM video URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org on About page – [#52756](https://core.trac.wordpress.org/ticket/52756) ## Props **Thanks to the 17 people who contributed to WordPress Core on Trac last week:** [@audrasjb](https://profiles.wordpress.org/audrasjb/) (4), [@sabernhardt](https://profiles.wordpress.org/sabernhardt/)( 3), [@vladytimy](https://profiles.wordpress.org/vladytimy/) (1), [@jeremyfelt](https://profiles.wordpress.org/jeremyfelt/)( 1), [@mihdan](https://profiles.wordpress.org/mihdan/) (1), [@subrataemfluence](https://profiles.wordpress.org/subrataemfluence/)( 1), [@TobiasBg](https://profiles.wordpress.org/tobiasbg/) (1), [@Otshelnik-Fm](https://profiles.wordpress.org/otshelnik-fm/)( 1), [@gwwar](https://profiles.wordpress.org/gwwar/) (1), [@timothyblynjacobs](https://profiles.wordpress.org/timothyblynjacobs/)( 1), [@joyously](https://profiles.wordpress.org/joyously/) (1), [@kraftner](https://profiles.wordpress.org/kraftner/)( 1), [@hareesh-pillai](https://profiles.wordpress.org/hareesh-pillai/) (1), [@Presskopp](https://profiles.wordpress.org/presskopp/)( 1), [@joseeyoast](https://profiles.wordpress.org/joseeyoast/) (1), [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)( 1), and [@mukesh27](https://profiles.wordpress.org/mukesh27/) (1). **Please join me to say _welcome_ to our 2 new Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. [https://core.trac.wordpress.org](https://core.trac.wordpress.org) of the week ♥️[@Otshelnik-Fm](https://profiles.wordpress.org/otshelnik-fm/) and [@joseeyoast](https://profiles.wordpress.org/joseeyoast/) **Core committers:** [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)( 6), [@ryelle](https://profiles.wordpress.org/ryelle/) (2), [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/)( 2), [@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/) (1), and [@gziolo](https://profiles.wordpress.org/gziolo/)( 1). Shout out to [@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/) for his first commit 🌟 _Please note: it only includes commits with proper props attribution._ [#5-7](https://make.wordpress.org/core/tag/5-7/), [#week-in-core](https://make.wordpress.org/core/tag/week-in-core/) [ ](https://profiles.wordpress.org/paaljoachim/) [Paal Joachim Romdahl](https://profiles.wordpress.org/paaljoachim/) 3:22 pm _on_ March 15, 2021 Tags: [agenda ( 1,142 )](https://make.wordpress.org/core/tag/agenda/), [core-editor ( 757 )](https://make.wordpress.org/core/tag/core-editor/), [core-editor-agenda ( 189 )](https://make.wordpress.org/core/tag/core-editor-agenda/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/)    # 󠀁[Editor Chat Agenda: 17 March 2021](https://make.wordpress.org/core/2021/03/15/editor-chat-agenda-17-march-2021/)󠁿 Facilitator and notetaker: [@itsjusteileen](https://profiles.wordpress.org/itsjusteileen/) This is the agenda for the weekly _editor chat_ scheduled for [Wednesday, March 17, 2021, 03:00 PM GMT+1](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Meeting&iso=20210317T10&p1=2157&ah=1). _This meeting is held in the [#core-editor](https://wordpress.slack.com/messages/C02QB2JS7) channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)._ * [WordPress 5.7](https://wordpress.org/news/2021/03/esperanza/) * 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/](https://wordpress.org/gutenberg/) 10.2 * [Monthly Plan for March 2021](https://make.wordpress.org/core/2021/03/08/whats-next-in-gutenberg-march-2021/) and key project updates: - Global Styles. * - 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. - Navigation block. - Full Site Editing. * Task Coordination. * Open Floor. If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion: * If you have anything to share for the Task Coordination section, please leave it as a comment on this post. * If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below. [#agenda](https://make.wordpress.org/core/tag/agenda/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#core-editor-agenda](https://make.wordpress.org/core/tag/core-editor-agenda/), [#meeting](https://make.wordpress.org/core/tag/meeting/) [ ](https://profiles.wordpress.org/psykro/) [Jonathan Bossenger](https://profiles.wordpress.org/psykro/) 2:55 pm _on_ March 15, 2021 Tags: [feature-notifications ( 49 )](https://make.wordpress.org/core/tag/feature-notifications/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/)    # 󠀁[WP Notify Office Hours Change](https://make.wordpress.org/core/2021/03/15/wp-notify-office-hours-change/)󠁿 I’d like to suggest a shift in the weekly WP Notify Office Hours. Due to a change in my personal life, I can no longer attend these office hours and successfully contribute. I would therefore like to suggest that we move office hours to either Tuesdays at 14:00 UTC or Thursdays at 14:00 UTC. I will leave the comments open until [Monday, March 22, 2021, 18:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210322T1800), at which time I will update this post with the final agreed upon change. [#feature-notifications](https://make.wordpress.org/core/tag/feature-notifications/), [#meeting](https://make.wordpress.org/core/tag/meeting/) # Post navigation [← Older posts](https://make.wordpress.org/core/2021/page/48/?output_format=md) [Newer posts →](https://make.wordpress.org/core/2021/page/46/?output_format=md)