Title: What’s new for developers? (April 2024)
Author: Justin Tadlock
Published: April 10, 2024
Last modified: May 11, 2024

---

 * [Showcase](https://wordpress.org/showcase/)
 * [Plugins](https://wordpress.org/plugins/)
 * [Themes](https://wordpress.org/themes/)
 * [Hosting](https://wordpress.org/hosting/)
 * [News](https://wordpress.org/news/)
    - [Learn WordPress](https://learn.wordpress.org/)
    - [Documentation](https://wordpress.org/documentation/)
    - [Education](https://wordpress.org/education/)
    - [Forums](https://wordpress.org/support/forums/)
    - [Developers](https://developer.wordpress.org/)
    - [Blocks](https://wordpress.org/blocks/)
    - [Patterns](https://wordpress.org/patterns/)
    - [Photos](https://wordpress.org/photos/)
    - [Openverse ︎](https://openverse.org/)
    - [WordPress.tv ︎](https://wordpress.tv/)
 *  - [About WordPress](https://wordpress.org/about/)
    - [Make WordPress](https://make.wordpress.org/)
    - [Events](https://events.wordpress.org/)
    - [Five for the Future](https://wordpress.org/five-for-the-future/)
    - [Enterprise](https://wordpress.org/enterprise/)
    - [Gutenberg ︎](https://wordpress.org/gutenberg/)
    - [Job Board ︎](https://jobs.wordpress.net/)
 * [Swag ︎](https://mercantile.wordpress.org/)
 * [Get WordPress](https://wordpress.org/download/)

Search in WordPress.org

 [ Get WordPress ](https://wordpress.org/download/)

[WordPress Developer Blog](https://developer.wordpress.org/news)

What’s new for developers? (April 2024)

 * [Snippets](https://developer.wordpress.org/news/snippets/)
    - [Blocks](https://developer.wordpress.org/news/category/blocks/)
    - [Concepts](https://developer.wordpress.org/news/category/concepts/)
    - [Common APIs](https://developer.wordpress.org/news/category/common-apis/)
    - [Design](https://developer.wordpress.org/news/category/design/)
    - [Playground](https://developer.wordpress.org/news/category/playground/)
    - [Plugins](https://developer.wordpress.org/news/category/plugins/)
    - [Themes](https://developer.wordpress.org/news/category/themes/)
 *  - [About this site](https://developer.wordpress.org/news/about/)
    - [Updates](https://developer.wordpress.org/news/category/updates/)
    - [How to contribute](https://developer.wordpress.org/news/how-to-contribute/)
    - [Tips and guidelines](https://developer.wordpress.org/news/tips-and-guidelines-for-writers/)
 * [Subscribe](https://developer.wordpress.org/news/subscribe/)
 * [Developer Resources](https://developer.wordpress.org/)

 * [Snippets](https://developer.wordpress.org/news/snippets/)
    - [Blocks](https://developer.wordpress.org/news/category/blocks/)
    - [Concepts](https://developer.wordpress.org/news/category/concepts/)
    - [Common APIs](https://developer.wordpress.org/news/category/common-apis/)
    - [Design](https://developer.wordpress.org/news/category/design/)
    - [Playground](https://developer.wordpress.org/news/category/playground/)
    - [Plugins](https://developer.wordpress.org/news/category/plugins/)
    - [Themes](https://developer.wordpress.org/news/category/themes/)
 *  - [About this site](https://developer.wordpress.org/news/about/)
    - [Updates](https://developer.wordpress.org/news/category/updates/)
    - [How to contribute](https://developer.wordpress.org/news/how-to-contribute/)
    - [Tips and guidelines](https://developer.wordpress.org/news/tips-and-guidelines-for-writers/)
 * [Subscribe](https://developer.wordpress.org/news/subscribe/)
 * [Developer Resources](https://developer.wordpress.org/)

# What’s new for developers? (April 2024)

By [Justin Tadlock](https://profiles.wordpress.org/greenshady/)

April 10, 2024

[Blocks](https://developer.wordpress.org/news/category/blocks/), [Plugins](https://developer.wordpress.org/news/category/plugins/),
[Themes](https://developer.wordpress.org/news/category/themes/)

What a month it’s been! [WordPress 6.5 “Regina”](https://wordpress.org/download/releases/6-5/)
officially launched after a minor issue set the release back one week. And there
are plenty of developer-related goodies, most of which you can check out in past
[monthly roundups](https://developer.wordpress.org/news/tag/roundup/) or many of
the other tutorials published here on the Developer Blog in the last couple of months.

And there’s still more to come, as our contributing writers are hard at work finalizing
additional content. Really, 6.5 was one of the heaviest developer-focused releases
we’ve had in a while, and I guarantee there’s something you’ll find useful for your
projects.

But the development cycle keeps spinning, and that means it’s time to set our sights
on the next major release: [WordPress 6.6](https://make.wordpress.org/core/6-6/).
In this edition of the monthly roundup, you’ll find a lot of new things that are
on the horizon.

**Heads up:** WordPress 6.6 will officially [drop support of PHP 7.0 and 7.1](https://make.wordpress.org/core/2024/04/08/dropping-support-for-php-7-1/).
The new minimum supported PHP version will be 7.2.24. This shouldn’t affect most
users, but be sure to upgrade any old versions before the 6.6 release if you’re 
one of the 2.45% of WordPress users still on one of those versions.

As usual, be sure to test the changes listed below with WordPress trunk and the 
latest version of the Gutenberg plugin.

Table of Contents

 1.  [Highlights](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#highlights)
 2.   a. [Interactive grid layouts and more](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#interactive-grid-layouts-and-more)
      b. [Color and typography presets in Global Styles](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#color-and-typography-presets-in-global-styles)
      c. [Root support for background images](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#root-support-for-background-images)
 3.  [Needs feedback: Major changes for meta boxes](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#needs-feedback-major-changes-for-meta-boxes)
 4.  [Plugins and tools](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#plugins-and-tools)
 5.   a.  [Playground plugin and more](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#playground-plugin-and-more)
      b.  [Block Bindings API updates](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#block-bindings-api-updates)
      c.  [Component updates](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#component-updates)
      d.  [Coding Standards updates](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#coding-standards-updates)
      e.  [Requests library updated](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#requests-library-updated)
      f.  [Unifying the Post and Site Editor](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#unifying-the-post-and-site-editor)
      g.  [Code blocks and line breaks](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#code-blocks-and-line-breaks)
      h.  [Pascal case template variable added to Create Block](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#pascal-case-template-variable-added-to-create-block)
      i.  [Extend the list of post content blocks](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#extend-the-list-of-post-content-blocks)
 6.  [Themes](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#themes)
 7.   a. [WordPress 6.5 lightbox settings regression](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#wordpress-6-5-lightbox-settings-regression)
      b. [Reducing specificity of global styles](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#reducing-specificity-of-global-styles)
      c. [Custom block CSS only rendered when in use](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#custom-block-css-only-rendered-when-in-use)
      d. [Template part replacement flow added to inspector controls](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#template-part-replacement-flow-added-to-inspector-controls)
      e. [Pattern overrides to use block name](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#pattern-overrides-to-use-block-name)
      f. [Featured image support for the Media & Text block](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#featured-image-support-for-the-media-text-block)
      g. [Block library updates](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#block-library-updates)
      h. [Notable bug fixes](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#notable-bug-fixes)
 8.  [Resources](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#resources)
 9.   a. [Developer Hours and Learn WordPress Tutorials](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#developer-hours-and-learn-wordpress-tutorials)
      b. [Hallway Hangouts](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#hallway-hangouts)
      c. [Developer Blog](https://developer.wordpress.org/news/2024/04/10/whats-new-for-developers-april-2024/#developer-blog)

## Highlights

### Interactive grid layouts and more

![WordPress post editor with a 3x3 grid of black boxes laid out in the content area.](
https://developer.wordpress.org/news/files/2024/04/grid-interactive.webp)

Awesome grid support is coming to WordPress. I know so many of you have been asking
for more since it was [introduced here on the Developer Blog](https://developer.wordpress.org/news/2024/02/06/adding-and-using-grid-support-in-wordpress-themes/).
Over the last several weeks, contributors have added some big features to grid layouts.

In Gutenberg 17.9, an [experimental “interactivity” mode](https://github.com/WordPress/gutenberg/pull/59052)
was added, allowing you to drag blocks across columns and rows that are nested within
a Grid. You can enable this by visiting **Gutenberg > Experiments** in your WordPress
admin and enabling the **Grid interactivity** option.

Gutenberg 18.0 shipped new enhancements to make the feature more powerful:

 * [**Column Start** and **Row Start** controls](https://github.com/WordPress/gutenberg/pull/59483)
   were added to the inspector for Grid children.
 * You can now select multiple blocks and [group them as a Grid](https://github.com/WordPress/gutenberg/pull/59853)
   as you would with other Group block variations.

### Color and typography presets in Global Styles

![WordPress Site Editor with the Styles > Colors panel open in the right. There 
is a grid of 9 preset color sets to choose from with various colors.](https://developer.
wordpress.org/news/files/2024/04/color-presets.webp)

In a nod to theme authors who have traditionally provided selectable typography 
sets and color schemes, contributors built [a similar system in Gutenberg 17.9](https://github.com/WordPress/gutenberg/pull/56622).
Under the **Styles** panel in the Site Editor, both the **Colors** and **Typography**
panels will now show presets that users can select to make quick global changes.

This new feature is backed by the existing [global style variations](https://developer.wordpress.org/themes/global-settings-and-styles/style-variations/)
system. Any colors or typography settings and styles defined via JSON files located
in your theme’s `/styles` folder will automatically become color or typography presets.
In practice, you could even create color or typography-only style variations just
for this purpose.

### Root support for background images

![WordPress Site Editor that shows a yellow to red gradient background. In the Sidebar
on the right, the Styles > Background panel is open and shows the gradient image
uploaded.](https://developer.wordpress.org/news/files/2024/04/background-global-
styles.webp)

Gutenberg 18.1 lets you define a [top-level background image](https://github.com/WordPress/gutenberg/pull/59354)
for the site in `theme.json`, which will open many opportunities for you to create
new and unique designs. Use the example code below to test this feature:

    ```language-json
    {
    	"$schema": "https://github.com/WordPress/gutenberg/raw/trunk/schemas/json/theme.json",
    	"version": 2,
    	"styles": {
    		"background": {
    			"backgroundImage": {
    				"url": "https://i0.wp.com/wordpress.org/files/2023/12/sotw-dotorg-drawer.png?w=1807&ssl=1",
    				"source": "file"
    			},
    			"backgroundPosition": "center center",
    			"backgroundRepeat": "repeat",
    			"backgroundSize": "cover"
    		}
    	}
    }
    ```

There is currently no method of defining a `theme` source and referencing a relative
image path that is stored in the theme. This is expected in a [followup enhancement](https://github.com/WordPress/gutenberg/pull/60578).

This change is also [accompanied by a UI control](https://github.com/WordPress/gutenberg/pull/59454)
that lets you set a background from the **Styles** panel in the Site Editor.

## Needs feedback: Major changes for meta boxes

A significant change is coming to how meta boxes are displayed in the Post Editor.
Instead of showing them at the bottom of the screen, [this PR collects and displays them](https://github.com/WordPress/gutenberg/pull/59242)
in a modal connected to a button in the top toolbar:

![WordPress post editor with a "Show meta boxes" toggle icon with a "Custom fields"
modal overlaid the screen.](https://developer.wordpress.org/news/files/2024/04/meta-
box-toggle.webp)

Meta boxes have been the _de facto_ standard interface for letting users enter custom
data from the post-editing screen throughout most of WordPress’s history, at least
until the launch of the Block Editor in version 5.0. To unify the Site and Post 
Editors, the Post Editor needs to be loaded in an iframe, and the current meta box
implementation prevents this from happening. This change will provide a consistent
WYSIWYG experience between the Editor and frontend views.

Ideally, if you are building a plugin that extends the editor with custom data input,
you would transition to one of the available [SlotFills](https://developer.wordpress.org/block-editor/reference-guides/slotfills/)
in the interface, creating a more integrated user experience.

Contributors ask for assistance in testing this PR with all sorts of plugins. To
test, download the [ZIP file from the ticket](https://github.com/WordPress/gutenberg/actions/runs/8112700478),
unzip it into the plugin directory of your test environment, and activate the plugin.
It needs to be unzipped and can’t be uploaded through the plugin page. Leave your
feedback on the ticket. For questions, you can also join the [#outreach channel ](https://wordpress.slack.com/archives/C015GUFFC00)
on WordPress Make Slack. 

## Plugins and tools

### Playground plugin and more

The [WordPress Playground project](https://wordpress.org/playground/) continues 
to evolve at a fast clip, and as always, we encourage you to give it a spin if you
haven’t already done so.

The biggest news is the availability of a new [Playground plugin](https://wordpress.org/plugins/playground/),
which lets you run a sandbox of your site in Playground and even test and install
plugins inside the sandbox. There are still some kinks to work out, such as this
[potential performance issue](https://github.com/WordPress/playground-tools/issues/222)
with large amounts of data. But give it a try and [report any issues](https://github.com/WordPress/playground-tools/issues)
you run into.

Other notable items include:

 * The start of a new [Blueprints PHP library](https://github.com/WordPress/wordpress-playground/issues/1025)
   for creating a consistent site setup tool that works with Playground, Docker,
   and hosted environments.
 * Stability improvements, including [over 50 resolved issues](https://github.com/WordPress/wordpress-playground/pulls?page=1&q=is%3Apr+is%3Aclosed)
   related to compatibility with native PHP, crashes, and error reporting.
 * The discussion on [version 2 of the Blueprints schema](https://github.com/WordPress/blueprints-library/issues/6)
   continues, and your feedback is wanted on the future of how Blueprints work.

### Block Bindings API updates

The initial version of the Block Bindings API shipped with WordPress 6.5, but there
is still much more work to be done before the API is as powerful as it should be.
A good place to start is an [update to the “Connected to custom field” message](https://github.com/WordPress/gutenberg/pull/59434)
when a block is bound to a custom data source, which was addressed in Gutenberg 
17.9.

A few key bug fixes were also shipped in the 6.5 release:

 * Bindings were corrected when used [inside the Query Loop block](https://github.com/WordPress/gutenberg/pull/59283)
   in the Editor.
 * [Protected fields](https://github.com/WordPress/gutenberg/pull/59326) bound to
   blocks are no longer shown.
 * Pressing `Enter` [when a bound block is selected](https://github.com/WordPress/gutenberg/pull/59361)
   now behaves correctly, creating a new block in the Editor.

### Component updates

Gutenberg 18.0 updated support for a couple of components:

 * `<TextControl>` [now supports](https://github.com/WordPress/gutenberg/pull/59666)`
   date`, `time`, and `datetime-local` types.
 * Nested `<MenuGroup>` [components are styled](https://github.com/WordPress/gutenberg/pull/59723)
   when used inside the `<Dropdown>` component.

### Coding Standards updates

Both the WordPress Coding Standards and PHP_CodeSniffer projects have been updated
in the past month. Be sure to upgrade if you rely on either of them:

 * [WordPress CS 3.1.0](https://github.com/WordPress/WordPress-Coding-Standards/releases/tag/3.1.0)
 * [PHP_CodeSniffer 3.9.1](https://github.com/PHPCSStandards/PHP_CodeSniffer/releases/tag/3.9.1)

### Requests library updated

Requests, the Core library that handles HTTP requests for interacting with other
sites, has been updated to [version 2.0.11](https://github.com/WordPress/Requests/releases/tag/v2.0.11)
with several changes. The most noteworthy are updates for PHP 8.4 support. This 
version of the library will [ship with WordPress 6.6](https://core.trac.wordpress.org/changeset/57876).

### Unifying the Post and Site Editor

An effort is underway to [unify and align](https://github.com/WordPress/gutenberg/issues/59878)
the publishing functionality between the Post and Site Editor. This requires slots,
actions, and selectors that were previously only available in the [`edit-post`](https://developer.wordpress.org/block-editor/reference-guides/packages/packages-edit-post/)
package to be moved to the [`editor`](https://developer.wordpress.org/block-editor/reference-guides/packages/packages-editor/)
package, which is available in both editors. Notably, the following slots are now
available in the Site Editor:

 * [`PluginDocumentSettingPanel`](https://github.com/WordPress/gutenberg/pull/59985#top)
 * [`PluginBlockSettingsMenuItem`](https://github.com/WordPress/gutenberg/pull/60033)
 * [`PluginPostPublishPanel`](https://github.com/WordPress/gutenberg/pull/60344)
 * [`PluginPrePublishPanel`](https://github.com/WordPress/gutenberg/pull/60344)

These slots will continue to work if you import them from the `edit-post` package,
but they will be deprecated when WordPress 6.6 is released in July.

### Code blocks and line breaks

As part of WordPress 6.5, the `RichText` component [was updated](https://github.com/WordPress/gutenberg/pull/55999)
so that line breaks are always serialized as HTML elements. This was done to improve
performance but had the unintended consequence of breaking third-party plugins that
apply syntax highlighting to the Code blocks. 

A fix [was implemented](https://github.com/WordPress/gutenberg/pull/59627) before
WordPress 6.5 was released, but any plugins that directly modify the save function
of the Code block will need to make additional adjustments. Guidance is provided
in the [pull request](https://github.com/WordPress/gutenberg/pull/59627). 

If you rely on a syntax highlighting plugin that experiences issues in WordPress
6.5, you can implement a temporary fix yourself by adding the following filter to
your theme:

    ```php
    /**
     * Replace breaks with new lines in all Code blocks on the front end.
     * This filter fixes an issue in the Code Syntax Block.
     *
     * @param string $block_content The block content about to be filtered.
     * @return string The filtered block content.
     */
    function themeslug_code_block_add_line_breaks( $block_content ) {
    	return str_ireplace(
    		[ '<br>', '<br/>', '<br />' ],
    		"\n",
    		$block_content
    	);
    }

    add_filter( 'render_block_core/code', 'themeslug_code_block_add_line_breaks', 10, 1 );
    ```

### Pascal case template variable added to Create Block

The Create Block package has a new [`namespacePascalCase` template variable](https://github.com/WordPress/gutenberg/pull/60223)
for populating valid PHP namespaces. So, a namespace of `create-block` becomes `
CreateBlock` when used for PHP namespaces and `@package` tags.

### Extend the list of post content blocks

Gutenberg 18.1 introduced a new `editor.postContentBlockTypes` JavaScript-based 
filter hook for the Editor. It lets you [customize the list of blocks](https://github.com/WordPress/gutenberg/pull/60068)
that should be enabled, even when used inside a locked template.

## Themes

### WordPress 6.5 lightbox settings regression

WordPress 6.5 [introduced a regression](https://github.com/WordPress/gutenberg/issues/59837)
for how lightbox settings work in `theme.json`. The issue made it impossible to 
enable lightbox while disabling user editing. There is a [fix in place](https://github.com/WordPress/gutenberg/pull/59890),
which was shipped with [version 6.5.2](https://wordpress.org/news/2024/04/wordpress-6-5-2-maintenance-and-security-release/).

### Reducing specificity of global styles

Two PRs landed in Gutenberg 18.1 aimed at reducing the specificity of global styles,
which nearly anyone who’s built a theme should appreciate. These tickets were split
into their component parts from an [earlier effort to reduce specificity](https://github.com/WordPress/gutenberg/pull/57841):

 * Reduce specificity of block library [styles conflicting with block supports](https://github.com/WordPress/gutenberg/pull/59457).
 * Reduce specificity of [global styles selectors only](https://github.com/WordPress/gutenberg/pull/60106).

Be sure to test these changes thoroughly alongside your themes if they have custom
styles to ensure compatibility.

### Custom block CSS only rendered when in use

Gutenberg 16.9 introduced a nice enhancement that cuts back on the CSS loaded on
any given page. Your [block-specific custom CSS](https://github.com/WordPress/gutenberg/pull/58991)
will now only render on the front end if the block is in use.

### Template part replacement flow added to inspector controls

This is more of a user-facing enhancement, but it should create fewer support headaches
for you if you build and distribute block themes. In Gutenberg 18.1, users can [replace template parts](https://github.com/WordPress/gutenberg/pull/55128)
via the inspector sidebar panel in the Sidebar Panel, which will display the alternative
parts and patterns available. This change makes the process of replacing a template
part globally much easier.

### Pattern overrides to use block name

The pattern overrides feature was not shipped with WordPress 6.5 as originally intended.
But work on the feature continues for a version 6.6 release. One of the primary 
issues was how to denote blocks as overridable in patterns. The current solution
is to [use the existing block naming feature](https://github.com/WordPress/gutenberg/pull/59268).

### Featured image support for the Media & Text block

In Gutenberg 18.0, you can set the Media & Text block to [use the featured image](https://github.com/WordPress/gutenberg/pull/51491),
just like the existing Cover image implementation. This opens a wealth of design
possibilities for column-based layouts inside the Query Loop block or for single
post/page templates.

### Block library updates

Several noteworthy block library updates have been added in the past month:

 * In Gutenberg 17.9, the Search block icon began using a [relative size (`1.25em`)](https://github.com/WordPress/gutenberg/pull/59159).
 * Added in Gutenberg 18.0, the Post Featured Image block [supports shadows](https://github.com/WordPress/gutenberg/pull/59616).
 * The Search block input field will correctly [inherit its typography rules](https://github.com/WordPress/gutenberg/pull/60321)
   as of Gutenberg 18.1.
 * Since Gutenberg 18.0, the Table block uses [fixed-width cells by default](https://github.com/WordPress/gutenberg/pull/49672).
 * The [Medium](https://github.com/WordPress/gutenberg/pull/57073) and [Reddit](https://github.com/WordPress/gutenberg/pull/59438)
   icons were updated to reflect the latest brand guidelines in Gutenberg 18.0.
 * Gutenberg 18.1 added [HTML element support](https://github.com/WordPress/gutenberg/pull/59654)
   to Site Tagline.

### Notable bug fixes

 * Theme fonts should [no longer be loaded twice](https://github.com/WordPress/gutenberg/pull/59421)
   in Gutenberg 17.9 since these are now handled by the font face resolver.
 * In Gutenberg 18.0, the [Cover block overlay will correctly display](https://github.com/WordPress/gutenberg/pull/59855)
   when connected to the featured image but there is no featured image present.
 * Also in Gutenberg 18.0, Social Link block label markup will only be [rendered when there’s a label](https://github.com/WordPress/gutenberg/pull/60060).
 * In Gutenberg 18.1, pattern previews should correctly [use a pattern’s defined viewport width](https://github.com/WordPress/gutenberg/pull/60315).

## Resources

### Developer Hours and Learn WordPress Tutorials

It’s been a busy few weeks for Developer Hours and Learn WordPress. Check out the
recordings and tutorials below: 

 * [Developer Hours: Exploring the Interactivity API in WordPress 6.5](https://www.youtube.com/watch?v=Sl6nqGN8YVQ&ab_channel=WordPress)
 * [Developer Hours: Exploring Block Hooks in WordPress 6.5](https://www.youtube.com/watch?v=ezPHiyhhaoQ)
 * [Developer Hours: Building custom blocks with the Interactivity API](https://youtu.be/ndW-Kz0iDdY)
 * [Exploring WordPress 6.5](https://learn.wordpress.org/tutorial/exploring-wordpress-6-5/)
 * [How to Test WordPress Beta Release?](https://learn.wordpress.org/tutorial/how-to-test-wordpress-beta-release/)

### Hallway Hangouts

Hallway Hangouts are an opportunity for the community to come together and discuss
important topics in WordPress. Recaps for the two events hosted in April are available:

 * [Hallway Hangout: Using Site Editor in Production for Client Sites](https://make.wordpress.org/core/2024/03/29/recap-hallway-hangout-using-site-editor-in-production-for-client-sites/)
 * [Hallway Hangout: Data Liberation Discussion and Brainstorm](https://make.wordpress.org/core/2024/03/26/hallway-hangout-data-liberation-discussion-and-brainstorm/)

### Developer Blog

Check out the most recent tutorial here on the Developer Blog if you haven’t already,
and stay tuned for more content showcasing features now available for WordPress 
6.5 and those being developed for WordPress 6.6:

 * [Introduction to Playground: running WordPress in the browser](https://developer.wordpress.org/news/2024/04/05/introduction-to-playground-running-wordpress-in-the-browser/)
 * [How to register custom font collections for the Font Library](https://developer.wordpress.org/news/2024/04/01/how-to-register-custom-font-collections-for-the-font-library/)
 * [How to work effectively with the useSelect hook](https://developer.wordpress.org/news/2024/03/28/how-to-work-effectively-with-the-useselect-hook/)
 * [How to use WordPress React components for plugin pages](https://developer.wordpress.org/news/2024/03/26/how-to-use-wordpress-react-components-for-plugin-pages/)
 * [Exploring the Block Hooks API in WordPress 6.5](https://developer.wordpress.org/news/2024/03/25/exploring-the-block-hooks-api-in-wordpress-6-5/)
 * [Drop Shadow updates in WordPress 6.5](https://developer.wordpress.org/news/2024/03/21/drop-shadow-updates-in-wordpress-6-5/)
 * [Pattern design tips and tricks for developers](https://developer.wordpress.org/news/2024/03/19/pattern-design-tips-and-tricks-for-developers/)
 * [How to register block variations with PHP](https://developer.wordpress.org/news/2024/03/14/how-to-register-block-variations-with-php/)

_Props to [@ndiego](https://profiles.wordpress.org/ndiego/) and [@bph](https://profiles.wordpress.org/bph/)
for co-writing and reviewing this article._

**Share the post: **

**Categories:** [Blocks](https://developer.wordpress.org/news/category/blocks/),
[Plugins](https://developer.wordpress.org/news/category/plugins/), [Themes](https://developer.wordpress.org/news/category/themes/)

**Tags:** [Monthly Roundups](https://developer.wordpress.org/news/tag/roundup/)

## 2 responses to “What’s new for developers? (April 2024)”

 1.  ![Tommaso Avatar](https://secure.gravatar.com/avatar/51d5c00240e114442f81b7646db4ca1e9c1fe88eb9af9efebd92450963e65da2?
     s=40&d=identicon&r=g)
 2.  Tommaso
 3.  [April 17, 2024](https://developer.wordpress.org/news/2024/04/whats-new-for-developers-april-2024/#comment-5309)
 4.  Support for mega menu was initially hypothesized for WordPress 6.5 and then later
     delayed to 6.6.
      I can’t see here any mentions related to the navigation block
     and the possibility to create mega menus.
 5.  [Reply](https://developer.wordpress.org/news/2024/04/whats-new-for-developers-april-2024/?replytocom=5309#respond)
 6.  ![sophia adam Avatar](https://secure.gravatar.com/avatar/6a9368a7aa5d3b50bd80618bee3d8ebb8af86779d45087ae71f4d9bd53e3c971?
     s=40&d=identicon&r=g)
 7.  [sophia adam](https://www.jorde-calf.com/)
 8.  [May 19, 2024](https://developer.wordpress.org/news/2024/04/whats-new-for-developers-april-2024/#comment-6148)
 9.  What a month it’s been! I’m excited about the official launch of WordPress 6.5“
     Regina,” even though a minor issue delayed it by a week. There are plenty of developer-
     related goodies to explore, as highlighted in the recent monthly roundups and 
     tutorials. With WordPress 6.6 on the horizon, don’t forget to upgrade from PHP
     7.0 and 7.1 before support drops. And if you’re looking to upgrade your style 
     too, check out these leather jackets for men!
 10. [Reply](https://developer.wordpress.org/news/2024/04/whats-new-for-developers-april-2024/?replytocom=6148#respond)

### Leave a Reply 󠀁[Cancel reply](https://developer.wordpress.org/news/2024/04/whats-new-for-developers-april-2024/?ref=hackernoon.com&output_format=md#respond)󠁿

Your email address will not be published. Required fields are marked *

Comment *

Name *

Email *

Website

 Save my name, email, and website in this browser for the next time I comment.

 Notify me of follow-up comments by email.

 Notify me of new posts by email.

Δ

## Have an idea for a new post?

### 󠀁[Learn how to contribute](https://developer.wordpress.org/news/how-to-contribute/)󠁿

Share your knowledge with fellow WordPress developers.

Search

### 󠀁[Review tips and guidelines](https://developer.wordpress.org/news/tips-and-guidelines-for-writers/)󠁿

Everything you need to know about writing for the Blog.

## Subscribe to the Blog

  Email Address

 Join 1,773 other subscribers

 * [About](https://wordpress.org/about/)
 * [News](https://wordpress.org/news/)
 * [Hosting](https://wordpress.org/hosting/)
 * [Privacy](https://wordpress.org/about/privacy/)

 * [Showcase](https://wordpress.org/showcase/)
 * [Themes](https://wordpress.org/themes/)
 * [Plugins](https://wordpress.org/plugins/)
 * [Patterns](https://wordpress.org/patterns/)

 * [Learn](https://learn.wordpress.org/)
 * [Documentation](https://wordpress.org/documentation/)
 * [Developers](https://developer.wordpress.org/)
 * [WordPress.tv ](https://wordpress.tv/)

 * [Get Involved](https://make.wordpress.org/)
 * [Events](https://events.wordpress.org/)
 * [Donate ](https://wordpressfoundation.org/donate/)
 * [Swag ](https://mercantile.wordpress.org/)

 * [WordPress.com ](https://wordpress.com/?ref=wporg-footer)
 * [Matt ](https://ma.tt/)
 * [bbPress ](https://bbpress.org/)
 * [BuddyPress ](https://buddypress.org/)

 The WordPress® trademark is the intellectual property of the WordPress Foundation.

 * [Visit our X (formerly Twitter) account](https://www.x.com/WordPress)
 * [Visit our Bluesky account](https://bsky.app/profile/wordpress.org)
 * [Visit our Mastodon account](https://mastodon.world/@WordPress)
 * [Visit our Threads account](https://www.threads.net/@wordpress)
 * [Visit our Facebook page](https://www.facebook.com/WordPress/)
 * [Visit our Instagram account](https://www.instagram.com/wordpress/)
 * [Visit our LinkedIn account](https://www.linkedin.com/company/wordpress)
 * [Visit our TikTok account](https://www.tiktok.com/@wordpress)
 * [Visit our YouTube channel](https://www.youtube.com/wordpress)
 * [Visit our Tumblr account](https://wordpress.tumblr.com/)