Planning for 7.0 – Make WordPress Core

Planning for 7.0 – Make WordPress Core
Skip to content
Make WordPress Core
Welcome!
The WordPress
core
Core
Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a
bug
bug
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.
Create a ticket
in the bug tracker.
Want to contribute?
Get started quickly with tickets marked as
good first bugs
for new contributors or join a
bug scrub
. There’s more on the
reports page
, like
patches needing testing
, and on
feature projects page
Other questions?
Here is a detailed
handbook for contributors
, complete with tutorials.
Communication
Core uses
Slack
for real-time communication. Contributors live all over the world, so there are discussions happening at all hours of the day.
Core development meetings are every Wednesday at
15:00 UTC
in the
#core
channel on
Slack
. Anyone can join and participate or listen in!
With 6.9
out in the world
, our collective attention has already turned to 7.0.
Core contributors
Core 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.
, together with Matt and Mary, had a call to discuss ideas and projects. There was shared excitement about this release, even if it’s
just
another number. This post acts as a gathering point for contributors to share what they are starting to work on and to find known areas they can contribute to. There will be another more tactical follow up with release schedule and responsibilities, this one is about the initial scope.
How to interact with this post
Please do not use this as a spot to request folks to work on features.
GitHub
GitHub
GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner.
and
Trac
Trac
An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.
are the best places to share feedback, talk about impact, and advocate for issues.
Please use this post to share what you are working on, including areas you’d like to help with that may be listed here, as well as areas that you are working on that are not. Items with TBD indicate areas where contributors are needed so please comment below if you’re keen to work on those pieces.
If you were planning to work in an area listed below and don’t see your name, please be sure to comment as well and it’ll be updated. It’s intentional that this post is meant to be a place to shore up who is working on what out in the open at this early stage.
Also note this is neither comprehensive nor yet a commitment that all of these things will be part of 7.0, since many are in early stages and may not make this release. Items marked with ✅ mean the work is already merged in
Gutenberg
Gutenberg
The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc.
or
trunk
trunk
A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.
Table of Contents
Collaboration
The project is getting deeper into Phase 3: Collaboration. Notes was a highlight feature in WP6.9 and there’s several improvements already planned to make it even more powerful and resilient.
Real time collaboration
Link:
GitHub issue
Key considerations:
There’s been a lot of progress in defining the
UI
UI
User interface
and the diffing mechanics for reconciling changes. It’s in very good shape and needs to be reviewed and tested diligently, especially around compatibility with third-party blocks and plugins.
This feature has a stronger dependency on server support and infrastructure than usual WordPress features, so there needs to be a definition of what’s the baseline experience shipping in WordPress (for example, peer-to-peer with 1 or 2 connections) and how it can be augmented, either by WP.org, hosting providers, or plugins.
Contributors:
acicovic
aduth
alecgeatches
czarate
ingeniumed
jsnajdr
, @maxschmelingkc,
paulkevan
shekharnwagh
youknowriad
Notes i2
Link:
GitHub issue
Key considerations:
Support partial selection inside
block
Block
Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.
rich text fields.
A “suggestions” mode and interface that allows Notes to refer to specific content within a block and apply the suggestions.
Support for multi-block notes.
Add rich text support in the comments.
Develop a dashboard
widget
Widget
A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user.
for recent notes.
More notification options (responses, follow a note, mentions).
Contributors:
adamsilverstein
jeffpaul
mamaduka
Admin
admin
(and super admin)
Improving screens across wp-admin
Link: TBD
Key considerations:
Explore CSS improvements
that can modernize the look and feel. For example, consider making the “modern” admin color scheme the default.
Admin bar and editor “site hub” improvements. Make the W menu item filterable. Possibly start work as an experiment in Gutenberg.
Consider a “This time last year” widget for bloggers.
Bring grid layout customization to dashboard experience or other screens. (Possible widgets at the top of comments, etc).
Contributors: TBD,
fabiankaegy
karmatosed
mcsf
DataViews and DataForms iterations
Link:
7.0 iteration issue
Key considerations:
DataForms/QuickEdit/Document inspector design iterations.
Hierarchical post visualization.
Make DataViews screens
extensible
Extensible
This is the ability to add additional functionality to the code. Plugins extend the WordPress core software.
in the site editor (templates, pages, etc).
Contributors:
oandregal
Design System
Link:
GitHub issue
Key considerations:
Components are already being worked on in wordpress/ui.
Theming system with design tokens using wordpress/theme.
Start replacing key parts of the editor UI with improved components (tabs, flyout menus).
Contributors:
0mirka00
aduth
jsnajdr
mciampini
wildworks
Font library admin section
Link:
Github issue
Key considerations:
Support for block themes.
Support for hybrid/classic themes.
Contributors:
youknowriad
Revisions
Revisions
The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision.
Link:
GitHub issue
Key tasks:
Rethink the revisions interface to be more modern, intuitive, and work with blocks.
Show visual diffs.
Bonus: potentially tie in with collaborative editing, suggestions, and undo management.
Contributors:
adamsilverstein
Customizable Keyboard Shortcuts
Link:
Github issue
Key considerations:
Build with design system components.
Contributors: TBD
APIs
Abilities & Workflows
API
API
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.
Link:
Github issue
Key considerations:
Hybrid abilities.
The client side package.
Driven by Fields API definitions.
Querying and filtering functionality for the abilities.
Implement some of the abilities
outlined in WordPress Core Abilities
Command palette and UI:
Differentiation between commands.
Ability to support two stages of a command.
Contributors:
jorgefilipecosta
gziolo
senadir
youknowriad
Upgrade to
React
React
React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces.
19
Link:
Github issue
Key considerations:
There’s a path for the block editor in the mobile apps that should remove this dependency
blocker
blocker
A bug which is so severe that it blocks a release.
Ecosystem impact.
Contributors:
aduth
jsnajdr
mamaduka
ralucastn
tyxla
Block API: Add validation levels
Links:
Github issue
with
initial PR
Key considerations:
The scope of this issue is to drastically reduce the amount of times a user sees a “this block is broken” message.
Impact on block API.
Contributors:
matveb
mcsf
youknowriad
Enforced iframed editor
Link:
GitHub issue
Backwards compatibility, extended testing.
Migration
Migration
Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies.
guide.
Contributors:
ellatrix
wildworks
WP client AI API
Link:
GitHub project
Key considerations:
An AI client and API for WordPress to communicate with any generative AI models of various
capabilities
capability
capability
is permission to perform one or more types of task. Checking if a user has a capability is performed by the
current_user_can
function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability).
using a uniform API.
Integration with Abilities API.
Strictly no providers included in
core
Core
Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
Decide nomenclature.
Ideally, the minimum
PHP
PHP
The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher
version has to be bumped from PHP 7.2.
Contributors:
flixos90
jason_the_adams
Creating blocks and patterns on the server
Link:
GitHub issue
Key considerations:
Most of the tools for a pretty straightforward PHP-only representation of blocks and patterns, including bindings, are ready.
Declarative block attributes and form components.
Pattern creation and syntax that allows easy construction of blocks and bindings.
Contributors:
priethor
, TBD
wordpress/build and routing (site editor)
Link:
GitHub issue
Scripts issue
Key considerations.
Add extensibility to site editor routing.
Dependency on standalone font library.
Refactor the site editor to allow
plugin
Plugin
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
or can be cost-based plugin from a third-party.
authors to add their pages there.
Opinionated build tool for plugins.
Update Gutenberg – Core
backport
backport
A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch.
flow.
Contributors:
youknowriad
Shortblocks
Links:
Bits as dynamic tokens
Bits: Introduce the ability to store and render bits
Rich text: try BITS with block binding API
Introduce parser for dynamic token system
Key considerations:
Decide name for the feature (shortblocks, inline blocks, bits).
Determine best syntax.
Connect with bindings UI.
Support for rich text autocomplete.
Contributors:
dmsnell
ellatrix
jonsurrell
Block bindings iterations
Link:
GitHub issue
Key considerations:
Open up “Pattern Overrides” and therefore intern block bindings to custom dynamic blocks
Filter available source items for a given attribute by format
Align with Fields API as a requirement.
Contributors:
bernhard-reiter
Navigation Block
A series of improvements were identified to simplify the navigation workflow and make the experience of managing menus more intuitive and straightforward.
Simpler navigation editing
Link:
GitHub issue
Key considerations:
Better insertion
Pattern editing and ContentOnly interactivity
Better presentation of “bound” page items.
Contributors:
get_dave
jeryj
Ability to customise “mobile” overlay
Link:
GitHub issue
Key considerations:
Implemented as a template part.
Ability to customize when the overlay appears (breakpoint settings) just for navigation overlay.
Contributors:
get_dave
jeryj
Customization
Over the past couple years we’ve been iterating on a series of related systems with the hope of arriving at a more streamlined editing experience of composite blocks and design patterns. We have some solid directions sketched out that are looking promising.
Explore more intuitive page navigation in the site editor
Link: TBD
Key considerations:
Modify the title bar to display a pages dropdown instead of empty command palette. List the pages used in the primary menu with a link to “browse all pages”.
Exploration
Add next/previous page links in zoomed-out view, similar to a carousel. See a preview in a zoomed out state with arrows next to preview or title bar.
Exploration
Contributors:
ellatrix
Pattern Editing (aka ContentOnly)
Link:
GitHub issue
Key considerations:
Ensure proper discoverability to enter/exit.
Ensure it works well with synced patterns.
Contributors:
aaronrobertshaw
andrewserong
isabel_brison
ramonopoly
talldanwp
Improve template management
Link:
GitHub PR
Key considerations:
Direction and
UX
UX
User experience
is still TBD and needs more exploration.
Retain access to template parts across theme switches
Contributors:
ellatrix
scruffian
Responsive editing mode
Link:
GitHub issue
Key considerations:
Toggle to engage responsive editing mode.
Block visibility i2:
add ability to hide blocks based on screen size
Allow style changes to be saved and retrieved for different breakpoints.
Allow customization of hardcoded breakpoints.
Contributors:
matveb
ramonopoly
Block supports and design tools:
Link:
GitHub issue
Key considerations:
Add text line indent support.
GitHub PR
Add
gradient support to text color options
Add height block support to dimension
Styles support for text shadow.
GitHub PR
Support for text alignment
with justify support
Allow Video backgrounds to be ‘Fixed’
Balanced line wrap
Text columns.
GitHub issue
GitHub issue
Support aspect ratio
on wide and full images
Contributors: TBD,
aaronrobertshaw
matveb
youknowriad
wildworks
Blocks
Keeping the momentum
on adding new blocks
and new block tools to expand the palette and expressiveness offered to theme builders and users. There’s also some refinements to some fundamental aspects of blocks to make them more resilient and more consistent.
Group block attributes
Link:
GitHub Issue
Key considerations:
Adding groups to InspectorControls (like BlockControls).
Add support for list representation to block API based on nav block work.
Implement content representation for media and rich text attributes. (Connected with contentOnly, bindings, and partially synced patterns work.)
Contributors: TBD
✅ Cover block: video embeds
Link:
GitHub Issue
GitHub PR
Contributors:
matveb
Modernize Code editor + Code block
Link:
GitHub link
Contributors:
jonsurrell
westonruter
Lazy load the Classic block
Link: TBD
Key considerations:
The main aim is performance—avoid loading TinyMCE by default if not needed.
If possible, address
moving the freeform block to a separate package
in this work too.
Contributors:
tyxla
Leverage iAPI for instant search block & submit comments without full page refresh
Links:
Instant Search
submit comments without requiring a full-page refresh
Contributors: TBD
Writing flow + drag and drop improvements
Link:
GitHub issue
Key considerations:
Get to a place where the drag handle from the toolbar can be entirely removed due to improved drag and drop functionality.
Making multi selection work on touch devices.
Improvements to inline insertion
and inline images.
Contributors:
ellatrix
✅ Tabs block
Link:
GitHub issue
Contributors:
mikachan
Release the Table of Contents block
Link:
GitHub issue
Contributors: TBD
Playlist block
Link:
GitHub issue
Contributors:
scruffian
Slider block
Link:
GitHub issue
GitHub issue
GitHub issue
Contributors:
lstraczynski
karolmanijak
Dialog block
Link:
GitHub issue
Contributors: TBD
✅ Breadcrumb block
Link:
GitHub Issue
Team:
ntsekouras
Add more dynamic URLs via block bindings to Buttons block and Image block
Link:
GitHub issue
API shape
Team: TBD
Icon block
Link:
GitHub issue
Key considerations:
Ship with a default set made out of some wordpress/icons.
Allow extenders to register their own sets.
Contributors:
mcsf
welcher
Gallery block: add lightbox support with the ability to switch between images
Link:
GitHub issue
GitHub PR
Contributor:
wildworks
Introduce heading levels as Heading block variations
Link:
Github issue
Key considerations:
Show up in search and slash inserter.
Easy toggling in
sidebar
Sidebar
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.
inspector and transforms.
Contributor:
matveb
Aim to stabilize grid block
Link:
GitHub issue
Contributor:
isabel_brison
Media
Client side media work
Link:
GitHub issue
Contributors:
adamsilverstein
ramonopoly
Media editor
Link:
Iteration issue
Contributors:
aaronrobertshaw
andrewserong
isabel_brison
ramonopoly
talldanwp
Designers looking across all these projects:
fcoveram
joen
jameskoster
mattmiklic
7-0
phase-3
Share this:
Share on Threads (Opens in new window)
Threads
Share on Mastodon (Opens in new window)
Mastodon
Share on Bluesky (Opens in new window)
Bluesky
Share on X (Opens in new window)
Share on Facebook (Opens in new window)
Share on LinkedIn (Opens in new window)
I realize this is not a commitment but it’s an impressive list nonetheless. I hope we can ship the maximum from this.
My question is: will responsiveness become a priority in the next ten years?
Responsive editing mode is listed here. Please check it out! It continues a range of work around responsiveness that’s been done in prior releases.
We fully embraced container queries with our custom theme and custom blocks (and
core
Core
Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
blocks where needed/possible) and have almost entirely eliminated the need for device size based settings/styles in the
block
Block
Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.
editor.
I didn’t see the tests update to support PHPUnit 10/11 in the list
I want to get this task done so I can get back to writing the missing tests!!
Really excited to see this list, looking forward to diving in where is needed and us all improving the experience.
This looks great! Excited to see where 7.0 takes us ✨
This list is huge, so exciting to see all the features and work underway.
Please add my name to the Notes i2 list as I plan to continue working on Notes. Also, please add me to
Revisions
Revisions
The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision.
– although not my highest priority this cycle, I am deeply invested in revisions and plan to support from the
core
Core
Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
side at a minimum.
Done, thank you! 🙂
Worth noting that I’ve been working on in-editor
revisions
Revisions
The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision.
tracking issue
).
Wow what a huge list, very exciting. Just as an update from me, I plan on getting Dialog to experimental state in January and if someone doesn’t beat me to it I can come back in and finish off the polish list on Tabs.
Improving screens across wp-
admin
admin
(and super admin)
Please also add my name to this as I am already starting to find ways to collaborate. Along with this I would also be very happy to contribute to ‘Design System’. I want to be helpful in other ways that are useful but this is where I am starting.
Let’s add “View Transitions” to this list, per
Matt in #core
. I’ll be contributing to that. This will go nicely with the
admin
admin
(and super admin)
refresh. The admin view transitions should be an easy lift. I’m not entirely sure view transitions on the frontend will be so straightforward. We may need to scope specifically to Twenty Twenty-Five (or to
block
Block
Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.
themes) but then provide an
API
API
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.
for themes to configure for their needs. The
feature plugin
introduces a
view-transitions
theme support for this purpose.
I’ve filed two tickets:
#64470
(for the
admin
admin
(and super admin)
) and
#64471
(for the frontend).
Improve template management
This is punted to a future release until we agree on a design and
UX
UX
User experience
I wanted to re-share an update from the
DataViews/DataForm iteration issue
Some tasks had been punted for the next iteration, including
visualizing hierarchical post types
The current focus is on the aspects of the Field
API
API
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.
we need to support well emerging use cases, such as
Pattern editing
and
PHP-only blocks
. We’re prioritizing work on:
74409
74858
74856
73180
72614
74105
We still want to extend the existing Site Editor screens, but it has been scoped down to registering fields as per
#74865
. We’ll focus on the above foundational work, first.
As we are veering towards
beta
Beta
A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.
1, I wanted to share a bigger update of where the above stands as I can gather from talking to people, testing, and gathering updates. I’m sharing this here for completeness and will link to it in the 7-0 release leads channel for others to benefit from. This is purposefully very, very, very concise.
Green (Good Progress/Ready)
Real time collaboration
. There are some remaining questions around opt in/opt out strategies and limitations that are being sorted and are known.
Visual Revisions
PHP-only block registration w/ auto-generated inspector controls
Navigation: Ability to customise “mobile” overlay
Simpler navigation editing
Ability to hide blocks responsively
Add QuickEdit to Data Views
Cover: add support for background videos as embeds
. Note that this has
some residual questions around opt out options
Breadcrumb block
Icon block
Enable grid block to be responsive when columns are set
, along with a
range of other improvements.
Gallery block: add lightbox support
Introduce heading levels as Heading block variations
(sub item of
block
Block
Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.
supports).
Block bindings: Open up “Pattern Overrides”
Add text line indent support
(sub item of block supports).
Add height block support to dimension
(sub item of block supports).
Support aspect ratio on wide and full images
(sub item of block supports).
Client side Abilities API
(sub item of Abilities & Workflows).
Improving screens across wp-admin
. The
ticket
ticket
Created for both bug reports and feature development on the bug tracker.
is still open but there
have been PRs done against this
Dedicated font library section
with compatibility for all themes. There were concerns with related build process changes within this work when it comes to wordpress/build and routing (punted for everything else outside of the site editor) but it’s not dependent to land the feature.
Pattern Editing
(aka ContentOnly). The bulk of the features landed with an
iteration issue
opened already for 7.1.
WP client AI API
. Made it after discussion on the review call for 7.0.
Yellow (At Risk/Nearly there)
This section was updated and edited over the last 24 hours since the comment was originally posted to share where things ended up in the green or red sections.
🔴 Red (Blocked/Major Issues)
Client side media
improvements.
Tabs block
. The block was moved back to experimental ahead of the GB release and was decided to not move ahead in 7.0. There are some aspects of the active tab state that are being done in a non-standard way and a more general solution is desired.
wordpress/build and routing
(site editor). See dedicated font library section.
Playlist block
. Work didn’t finish in time.
Dialog block
. Work didn’t finish.
Notes: Emoji support
. Decision around storage too last minute.
Notes: Compact mode
. Decision around design too last minute.
WordPress Core Abilities
(sub item of Abilities & Workflows)
Markdown generator for content
. Work was rapidly evolving but it’s unclear what can land for
Core
Core
Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
and needs more time. Work will focus on adding to
wordpress.org
WordPress.org
The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization.
for now.
Cancelled
Hierarchical post visualization (sub-item of DataViews)
Design System
Customizable Keyboard Shortcuts
Upgrade to
React
React
React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces.
19
Block
API
API
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.
: Add validation levels
Enforced iframed editor
Shortblocks
The remaining block bindings iterations for
bug
bug
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 and enhancements.
Explore more intuitive page navigation in the site editor
Improve template management
Group block attributes
Modernize Code editor + Code block
Lazy load the Classic block
Leverage iAPI for instant search block & submit comments
Writing flow + drag and drop improvements
Release the Table of Contents block
Slider block.
Add more dynamic URLs via block bindings
Media editor
cc @matveb @4thhubbard for your awareness as both project leadership and release squad members.
Hi
annezazu
Notes: Emoji support & Compact mode are blocked. Do you have any news about “
Support partial text selection notes”
As you can see, it has not been merged. To help out,
I added an update for Notes and what shipped here
. There are no new major features.
Heads up that I just finished updating the above comment with the latest that I can find for the release. In particular, I focused on the yellow section for anything that is sitting in between as those are the most relevant and important areas to track.
Looks like
Image: add focal point controls
is also coming in 7.0 – yay!
Comments are closed.
Site resources
Email Updates
Enter your email address to subscribe to this blog and receive notifications of new posts by email.
Join 6,694 other subscribers
Recent Updates
Recent Comments
No Replies
Current Release
The current release in progress is
WordPress 7.0
. Planned future releases are listed on
the Project Roadmap
. Feature projects not tied to specific releases can be found on
the Features page.
Regular Chats
Note:
All chats happen on
Slack
Weekly Developer Meetings
: [time relative]Wednesday 15:00 UTC[/time] in
#core
About the Dev Chat
Agendas
Summaries
Performance Weekly Chat
[time relative]Tuesday 15:00 UTC[/time] in
#core-performance
New Contributors Chat
The 2nd and 4th Wednesday of every month at 17:00 UTC in
#core
See all meetings →
Recent Posts and Comments
Team Pledges
2664 people
have pledged time to contribute to Core Team efforts! When looking for help on a project or program, try starting by reaching out to them!
compose new post
reply
edit
go to top
go to the next post or comment
go to the previous post or comment
toggle comment visibility
esc
cancel edit post or comment