Title: phase 3 – Make WordPress Core --- # Tag Archives: phase 3 [ ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/) 7:29 pm _on_ June 3, 2026 Tags: [7.1 ( 68 )](https://make.wordpress.org/core/tag/7-1/), [collaboration ( 4 )](https://make.wordpress.org/core/tag/collaboration/), [feature-real-time-collaboration ( 4 )](https://make.wordpress.org/core/tag/feature-real-time-collaboration/), [gutenberg ( 553 )](https://make.wordpress.org/core/tag/gutenberg/), phase 3    # 󠀁[Announcing a collaborative editing outreach effort for 7.1](https://make.wordpress.org/core/2026/06/03/announcing-a-collaborative-editing-outreach-effort-for-7-1/)󠁿 A new dedicated outreach effort is underway for WordPress 7.1 to ensure collaborative editing gets the collaborative testing it needs. Please join [#collaborative-editing-outreach](https://wordpress.slack.com/archives/C0B7W4UQFC2) in 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/)( [steps to sign up here](https://make.wordpress.org/chat/)) if you: * Want to use collaborative editing on a regular basis. * Enjoy being an early adopter. * Feel comfortable using the latest version of the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party.. * Have the ability to participate through the 7.1 cycle (at least until 8/18/26). Thanks in advance for helping shape the future of this feature. ## **Why now?** Collaborative features require an inherently collaborative way of testing. For the 7.0 cycle, a lot of time and effort was spent with more developer oriented testing, [enterprise level testing](https://make.wordpress.org/core/2025/12/16/real-time-collaboration-early-user-feedback/), and [deterministic testing with hosts](https://make.wordpress.org/hosting/2026/04/29/urgent-testing-request-to-web-hosts-for-collaborative-editing-by-may-4th/). While incredibly useful, this effort broadens the scope of testing by bringing in passionate real-world early adopters across a range of hosting environments and backgrounds. For collaborative editing to truly succeed, it’s important to go beyond just getting stability, performance, and reliability right. In running the FSE Outreach Program, I saw how powerful it was to have a dedicated space for folks to regularly interact with those building the feature for a faster feedback 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) in the right direction. After the hard decision was made to remove [collaborative editing from WordPress 7.0](https://make.wordpress.org/core/2026/05/08/rtc-removed-from-7-0/), the aim is that ahead of 7.1 the outreach program model provides enough structure to create meaningful feedback without being too overbearing or exclusive considering the timeframe. [This was first discussed in #feature-realtime-collaboration](https://wordpress.slack.com/archives/C07NVJ51X6K/p1779836917336809) before being brought to project leadership.  ## **Who can join?** Anyone is welcome to join [#collaborative-editing-outreach](https://wordpress.slack.com/archives/C0B7W4UQFC2)! Real Time Collaboration is included in the latest versions of Gutenberg, and can be enabled under `Settings > Writing` in the dashboard when the Gutenberg plugin is active. It’s critical people from across different hosting environments and use cases are a part of this, from nonprofits to small businesses to newsrooms. If you have a large need for collaborative editing, enjoy sharing feedback, and are comfortable with using the latest Gutenberg plugin, this is an awesome way to contribute to the WordPress project. Test team badges will be given out at the end.  ## **More about the effort** The aim is to engage passionate real-world early adopters across a spread of hosting environments in a dedicated slack channel throughout the release process to ensure a tight feedback loop for both bugs and feature requests. This will take a simple form: a dedicated slack channel ([#collaborative-editing-outreach](https://wordpress.slack.com/archives/C0B7W4UQFC2)) where folks can get set up with collaborative editing, share ongoing feedback, and those working on the feature can open bugs/make fixes/share improvements/etc. Compared to the FSE Outreach Program, there won’t be ongoing themed calls for testing since they would end up being very repetitive. Instead, key updates will be shared in the slack channel to help inform folks as new fixes or features are added to give feedback on them. The latest updates for collaborative editing will be delivered through the Gutenberg plugin which is why using the latest version is a requirement for this channel. [As discussed here](https://wordpress.slack.com/archives/C07NVJ51X6K/p1779824541339439), a featured plugin isn’t currently feasible.  Tied to this, outreach will be done to hosting companies to attempt to recruit participants for this outreach program. This is being done to help get as many different environments as possible represented.  Currently, [@amykamala](https://profiles.wordpress.org/amykamala/), [@greenshady](https://profiles.wordpress.org/greenshady/), and I will be acting as the small crew driving this forward in the slack channel, alongside the developers and designers working on this feature.  ## **Questions? Comments? Concerns?** Please leave them below. Thanks for engaging. _Thank you to [@amykamala](https://profiles.wordpress.org/amykamala/) [@greenshady](https://profiles.wordpress.org/greenshady/) [@maxschmeling](https://profiles.wordpress.org/maxschmeling/) for reviewing this post. _ [#7-1](https://make.wordpress.org/core/tag/7-1/), [#collaboration](https://make.wordpress.org/core/tag/collaboration/), [#feature-real-time-collaboration](https://make.wordpress.org/core/tag/feature-real-time-collaboration/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/), [#phase-3](https://make.wordpress.org/core/tag/phase-3/) [ ](https://profiles.wordpress.org/smithjw1/) [Jacob Smith](https://profiles.wordpress.org/smithjw1/) 4:56 pm _on_ December 16, 2025 Tags: [collaboration ( 4 )](https://make.wordpress.org/core/tag/collaboration/), phase 3    # 󠀁[Real-time collaboration: Early user feedback](https://make.wordpress.org/core/2025/12/16/real-time-collaboration-early-user-feedback/)󠁿 Real-time collaboration—the ability for multiple users to edit the same post simultaneously, similar to Google Docs—is being developed for [WordPress 7.0](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/), scheduled for release in 2026. Beginning in October 2025, [WordPress VIP](https://wpvip.com/) customers have had access to a betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. version of real-time collaboration to begin stress-testing the experience across different environments and use cases, informing the work as early as possible. The beta has provided valuable insights into how real-time collaboration performs with production WordPress sites and real editorial workflows. The response has been enthusiastic, with several organizations already enabling the feature in production. If you haven’t seen it already, here’s a demo of the feature in action. ## **About the research** This post summarizes feedback gathered from 45 beta participants between October and early December 2025. While the issues are being tracked individually under the [[Type] Real Time Collaboration](https://github.com/WordPress/gutenberg/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BFeature%5D%20Real-time%20Collaboration%22) label, this summary centralizes the information for easier review and broader transparency. The insights come from: * Direct conversations with technical leads and editorial teams at participating organizations. * Recorded testing sessions and demonstrations. * Written feedback submitted through beta feedback channels. * Observations of production and staging deployments. Participating organizations span industries including news and media, higher education, research institutions, and enterprise publishing; all are larger organizations with multi-person editorial teams. ## **Key insight: It just works with modern WordPress** The most consistent feedback: **real-time collaboration works seamlessly when sites are built for modern WordPress**. Organizations using the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor with native WordPress blocks and custom blocks developed using best practices reported smooth experiences with minimal issues. One technical lead at a major research institution noted their team has invested in a deep understanding 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/) and, as a result, “… have not run into any issues.” Their editorial team described the feature as delivering “an amazing workflow change,” eliminating the frustration of kicking colleagues out of posts to make quick edits. Multiple teams tested the limits by: * Adding dozens of blocks simultaneously. * Copying large amounts of existing content in parallel. * Having entire teams edit the same post together (one team specifically noted “ this is so fun”). In these stress tests with native blocks and modern custom blocks, real-time collaboration held up remarkably well. ## **Other insights** ### **The value of Notes** The newly released [Notes](https://make.wordpress.org/core/2025/11/15/notes-feature-in-wordpress-6-9/) feature generated significant enthusiasm.  One communications team called it “revolutionary.” Teams particularly value the ability to leave contextual feedback directly in the editor without disrupting the editorial flow.  This feedback confirms that collaborative editing is a suite of tools that make it easier for you to create in WordPress from your very first keystroke, not a single feature. ### **Flexible workflows** Different organizations expressed distinct preferences for how collaboration should work within their editorial processes: * **Some teams want flexibility**: Publishers aggregating content from distributed teams appreciate the ability for multiple editors to work simultaneously across different sections of a post. * **Others prefer predictability**: Organizations with established “check-in, check- out” workflows expressed interest in mode controls that would allow them to programmatically determine editing permissions based on user roles and post status.  One organization specifically noted their less technical users might feel “uncomfortable with the shift to a fully collaborative environment, fearing they might step on each other’s toes.” Teams want the ability to adapt the collaboration model to their existing editorial culture rather than completely restructuring workflows. ### **Attribution** Multiple organizations emphasized the need for better attribution tracking. Today, when a user saves a revision, you know they made all changes. With real-time collaboration, multiple users can make changes to the same version. Contributors are working to address this feedback by adding “contributor” metadata for versions. You can follow that work in this [GitHub issue](https://github.com/WordPress/gutenberg/issues/73943). ### **Where things go wrong** The most significant compatibility issues emerged with **blocks storing data in post metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. rather than block attributes**, particularly when that post meta isn’t updated using modern methods. Real-time collaboration works with any post meta that is [registered](https://developer.wordpress.org/reference/functions/register_post_meta/) with `show_in_rest` set to true. Metadata registered this way will participate in the data store that powers real-time collaboration. Legacy metaboxes update meta using other means. This will be an important area to address for WordPress 7.0. 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. authors will want to know what work, if any, is required to ensure their code supports real-time collaboration. ### **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)** The current beta does not meet the accessibility standards expected for WordPress. Providing functional affordances in a real-time environment is challenging, but it is a challenge to be met. This is an area where help is needed from the Accessibility team. You can report any accessibility issues you encounter on this [GitHub tracking issue](https://github.com/WordPress/gutenberg/issues/73942). ## **Going forward** Experimental work in Gutenberg is tracked in a [branch](https://github.com/WordPress/gutenberg/tree/wpvip/rtc-plugin), and it is also being merged upstream to provide [undo support](https://github.com/WordPress/gutenberg/pull/72407) and [post meta syncing](https://github.com/WordPress/gutenberg/pull/72332). If you want to test the beta for real-time collaboration today, you can follow the instructions in this [GitHub repository](https://github.com/Automattic/vip-real-time-collaboration) to set up an environment. You can test locally by editing content in two different browser windows.  Stay tuned for broader dedicated calls for testing and more summaries like this. The aim now is to get everything into Gutenberg trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. to make it easier for more testing in different environments. If you have feedback or questions, please comment here. Issues can be added with the `[Feature] Real-time Collaboration` label [on GitHub](https://github.com/WordPress/gutenberg/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BFeature%5D%20Real-time%20Collaboration%22). Props to [@annezazu](https://profiles.wordpress.org/annezazu/) for reviewing this post. [#collaboration](https://make.wordpress.org/core/tag/collaboration/), [#phase-3](https://make.wordpress.org/core/tag/phase-3/) [ ](https://profiles.wordpress.org/matveb/) [Matias Ventura](https://profiles.wordpress.org/matveb/) 4:44 pm _on_ December 11, 2025 Tags: [7.0 ( 76 )](https://make.wordpress.org/core/tag/7-0/), phase 3    # 󠀁[Planning for 7.0](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/)󠁿 With 6.9 [out in the world](https://wordpress.org/download/releases/6-9/), our collective attention has already turned to 7.0. 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), 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. GitHubGitHub 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. [https://github.com/](https://github.com/) and TracTrac 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 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/) or trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.. **Table of Contents** * [Collaboration ](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#collaboration) * [Admin](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#admin) * [APIs](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#apis) * [Navigation Block](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#navigation-block) * [Customization](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#customization) * [Blocks](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#blocks) * [Media](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#media) ## 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](https://github.com/WordPress/gutenberg/issues/52593) * Key considerations: - There’s been a lot of progress in defining the UIUI 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](https://profiles.wordpress.org/acicovic/), [@aduth](https://profiles.wordpress.org/aduth/), [@alecgeatches](https://profiles.wordpress.org/alecgeatches/), [@czarate](https://profiles.wordpress.org/czarate/), [@ingeniumed](https://profiles.wordpress.org/ingeniumed/), [@jsnajdr](https://profiles.wordpress.org/jsnajdr/),@ maxschmelingkc, [@paulkevan](https://profiles.wordpress.org/paulkevan/), [@shekharnwagh](https://profiles.wordpress.org/shekharnwagh/), [@youknowriad](https://profiles.wordpress.org/youknowriad/) **Notes i2** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73260) * Key considerations: - Support partial selection inside 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. 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 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. for recent notes. - More notification options (responses, follow a note, mentions). * Contributors: [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/), [@jeffpaul](https://profiles.wordpress.org/jeffpaul/), [@mamaduka](https://profiles.wordpress.org/mamaduka/) --- ## Adminadmin (and super admin) **Improving screens across wp-admin** * Link: TBD * Key considerations: - [Explore CSS improvements](https://core.trac.wordpress.org/ticket/64308) 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](https://profiles.wordpress.org/fabiankaegy/), [@karmatosed](https://profiles.wordpress.org/karmatosed/), [@mcsf](https://profiles.wordpress.org/mcsf/) **DataViews and DataForms iterations** * Link: [7.0 iteration issue](https://github.com/WordPress/gutenberg/issues/73076) * Key considerations: - DataForms/QuickEdit/Document inspector design iterations. - Hierarchical post visualization. - Make DataViews screens extensibleExtensible 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](https://profiles.wordpress.org/oandregal/) **Design System** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/71196) * 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](https://profiles.wordpress.org/0mirka00/), [@aduth](https://profiles.wordpress.org/aduth/), [@jsnajdr](https://profiles.wordpress.org/jsnajdr/), [@mciampini](https://profiles.wordpress.org/mciampini/), [@wildworks](https://profiles.wordpress.org/wildworks/) **Font library admin section** * Link: [Github issue](https://github.com/WordPress/gutenberg/issues/57904) * Key considerations: - **✅ **Support for block themes. - Support for hybrid/classic themes. * Contributors: [@youknowriad](https://profiles.wordpress.org/youknowriad/) **RevisionsRevisions 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](https://github.com/WordPress/gutenberg/issues/52138) * 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](https://profiles.wordpress.org/adamsilverstein/) **Customizable Keyboard Shortcuts** * Link: [Github issue](https://github.com/WordPress/gutenberg/issues/3218) * Key considerations: - Build with design system components. * Contributors: TBD --- ## APIs **Abilities & Workflows 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.** * Link: [Github issue](https://github.com/WordPress/gutenberg/issues/70710) * 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](https://github.com/WordPress/ai/issues/40). - Command palette and UI: * Differentiation between commands. * Ability to support two stages of a command. * Contributors: [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) [@gziolo](https://profiles.wordpress.org/gziolo/) [@senadir](https://profiles.wordpress.org/senadir/) [@youknowriad](https://profiles.wordpress.org/youknowriad/) **Upgrade to 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/) 19** * Link: [Github issue](https://github.com/WordPress/gutenberg/issues/71336) * Key considerations: - There’s a path for the block editor in the mobile apps that should remove this dependency blockerblocker A bug which is so severe that it blocks a release.. - Ecosystem impact. * Contributors: [@aduth](https://profiles.wordpress.org/aduth/) [@jsnajdr](https://profiles.wordpress.org/jsnajdr/) [@mamaduka](https://profiles.wordpress.org/mamaduka/) [@ralucastn](https://profiles.wordpress.org/ralucastn/) [@tyxla](https://profiles.wordpress.org/tyxla/) **Block API: Add validation levels** * Links: [Github issue](https://github.com/WordPress/gutenberg/issues/21703) with [initial PR** **](https://github.com/WordPress/gutenberg/pull/73116) * 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](https://profiles.wordpress.org/matveb/) [@mcsf](https://profiles.wordpress.org/mcsf/) [@youknowriad](https://profiles.wordpress.org/youknowriad/) **Enforced iframed editor** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73138). - Backwards compatibility, extended testing. - **✅ **MigrationMigration 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](https://profiles.wordpress.org/ellatrix/), [@wildworks](https://profiles.wordpress.org/wildworks/) **WP client AI API** * Link: [GitHub project](https://github.com/WordPress/wp-ai-client) * Key considerations: - An AI client and API for WordPress to communicate with any generative AI models of various capabilitiescapability A **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 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. - Decide nomenclature. - Ideally, the minimum PHPPHP 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](https://profiles.wordpress.org/flixos90/) [@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/) **Creating blocks and patterns on the server** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/71792) * 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](https://profiles.wordpress.org/priethor/), TBD **wordpress/build and routing (site editor)** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/70862); [Scripts issue](https://github.com/WordPress/gutenberg/issues/72032) * Key considerations. - Add extensibility to site editor routing. - Dependency on standalone font library. - Refactor the site editor to allow 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. authors to add their pages there. - **✅ **Opinionated build tool for plugins. - Update Gutenberg – Core backportbackport 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](https://profiles.wordpress.org/youknowriad/)  **Shortblocks** * Links: [Bits as dynamic tokens](https://make.wordpress.org/core/2024/06/08/proposal-bits-as-dynamic-tokens/); [Bits: Introduce the ability to store and render bits](https://github.com/WordPress/wordpress-develop/pull/6390), [Rich text: try BITS with block binding API](https://github.com/WordPress/gutenberg/pull/60735), [Introduce parser for dynamic token system](https://github.com/WordPress/gutenberg/pull/42015). * 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](https://profiles.wordpress.org/dmsnell/), [@ellatrix](https://profiles.wordpress.org/ellatrix/), [@jonsurrell](https://profiles.wordpress.org/jonsurrell/) **Block bindings iterations** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73467) * Key considerations: - [Open up “Pattern Overrides” and therefore intern block bindings to custom dynamic blocks](https://href.li/?https://github.com/WordPress/gutenberg/issues/64870). - [Filter available source items for a given attribute by format](https://href.li/?https://github.com/WordPress/gutenberg/issues/72446). - Align with Fields API as a requirement.  * Contributors: [@bernhard-reiter](https://profiles.wordpress.org/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](https://github.com/WordPress/gutenberg/issues/65699) * Key considerations: - [Better insertion](https://github.com/WordPress/gutenberg/issues/73647). - [Pattern editing and ContentOnly interactivity](https://github.com/WordPress/gutenberg/issues/71517). - Better presentation of “bound” page items. * Contributors: [@get_dave](https://profiles.wordpress.org/get_dave/), [@jeryj](https://profiles.wordpress.org/jeryj/) **Ability to customise “mobile” overlay ** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73084) * Key considerations: - Implemented as a template part. - Ability to customize when the overlay appears (breakpoint settings) just for navigation overlay. * Contributors: [@get_dave](https://profiles.wordpress.org/get_dave/), [@jeryj](https://profiles.wordpress.org/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](https://github.com/WordPress/gutenberg/pull/73631). - 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](https://github.com/WordPress/gutenberg/pull/73628). * Contributors: [@ellatrix](https://profiles.wordpress.org/ellatrix/) **Pattern Editing (aka ContentOnly)** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/71517) * Key considerations: - Ensure proper discoverability to enter/exit. - Ensure it works well with synced patterns.  * Contributors: [@aaronrobertshaw](https://profiles.wordpress.org/aaronrobertshaw/), [@andrewserong](https://profiles.wordpress.org/andrewserong/), [@isabel_brison](https://profiles.wordpress.org/isabel_brison/), [@ramonopoly](https://profiles.wordpress.org/ramonopoly/) [@talldanwp](https://profiles.wordpress.org/talldanwp/). **Improve template management** * Link: [GitHub PR](https://github.com/WordPress/gutenberg/pull/67125) * Key considerations: - Direction and UXUX User experience is still TBD and needs more exploration. - [Retain access to template parts across theme switches](https://github.com/WordPress/gutenberg/issues/72452). * Contributors: [@ellatrix](https://profiles.wordpress.org/ellatrix/) [@scruffian](https://profiles.wordpress.org/scruffian/). **Responsive editing mode** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/19909) * Key considerations: - Toggle to engage responsive editing mode. - Block visibility i2: [add ability to hide blocks based on screen size](https://github.com/WordPress/gutenberg/issues/72502). - Allow style changes to be saved and retrieved for different breakpoints. - Allow customization of hardcoded breakpoints. * Contributors: [@matveb](https://profiles.wordpress.org/matveb/) [@ramonopoly](https://profiles.wordpress.org/ramonopoly/) **Block supports and design tools:  ** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73772) * Key considerations: - Add text line indent support. [GitHub PR](https://github.com/WordPress/gutenberg/pull/73114). - Add [gradient support to text color options](https://github.com/WordPress/gutenberg/issues/30982). - [Add height block support to dimension ](https://github.com/WordPress/gutenberg/pull/71914). - Styles support for text shadow. [GitHub PR](https://github.com/WordPress/gutenberg/pull/73320). - Support for text alignment [with justify support](https://github.com/WordPress/gutenberg/issues/50319). - [Allow Video backgrounds to be ‘Fixed’](https://github.com/WordPress/gutenberg/issues/52585). - [Balanced line wrap](https://github.com/WordPress/gutenberg/issues/52387). - Text columns. [GitHub issue](https://github.com/WordPress/gutenberg/issues/27118); [GitHub issue](https://github.com/WordPress/gutenberg/issues/25459). - Support aspect ratio [on wide and full images](https://github.com/WordPress/gutenberg/issues/53652). * Contributors: TBD, [@aaronrobertshaw](https://profiles.wordpress.org/aaronrobertshaw/) [@matveb](https://profiles.wordpress.org/matveb/) [@youknowriad](https://profiles.wordpress.org/youknowriad/) [@wildworks](https://profiles.wordpress.org/wildworks/) --- ## Blocks Keeping the momentum [on adding new blocks](https://github.com/WordPress/gutenberg/issues/71026) 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](https://github.com/WordPress/gutenberg/issues/73845) * 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](https://github.com/WordPress/gutenberg/issues/28860); [GitHub PR](https://github.com/WordPress/gutenberg/pull/73023) * Contributors: [@matveb](https://profiles.wordpress.org/matveb/)  **Modernize Code editor + Code block** * Link: [GitHub link](https://github.com/WordPress/gutenberg/issues/10423) * Contributors: [@jonsurrell](https://profiles.wordpress.org/jonsurrell/), [@westonruter](https://profiles.wordpress.org/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](https://github.com/WordPress/gutenberg/pull/70603#top) in this work too. * Contributors: [@tyxla](https://profiles.wordpress.org/tyxla/) **Leverage iAPI for instant search block & submit comments without full page refresh** * Links: [Instant Search](https://href.li/?https://github.com/WordPress/gutenberg/pull/67181), [submit comments without requiring a full-page refresh](https://href.li/?https://github.com/WordPress/gutenberg/pull/53737). * Contributors: TBD **Writing flow + drag and drop improvements** * Link: [GitHub issue](https://href.li/?https://github.com/WordPress/gutenberg/issues/63255) * 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](https://github.com/WordPress/gutenberg/issues/73581) and inline images. * Contributors: [@ellatrix](https://profiles.wordpress.org/ellatrix/) **✅ Tabs block ** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73230) * Contributors: [@mikachan](https://profiles.wordpress.org/mikachan/) **Release the Table of Contents block ** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/42229) * Contributors: TBD  **Playlist block** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/805) * Contributors: [@scruffian](https://profiles.wordpress.org/scruffian/) **Slider block** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/43369), [GitHub issue](https://github.com/WordPress/gutenberg/issues/25501), [GitHub issue](https://github.com/WordPress/gutenberg/issues/25502) * Contributors: [@lstraczynski](https://profiles.wordpress.org/lstraczynski/), [@karolmanijak](https://profiles.wordpress.org/karolmanijak/) **Dialog block** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/pull/71618) * Contributors: TBD **✅ Breadcrumb block** * Link: [GitHub Issue](https://github.com/WordPress/gutenberg/issues/72498) * Team: [@ntsekouras](https://profiles.wordpress.org/ntsekouras/) **Add more dynamic URLs via block bindings to Buttons block and Image block** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/18345#issuecomment-3400461363), [API shape](https://github.com/WordPress/gutenberg/issues/72426) * Team: TBD **Icon block** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/16484) * Key considerations: - Ship with a default set made out of some wordpress/icons. - Allow extenders to register their own sets. * Contributors: [@mcsf](https://profiles.wordpress.org/mcsf/) [@welcher](https://profiles.wordpress.org/welcher/) **Gallery block: add lightbox support with the ability to switch between images** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/56310), [GitHub PR](https://github.com/WordPress/gutenberg/pull/62906#issuecomment-3535417814) * Contributor: [@wildworks](https://profiles.wordpress.org/wildworks/) **Introduce heading levels as Heading block variations** * Link: [Github issue](https://github.com/WordPress/gutenberg/issues/42181); [https://github.com/WordPress/gutenberg/issues/42181](https://github.com/WordPress/gutenberg/issues/42181) * Key considerations: - Show up in search and slash inserter. - Easy toggling in 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. inspector and transforms. * Contributor: [@matveb](https://profiles.wordpress.org/matveb/) **Aim to stabilize grid block** * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73773) * Contributor: [@isabel_brison](https://profiles.wordpress.org/isabel_brison/) --- ## Media **Client side media work** * Link: [GitHub issue ](https://github.com/WordPress/gutenberg/issues/61447) * Contributors: [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/), [@ramonopoly](https://profiles.wordpress.org/ramonopoly/) **Media editor** * Link: [Iteration issue](https://github.com/WordPress/gutenberg/issues/73771) * Contributors: [@aaronrobertshaw](https://profiles.wordpress.org/aaronrobertshaw/), [@andrewserong](https://profiles.wordpress.org/andrewserong/), [@isabel_brison](https://profiles.wordpress.org/isabel_brison/), [@ramonopoly](https://profiles.wordpress.org/ramonopoly/), [@talldanwp](https://profiles.wordpress.org/talldanwp/) --- Designers looking across all these projects: [@fcoveram](https://profiles.wordpress.org/fcoveram/), [@joen](https://profiles.wordpress.org/joen/), [@jameskoster](https://profiles.wordpress.org/jameskoster/), [@mattmiklic](https://profiles.wordpress.org/mattmiklic/). [#7-0](https://make.wordpress.org/core/tag/7-0/), [#phase-3](https://make.wordpress.org/core/tag/phase-3/) [ ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/) 3:15 am _on_ November 6, 2025 Tags: [gutenberg ( 553 )](https://make.wordpress.org/core/tag/gutenberg/), phase 3    # 󠀁[Update on Phase 3: Collaboration efforts (Nov 2025)](https://make.wordpress.org/core/2025/11/06/update-on-phase-3-2025/)󠁿 [After last year’s update](https://make.wordpress.org/core/2024/11/21/update-on-phase-3-collaboration-efforts/), this post seeks to summarize what’s been completed, what’s in progress, and how to follow along or contribute. This post also seeks to set expectations going forward and answer reoccurring questions at a high level. As a reminder [Phase 3 is centered around](https://make.wordpress.org/core/2023/03/24/phase-3-collaboration/) fostering seamless collaboration, tying together the user experience, and streamlining the content management flows to improve the way creators and teams work together within WordPress. As work progresses, feedback is needed and welcomed to ensure broader adoption. [[ A design concept for real time collaboration with notes. ### Real-time collaboration Work is underway to expand the collaborative editing experiment, with the [latest update](https://github.com/WordPress/gutenberg/issues/52593#issuecomment-3424271929) highlighting key areas in progress: * Performant and stable synchronization. * Protections to make sure that the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-data package retains control over which entity records are synced and how changes are merged. * A filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks). They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to give plugins the ability to extend a SyncProvider class. This allows plugins to provide their own [sync transports](https://docs.yjs.dev/ecosystem/connection-provider) and to implement user-facing sync behaviors such as awareness / presence indicators. * Stubs (lightweight placeholder records) that allow CRDT docs to be persisted in metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress., avoiding [the “initialization problem”](https://github.com/dmonad/gutenberg/blob/93db3f63a525e0684ae3c330547c33b3324ec0c1/packages/sync/CODE.md#the-initialization-problem) as described by Kevin Jahns. * A Yjs-powered UndoManager that works across multiple synced entities. WordPress VIP has developed a [working implementation](https://github.com/Automattic/vip-real-time-collaboration) demonstrating these capabilitiescapability A **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)., and various contributors are working to bring functionality into Core via 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/). All of this work is being done to pave the way for possible inclusion in WordPress 7.0. For now, if you want to help test and give feedback, you can do so by using the latest Gutenberg pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. and enabling the “Collaboration: add real-time editing” experiment in Gutenberg > Experiments. Keep in mind that a [PR is not yet merged to remove the post lock modal](https://github.com/WordPress/gutenberg/pull/72326) but, until it is, you can still test having two sessions and see changes behind the modal itself.  _Follow along in _[_this dedicated GitHub issue_](https://github.com/WordPress/gutenberg/issues/52593)_ and/or in the _[_#feature-realtime-collaboration_](https://wordpress.slack.com/archives/C07NVJ51X6K)_ 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/) channel._ ### Async collaboration: Notes Formerly known as 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. Comments, [the Notes feature is set to debut in WordPress 6.9](https://github.com/WordPress/gutenberg/issues/66377), bringing block-level Notes to Core after first appearing in the Gutenberg plugin as an experimental feature in October of last year. With this initial release, you’ll be able to add/resolve/delete/thread notes on entire blocks but not yet on specific elements within a block. The name Notes was chosen to clearly distinguish it from WordPress’s existing comment functionality, making it easier to discuss and document the feature moving forward. It also provides flexibility for future expansions beyond block-level notes, without needing another rename. This was truly a collaborative effort to land this feature with various folks from across the community coming together from Fueled, Multidots, Automattic, GoDaddy, and Human Made contributing as well as individuals like Adam Silverstein and Aki Hamano. Feedback as the feature lands in Core will help shape what’s next here so please help test and [open issues](https://github.com/WordPress/gutenberg/issues). For now, initial future plans include compatibility with real time collaboration, the ability to leave notes on individual items within a block rather than just at the block level, and built-in notifications.  _Follow along in _[_this dedicated GitHub issue_](https://github.com/WordPress/gutenberg/issues/59445)_._ ### Adminadmin (and super admin) redesign: DataView & DataForm Early exploration centers on defining foundational primitives with DataView and DataForm components, building blocks that separate structure from presentation to support broad reusability across admin surfaces. Work has continued on both of these components to make them strong foundations that can handle more use cases with 154 commits done by ~37 different authors just for this latest release. [For WordPress 6.9](https://github.com/WordPress/gutenberg/issues/70936), this includes access to new field types, expanded filtering options, grouping support, views persistence, and improved configuration for custom dashboards and workflows. As a reminder, both of these components have been created with extensibility at the heart of everything being built. You can view each in their respective Storybook views: [DataViews](https://wordpress.github.io/gutenberg/?path=/docs/dataviews-dataviews--docs) and [DataForm](https://wordpress.github.io/gutenberg/?path=/docs/dataviews-dataform--docs). You can also read a more granular overview of what’s landed in [this iteration issue for 6.9](https://github.com/WordPress/gutenberg/issues/70936). For now, if you want to help test and give feedback, you can do so by using the existing Pages, Templates, and Patterns screens in the Site Editor. For some of the more experimental aspects, you can help test by using the latest Gutenberg plugin and enabling from the Gutenberg > Experiments page the following different experiments: * Data Views: add Quick Edit – this adds a Quick Edit panel in the Site Editor Pages experience. * Data Views: enable for Posts – this adds a redesigned Posts dashboard accessible through a submenu item in the Gutenberg plugin so you can still have access to your current Posts experience.  Below is a demo of this last experiment that enables Data Views for Posts. It also showcases a feature of WordPress 6.9 with data views options now persisting across sessions, until you hit reset view. _Follow along in this dedicated [Admin Materials and Surfaces](https://github.com/WordPress/gutenberg/issues/70913#top) issue._ [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/), [#phase-3](https://make.wordpress.org/core/tag/phase-3/) [ ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/) 4:36 pm _on_ January 7, 2025 Tags: [gutenberg ( 553 )](https://make.wordpress.org/core/tag/gutenberg/), [hallway-hangout ( 19 )](https://make.wordpress.org/core/tag/hallway-hangout/), phase 3    # 󠀁[Reliable Sync Protocol PR: Live Demo & Discussion for Collaborative Editing](https://make.wordpress.org/core/2025/01/07/reliable-sync-protocol-pr-live-demo-discussion-for-collaborative-editing/)󠁿 On January 6th at 7PM UTC, a group gathered for a demo and discussion with Kevin Jahns, the author of Yjs, a popular framework for building collaborative applications. In this session, we went in depth on an [in progress pull request that implements a reliable sync protocol for collaborative editing](https://github.com/WordPress/gutenberg/pull/68483). We also all collaborated on a post live as a fun way to test limits! Thank you to all who joined and for Kevin for hosting. To follow future efforts in this space, please follow [this dedicated GitHub issue](https://github.com/WordPress/gutenberg/issues/52593) and/or join the [#feature-realtime-collaboration](https://wordpress.slack.com/archives/C07NVJ51X6K) 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/) channel. ## Recording ## Notes Notes are mainly powered by an AI note taker so please leave a comment if anything feels wildly off. **Overview** Kevin Jahns presented a demonstration on utilizing Yjs to enhance real-time editing capabilitiescapability A **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). in WordPress, addressing existing challenges such as content synchronization and potential conflicts during simultaneous edits. He introduced features like automatic 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_. resolution and a heartbeat 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. for near real-time updates, emphasizing that while the current implementation may not fully replicate the Google Docs experience, it significantly improves user trust and collaboration. Participants were encouraged to explore Yjs further and consider its applications in their projects. Jahns discussed the technical obstacles in implementing collaborative editing, particularly the lack of WebSocket support across various PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher engines and the limitations of WebRTC, which requires multiple servers for reliable operation. He proposed using HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. requests for syncing while allowing WebRTC as an optional enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature.. Additionally, he highlighted issues with 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. validation errors and synchronization challenges with custom block types in the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) editor, suggesting the creation of a special editor binding for Yjs to improve synchronization. Security concerns regarding the WebRTC setup were also raised, with a focus on the need for role-based collaboration restrictions to prevent document manipulation. The session also covered the storage and management of Yjs documents, with Jahns explaining that Yjs content is stored as comments in post content, facilitating straightforward revision creation. He acknowledged the challenges of managing real- time changes and the impact of Yjs documents on content size. Discussions included the limitations of WebRTC, particularly its reliance on costly TURN servers, and the need for ongoing testing to ensure the reliability of collaborative editing features. Jahns emphasized the importance of prioritizing collaborative editing to enhance the editor’s evolution and received appreciation for his transparency and commitment to the Gutenberg project. **Real-Time Editing Demo with Yjs** Kevin Jahns presented a demo on real-time editing with Yjs, emphasizing its role in enhancing collaborative features in WordPress. He explained the limitations of the current WordPress editor regarding content synchronization and introduced new features like automatic conflict resolution and the heartbeat API for better real-time collaboration. **Collaborative Editing in WordPress** Kevin Jahns addressed the difficulties of enabling collaborative editing in WordPress, noting that WebSockets are not universally supported across PHP engines. He explained that while WebRTC could be used as a fallback, it is not reliable enough for all users. Instead, he proposed using HTTP requests for syncing, with WebRTC as a progressive enhancement for those who can utilize it. **Block Synchronization and Customization Challenges** Kevin Jahns addressed synchronization issues with block types (and ran into an error with block validation in the process!). He explained that while standard elements like text and images function properly, custom block types may encounter difficulties due to Gutenberg’s design, which does not fully accommodate changes from multiple peers. Jahns emphasized the need for a special editor binding for Yjs to enhance synchronization. **Discussion on Signaling Server and Security Concerns** Kevin Jahns confirmed that Jorge’s signaling server implementation in WordPress remains unchanged. He raised security concerns regarding the WebRTC setup, highlighting that it permits document manipulation by anyone with read access. Jorge noted that to make the system production- ready, several security measures need to be implemented, particularly around user roles and collaboration. **Yjs Document Storage and Revision Management** Kevin Jahns responded to Frank’s inquiry about the Yjs implementation and its impact on content revisionsRevisions 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.. He detailed that Yjs documents are stored as comments within the post content, which facilitates the creation of revisions upon saving. Additionally, he mentioned that future comparisons of revisions could be made using Yjs documents, similar to a git diff, and that attribution for content creation is also supported. **Discussion on Yjs Document Implementation and Security Concerns** Kevin Jahns highlighted the downside of Yjs documents inflating content size but reassured that normal users wouldn’t see the comments. Aaron Jorbin pointed out the security implications of allowing users to input unfiltered HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers.. Kevin also mentioned the potential for filtering user visibility of Yjs comments and the need to track edits made by users, which currently lacks a backend solution. **WebRTC vs. WebSocket for Collaborative Editing in WordPress** Kevin Jahns explained that WebRTC is not a reliable option for collaborative editing in WordPress due to its dependency on multiple servers and potential blocking by companies. He suggested using HTTP requests as a baseline for collaboration, which provides a satisfactory experience for most users. For those needing more reliability, he mentioned the possibility of implementing WebSocket servers, which could also enhance security and authentication. **Discussion on WebRTC and TURN Servers** Kevin Jahns highlighted the overhead of WebRTC and the expense of hosting TURN servers, indicating that they are not a viable option for everyone. Jorge shared his thoughts about the reliability of TURN servers from providers like Google and Twilio. They noted that while STUN servers are affordable and public, TURN servers are costly and can lead to misuse. **Collaborative Editing and Yjs Integration** Kevin Jahns highlighted the challenges faced with collaborative editing in the current editor setup, particularly issues with image handling and the undo-redo functionality. He stressed the necessity of prioritizing collaborative editing and proposed using Yjs as a solution to enhance these features. Kevin also mentioned that recent updates to Gutenberg have caused disruptions, indicating a need for better testing and support. **Yjs Integration and Block Syncing Challenges** Kevin Jahns explained the process of syncing textual content through 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., noting that changes in one block can overwrite changes in another. He acknowledged existing issues with tables and galleries, indicating that these would be addressed in future pull requests. Kevin also highlighted the importance of creating a robust integration with Yjs for better collaboration. [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/), [#hallway-hangout](https://make.wordpress.org/core/tag/hallway-hangout/), [#phase-3](https://make.wordpress.org/core/tag/phase-3/) [ ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/) 9:36 pm _on_ November 21, 2024 Tags: [gutenberg ( 553 )](https://make.wordpress.org/core/tag/gutenberg/), phase 3    # 󠀁[Update on Phase 3: Collaboration efforts](https://make.wordpress.org/core/2024/11/21/update-on-phase-3-collaboration-efforts/)󠁿 Over the last year, Phase 3 of the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) roadmap has begun to take form and with it comes a need for an update around what’s been done, how to follow along, and what to expect going forward. This post seeks to provide answers at a high level view of these questions. As a reminder [Phase 3 is centered around](https://make.wordpress.org/core/2023/03/24/phase-3-collaboration/) fostering seamless collaboration, tying together the user experience, and streamlining the content management flows to improve the way creators and teams work together within WordPress. As work progresses, feedback is needed and welcomed to ensure broader adoption. ### **Real-time collaboration** Over the last few months, Kevin Jahns, the author of Yjs, a popular framework for building collaborative applications has been sponsored by Automattic to work on real-time collaboration, after an initial experiment landed. He kicked off his efforts with some research and dialogue in [this discussion issue](https://github.com/WordPress/gutenberg/discussions/65012). More recently, he’s pulled together some prototypes ahead of sharing a full proposal for how to proceed. Right now, consider this work as being in a strong experimental stage without a final approach. The next step is to get the initial approach into a PR for folks to give feedback on and discuss openly.  Below is a demo showing syncing content only relying on HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. APIs with the autosave interval set to 3 seconds. Because it relies on HTTP APIs, this demo would work on all WordPress instances: Going a step further, [you can see more demos in a recent update](https://github.com/WordPress/gutenberg/discussions/65012#discussioncomment-11075617) including adding y-webrtc into the experience to show how real time collaboration would work for users who can establish a peer-to-peer WebRTC connection. _Follow along in _[_this dedicated GitHub issue_](https://github.com/WordPress/gutenberg/issues/52593)_ and/or in the _[_#feature-realtime-collaboration_](https://wordpress.slack.com/archives/C07NVJ51X6K)_ 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/) channel._ ### **Async collaboration: In-line comments** An initial experiment for [block-level inline comments landed with Gutenberg 19.6](https://github.com/WordPress/gutenberg/pull/60622), breaking ground on the first of many async collaboration upgrades. At this point, another iteration on this initial feature is [already planned and underway](https://github.com/WordPress/gutenberg/issues/66377) to refine the current experience further. If you’d like to help test and shape the feature further, stay tuned for a dedicated call for testing or start testing today with [this WordPress Playground instance](https://playground.wordpress.net/#%7B%20%22plugins%22:%20%5B%20%22gutenberg%22%20%5D,%20%22steps%22:%20%5B%20%7B%20%22step%22:%20%22runPHP%22,%20%22code%22:%20%22%3C?php%20require%20'/wordpress/wp-load.php';%20update_option(%20'gutenberg-experiments',%20array(%20'gutenberg-block-comment'%20=%3E%20true%20)%20);%22%20%7D%20%5D,%20%22preferredVersions%22:%20%7B%20%22php%22:%20%228.0%22,%20%22wp%22:%20%22latest%22%20%7D,%20%22features%22:%20%7B%7D,%20%22login%22:%20true%20%7D) and [open issues](https://github.com/WordPress/gutenberg/issues) in the Gutenberg GitHubGitHub 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. [https://github.com/](https://github.com/) repository. The aim is to get early feedback and quickly iterate in order to land this new feature in an upcoming major WordPress release. Below is a look at the near term design slated to be shipped next with visuals for adding a comment, leaving a comment, toggling to see resolved comments, and the resulting view when looking at resolved comments: [⌊The post editor open to a paragraph block selected and the "more" menu open. The" Add comment" option is highlighted as if to select it and a few comments are visible in the right sidebar. ⌉⌊The post editor open to a paragraph block selected and the" more" menu open. The "Add comment" option is highlighted as if to select it and a few comments are visible in the right sidebar. ⌉[ [⌊The post editor open to a paragraph block selected and an in progress comment being written in the right sidebar. Other comments are visible. ⌉⌊The post editor open to a paragraph block selected and an in progress comment being written in the right sidebar. Other comments are visible. ⌉[ [⌊The post editor open to a paragraph block selected and the right sidebar visible showing a comments section with a toggle open to select "Show resolved" or "Show mine". Show resolved is highlighted. ⌉⌊The post editor open to a paragraph block selected and the right sidebar visible showing a comments section with a toggle open to select "Show resolved" or "Show mine". Show resolved is highlighted. ⌉[ [⌊The post editor open to a paragraph block selected and the right sidebar visible showing a comments section with a toggle open to select "Show resolved" or "Show mine". Show resolved is selected and some greyed out resolved comments are visible.⌉⌊ The post editor open to a paragraph block selected and the right sidebar visible showing a comments section with a toggle open to select "Show resolved" or "Show mine". Show resolved is selected and some greyed out resolved comments are visible. ⌉[ _Follow along in _[_this dedicated GitHub issue_](https://github.com/WordPress/gutenberg/issues/66377). ### **Adminadmin (and super admin) redesign: DataView & DataForm** DataViews is the foundational component of the initial [overall admin design efforts](https://make.wordpress.org/core/2023/07/12/admin-design/). By design, these views are being built out only in the Site Editor, with a few efforts branching out including an experiment for a [new, separate Posts experience using Data Views](https://github.com/WordPress/gutenberg/pull/62705) and an early [Media Library powered by Data Views proof of concept.](https://github.com/WordPress/gutenberg/pull/53788) As a next step of the initial development of DataViews, the more recent [DataForm API](https://github.com/WordPress/gutenberg/pull/63032) was later introduced in Gutenberg 18.8 with the aim to reduce expected duplication to create forms in Data Views. Work has continued progressively from there with DataViews and DataForm components influencing each other’s development. You can view each in their respective Storybook views: [DataViews](https://wordpress.github.io/gutenberg/?path=/docs/dataviews-dataviews--docs) and [DataForm](https://wordpress.github.io/gutenberg/?path=/docs/dataviews-dataform--docs). Both of these components have been created with extensibility at the heart of everything being built! For now, 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. and agency developers can already start using the DataViews component for their WordPress customizations with two different Developer Blogblog (versus network, site) tutorials to get you started: [Using Data Views to display and interact with data in plugins](https://developer.wordpress.org/news/2024/08/27/using-data-views-to-display-and-interact-with-data-in-plugins/) and [Actions from Data Views: Adding images to the Media Library](https://developer.wordpress.org/news/2024/09/23/actions-from-data-views-adding-images-to-the-media-library/). If you want to go on a deeper dive, [watch a recent hallway hangout](https://make.wordpress.org/core/2024/10/30/recap-hallway-hangout-dataviews-and-dataform-components/) that goes through both of these components with folks actively working on them. Expect a continual focus on extensibility as these components evolve. Below is a look at how DataViews comes together with the DataForm work with an easy option to quick edit within one’s pages: _Follow along in this dedicated _[_DataViews component issue_](https://github.com/WordPress/gutenberg/issues/55083)_ and this _[_DataForm component issue_](https://github.com/WordPress/gutenberg/issues/59745)_. For early design work in this area and beyond, check out the _[_biweekly design updates_](https://make.wordpress.org/design/tag/design-share/)_._ --- _Thanks to [@priethor](https://profiles.wordpress.org/priethor/) [@youknowriad](https://profiles.wordpress.org/youknowriad/) [@4thhubbard](https://profiles.wordpress.org/4thhubbard/) [@matveb](https://profiles.wordpress.org/matveb/) for reviewing this post and for [@joen](https://profiles.wordpress.org/joen/) and [@jameskoster](https://profiles.wordpress.org/jameskoster/) for the design assets_. [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/), [#phase-3](https://make.wordpress.org/core/tag/phase-3/) [ ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/) 7:46 pm _on_ June 13, 2024 Tags: [gutenberg ( 553 )](https://make.wordpress.org/core/tag/gutenberg/), phase 3, [plugins ( 33 )](https://make.wordpress.org/core/tag/plugins/)    # 󠀁[Data Views Update – June 2024](https://make.wordpress.org/core/2024/06/13/data-views-update-june-2024/)󠁿 With the last few releases of WordPress, the glimmers of phase 3 of the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) roadmap are starting to shine through, namely in the form of the new powerful [Data Views](https://github.com/WordPress/gutenberg/issues/55083). While exciting to see a glimpse of what’s to come, it’s also causing an understandable increase in questions – What can we use today? What_ should _we use based on each use case? What work is coming up next? This post seeks to provide answers at a high level view of these questions, along with some general context as to what’s being done and why. It’s pulled from a wide range of conversations including [advancing the site editor index views](https://github.com/WordPress/gutenberg/issues/59659), [ ](https://woodesignthings.wordpress.com/2024/05/14/rfc-woo-settings-design-update/#comment-10788) [Roadmap to 6.6](https://make.wordpress.org/core/2024/05/03/roadmap-to-6-6/), and more. This is and shall continue to be an evolving conversation. ## **Background: ** **What problems are Data Views trying to solve?** The current WP List Tables lack the flexibility required for more complex websites and are not suited for the technological demands of phase 3, which emphasizes collaboration workflows like saving and sharing specific views. Data Views aims to revolutionize these views by providing enhanced functionality, including alternative display options, extensive customization capabilitiescapability A **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)., and robust extension points. **What are Data Views? ** Data Views refers to an improved and reusable UIUI User interface for different screens in WordPress that deal with collections of things whether that’s templates, patterns, posts, media, and more. Currently, those views are known as WP List Tables and Data Views seeks to replace those over time. It’s being built with extensibility in mind and is a big part of phase 3, specifically the Adminadmin (and super admin) Redesign efforts. This new UI will also power other long term future parts of phase 3 work, including workflow improvements for assigning folks to review posts or creating custom views to streamline processes. Currently, the Data Views are isolated just to the Site Editor and an initial version was released in 6.5 with a broader iteration underway for 6.6. Below is a video showing the current WP List Tables in comparison to the new Data Views, showing both shared functionality and some of what the Data Views can offer that WP List Tables can’t, like different layouts, exposing more fields, and offering previews: **Why is the work being approached this way?** This work is intentionally being done first in the Site Editor with private APIs to allow for quick iteration and a more narrow impact than starting in the broader wp-admin landscape. The following principles are in mind as this work is underway: * Iteratively, with each step bringing meaningful improvements. * Stay subject to feedback from the broader community. * Stay backwards compatible. * Focus on 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). * [Built with extensibility](https://github.com/WordPress/gutenberg/issues/61084) in mind from the start.  * Best in class user experience.  Ultimately, whatever is shipped publicly will need to be maintained and it’s important to avoid disruptive changes while these efforts are in an iterative stage.   **What’s happening for WordPress 6.6?** For WordPress 6.6, set to launch in July, the release includes work to bring the various management pages forward in the Site Editor (manage all templates, manage all template parts, manage all pages) so those options are immediately seen when visiting the respective sections, reducing the number of steps to access important information. For pages, a new side by side layout will be introduced so one can see both a list of all pages and a preview of the currently selected page. For patterns, template part management will be removed and integrated into the current overall patterns section. Interspersed within all of these larger changes are smaller enhancements in functionality and feel, including [details normalization](https://href.li/?https://github.com/WordPress/gutenberg/issues/59689) that will eventually scale up into a bulk editing tool. **What’s coming up after WordPress 6.6?** A major priority is extensibility APIs so plugins in the future can begin altering and extending these pages, inevitably resulting in more feedback. Currently, an [initial API has been bootstrapped](https://github.com/WordPress/gutenberg/pull/62052) to allow third-party developers to register and unregister post type actions with [broader, high level plans outlined](https://github.com/WordPress/gutenberg/issues/61084). Outside of that, there are explorations underway to bring the new list views, as an opt-in experiment in the Gutenberg pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party., [to the Posts listing](https://github.com/WordPress/gutenberg/issues/62371) and the [Media library](https://github.com/WordPress/gutenberg/issues/55238). These are intentionally being done as experiments for now to see what might be viable for a future release and will take the form of contained Site Editor-like instances. At the same time, a [Data Views Forms effort ](https://github.com/WordPress/gutenberg/issues/59745) is underway that’s meant to allow for bulk editing first and, in the future, to be a framework to generate forms and details panels. [⌊Re-imagined WordPress Media Library showing an organized sidebar with categories, file types, and tags on the left with a list of all media files in the frame.⌉⌊Re- imagined WordPress Media Library showing an organized sidebar with categories, file types, and tags on the left with a list of all media files in the frame.⌉[ _A design that imagines a _[_Data Views powered Media Library experience_](https://github.com/WordPress/gutenberg/issues/55238#issuecomment-2120835504)_._ ## **Can we use Data Views?** **TLDR: This work is in an evolving middle stage where feedback is needed but what’s being done isn’t fully formed to implement wholesale. ** Extensibility has been a key piece of this work baked into all of these efforts from the very beginning. However, in order to move quickly to build on new parts of Data Views and avoid breaking changes, these APIs are currently Gutenberg plugin- only APIs. At the same time, it’s important to get extender feedback to shape the work being done.  For now, folks can bundle the Data Views styles into a plugin. You can even[ copy/paste these frames in the design library](https://www.figma.com/design/e4tLacmlPuZV47l7901FEs/WordPress-Design-Library?node-id=66128-15838&t=gAUDrPRvOxU7E4A0-0) for quick mockups. Currently, the `@wordpress/dataviews` package is public already, meaning you can install it, use it from npm, and bundle it in your own scripts. What remains private is that it’s not exposed as a WP global, which means future breaking changes are possible but you’ll be able to upgrade the package at your own pace if you bundle it. **There are also no extensibility APIs for the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. provided data-views yet for WordPress 6.6 (Templates, pages, patterns) which means you can’t alter these pages yet from a WordPress plugin.** As mentioned above, an [initial API has been bootstrapped](https://github.com/WordPress/gutenberg/pull/62052) to allow third-party developers to register and unregister post type actions with [broader, high level plans outlined](https://github.com/WordPress/gutenberg/issues/61084) for furthering extensibility.  For those who can adopt this work, please do and report back around the edges you find so we can iterate. For some, you may need to wait until it’s fully formed. The answer depends on what you’re trying to do and on what timescale. As always though, going as native as possible as soon as possible is beneficial both to ensure what’s being built works for your use case and to prevent the future work that will be needed to adopt what’s built.  In the future, you can imagine a more customizable interface all within the same current navigation structure rather than a wp-admin like interface. Folks can pick and choose which plugin interfaces to pin and use, rearrange navigation items, and experience a similar flow and presentation no matter where they go. We aren’t there yet but we’re on a path in that direction: [⌊View of an imagined WordPress interface with a sidebar showing various options to select between and a preview of the site in question. ⌉⌊View of an imagined WordPress interface with a sidebar showing various options to select between and a preview of the site in question. ⌉[ ## **Where can I follow along and provide feedback?** Feedback is wanted and _needed_! Here are a few ways to follow along, depending on the level you want: * [Phase 3: WordPress admin redesign](https://github.com/WordPress/gutenberg/issues/53322#top): this is the highest level overview of the current work and thinking for the whole of the admin redesign. * [DataViews component](https://github.com/WordPress/gutenberg/issues/55083#top): this is the highest level overview of the data views specific component and technical work needed that is a big piece of the overall admin redesign. * [Advancing site editor index views](https://github.com/WordPress/gutenberg/issues/59659#top): this is a medium term scope of work that’s likely to exist across a few WordPress major releases. * [Data Views Extensibility issue](https://github.com/WordPress/gutenberg/issues/61084): this is a dedicated issue to the topic of extensibility.  * [Data Views for Posts, Categories, and Tags](https://github.com/WordPress/gutenberg/issues/62371): this is a dedicated issue around exploring bringing data views to power the Posts section of WP Admin. * [Data Views issues label](https://github.com/WordPress/gutenberg/labels/%5BFeature%5D%20Data%20Views): this gives a very granular look at the various pieces being worked on. This might be helpful to wade through when you’re attempting to open an issue or comment on a current one. **To share feedback and ask questions, check**[ **currently open issues**](https://github.com/WordPress/gutenberg/labels/%5BFeature%5D%20Data%20Views)** to leave a comment or** [**open a new GitHub issue in the Gutenberg repo.**](https://github.com/WordPress/gutenberg/issues/new/choose)**** This post is simply to share an update and the best place to get involved in a discussion is in GitHubGitHub 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. [https://github.com/](https://github.com/). If you have clarifying questions about the post itself, you’re welcome to ask them. _Thank you to [@fabiankaegy](https://profiles.wordpress.org/fabiankaegy/) [@jorbin](https://profiles.wordpress.org/jorbin/) [@youknowriad](https://profiles.wordpress.org/youknowriad/) [@joemcgill](https://profiles.wordpress.org/joemcgill/) [@mikachan](https://profiles.wordpress.org/mikachan/) for reviewing and collaborating on this post. Thank you to [@joen](https://profiles.wordpress.org/joen/) for creating the video used._ [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/), [#phase-3](https://make.wordpress.org/core/tag/phase-3/), [#plugins](https://make.wordpress.org/core/tag/plugins/) [ ](https://profiles.wordpress.org/antpb/) [Anthony Burchell](https://profiles.wordpress.org/antpb/) 4:51 pm _on_ January 17, 2024 Tags: [agenda ( 1,149 )](https://make.wordpress.org/core/tag/agenda/), [media ( 93 )](https://make.wordpress.org/core/tag/media/), [media library ( 4 )](https://make.wordpress.org/core/tag/media-library/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), phase 3    # 󠀁[Phase 3 Media Meeting: February 7, 2024](https://make.wordpress.org/core/2024/01/17/media-phase-3-meeting-feb-7/)󠁿 **Date and time:** [February 7, 2024 at 24:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240208T0000) ** Location:** [#core-media](http://wordpress.slack.com/messages/core-media/)**Duration:** 1:00 hr The Media Component team is coordinating a meeting with the Editor team and other interested stakeholders to work on planning for the proposed Phase 3 Media Library. There are a few issues already open about the Media Library proposal, but this major development depends on close coordination between the Media and Editor teams to work effectively together. In a recent Media Component meeting it was suggested that there should be a dedicated meeting time to kick off a round table discussion about some of the opportunities and challenges ahead in the development of Phase 3. The Media Component Maintainers hope to find areas of focus where contributors can lean in to align efforts with folks working on Phase 3. In previous meetings the team has gone through the backlog of over 600 issues and categorized tickets as `phase-3-media-triage` for discussion around how Phase 3 could potentially solve these tickets alongside a rebuild of the Media Library. Some of these tickets are an opportunity to change lower level issues like db structure, but the redesign is a good time to address these possibilities. ## Relevant Pull Requests, Issues, and Posts: [Phase 3: Collaboration > Media Library](https://github.com/WordPress/gutenberg/issues/55238) [PR Dataview: media view](https://github.com/WordPress/gutenberg/pull/56237) > [Media Library](https://make.wordpress.org/core/2023/07/07/media-library/) ## Proposed meeting agenda: 1. Introductions 2. Brief presentation on the goals and vision of Phase 3 redesign for the Media Library 3. Discussion on alignment of CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Media focus to help the process 4. Agree on communication channels and checkpoints for regular updates 5. Review of [Phase-3-Triage Tickets](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&keywords=~phase-3-media-triage&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&order=priority) A more detailed agenda will be published prior to the meeting. If you would like to join this meeting please join the [#core-media](http://wordpress.slack.com/messages/core-media/)__ channel [February 7, 2024 at 24:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240208T0000). This time seems to align with most of the world as a decent hour to meet for stakeholders and folks active in Media. --- _This meeting happens in the _[#core-media](http://wordpress.slack.com/messages/core-media/)_ channel. To join the meeting, you’ll need an account on the [Make WordPress Slack](https://make.wordpress.org/chat/)_._ Props [@joedolson](https://profiles.wordpress.org/joedolson/) for helping prepare and proofread this post._ [#agenda](https://make.wordpress.org/core/tag/agenda/), [#media](https://make.wordpress.org/core/tag/media/), [#media-library](https://make.wordpress.org/core/tag/media-library/), [#meeting](https://make.wordpress.org/core/tag/meeting/), [#phase-3](https://make.wordpress.org/core/tag/phase-3/) [ ](https://profiles.wordpress.org/s1m0nd/) [Simon Dickson](https://profiles.wordpress.org/s1m0nd/) 10:50 am _on_ January 8, 2024 Tags: [feedback ( 3 )](https://make.wordpress.org/core/tag/feedback/), phase 3, [summary ( 981 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Phase 3 Agency Outreach Recap, December 2023](https://make.wordpress.org/core/2024/01/08/phase-3-agency-outreach-recap-december-2023/)󠁿 Phase 3’s focus on collaboration, revisionsRevisions 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. and workflow takes 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/) further into enterprise territory. Inspired by [@annezazu](https://profiles.wordpress.org/annezazu/)’ s earlier outreach exercise, and following up on [my own proposal](https://make.wordpress.org/core/2023/10/23/summary-and-insights-of-phase-3-related-conversations/#comment-45779), I took the opportunity of availability during December 2023 to reach out to WordPress agencies specialising in enterprise projects, inviting them to a series of informal show-and-tell sessions. The aim was to gain an insight into enterprise clients’ requirements, and how agencies currently address them. Sessions were offered on a semi-confidential ‘[Chatham House Rule](https://www.chathamhouse.org/about-us/chatham-house-rule)’ basis, to avoid any concerns around client confidentiality; but I committed to publishing a summary of what we saw and learned. ## Take-up was disappointing. Invites were sent via several different outreach channels, chosen primarily based on the personal connections of the people involved: WordPress VIP’s partner networknetwork( versus site, blog), the Enterprise channel in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds 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/), and the News Nerdery community. This ought to have touched around 100 enterprise- centric agencies. I scheduled 9 one-hour sessions over a 10-day period, at times to suit all timezones. There was capacity for around 40 agencies to participate; but in the end, fewer than 5 agencies signed up. A few others indicated an interest, but did not get round to signing up. There are many possible explanations. Perhaps December was simply poor timing. Our call for presentations was kept deliberately open and vague; perhaps it should have been more specific. Informal walkthroughs were requested, to minimise the burden of planning and preparation, but perhaps folks would have been more comfortable giving formal presentations. What is clear is that Core currently lacks warm and clear communication channels with the agency ecosystem – at a time when such channels would be particularly useful for both parties. It also follows that the following observations are based on a smaller snapshot of enterprise usage than was hoped for.  ## Enterprise development practice moves slowly. Agencies and their clients now seem comfortable with blocks, as delivered in Phase 1: this is largely backed up by data in the recent [SOEWP survey](https://soewp.com). But we saw no examples yet of Phase 2-style ‘site customisation’: agencies are still sticking with familiar models based on site metadata and Settings pages, even when Phase 2 functionality would probably deliver a better outcome. An enterprise may only revisit its tech stack every 3 or 4 years, with no reason to fix what isn’t broken. Agencies are probably working on multiple enterprise contracts simultaneously, theoretically giving them more opportunities to embrace new possibilities; but with a decade of pre-Gutenberg ‘muscle memory’, they have a commercial incentive to stick with what they know until proven otherwise. ## Collaboration will inevitably happen outside WordPress. Enterprise employees spend their entire day in office suites like Google Docs or Microsoft 365; social media planning solutions; general collaboration platforms like Jira or Asana; industry specific tools like Desk-Net for newsrooms; technical platforms like GitHubGitHub 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. [https://github.com/](https://github.com/). If businesses already have these tools, integrated into their company-wide workflow, for tasks beyond website management, it’s a bigger challenge for WordPress to force its way into the picture. Collaboration also happens before WordPress arrives on the scene, in the definition of a ‘house style’, or page templates, which are then hard-coded into the WordPress workflow. Web content creators get limited flexibility, or perhaps none at all, simply filling in boxes. This may seem like the antithesis of user empowerment. But: * The business gets predictable, consistent results, always on-brand, delivered efficiently. * Employees’ main concern is to get the job done quickly, and move on to their next task. * Agencies can tailor UIUI User interface and UXUX User experience to very specific outcomes, minimising the support burden. ## Real-time content collaboration is not a current user priority. We saw no ‘cowpaths to be paved’ when it comes to real-time collaboration on normal content. The closest we have come has been from an agency working with large news organisations: they described multiple people swarming on a single piece of content, but working on different aspects of it. There would only be one author writing in ‘the content area’: but they would be supported by a picture editor, an SEO manager, a headline manager, a ‘homepage manager’ deciding where it will appear. (This is broadly in line with [@annezazu](https://profiles.wordpress.org/annezazu/)’s earlier findings.) But some content types are, by definition, real-time and multi-author. One agency brought up the example of ‘live blogs’. If a news site runs ‘live blogs’, typically for major ‘breaking news’ events or sports coverage, these will usually be among their most popular articles of the day. ([Source: Press Gazette, 2023.](https://pressgazette.co.uk/publishers/digital-journalism/live-blogs-bbc-guardian-sky-news/)) Publishers dislike ‘live blogblog (versus network, site)’ solutions embedded from third-party platforms, which do not deliver search-engine benefits. We saw one custom WP-based solution running in the back end, which suffered from the current inability to have multiple authors on the same edit screen. We also know of front-end based, Gutenberg-compatible liveblogs which allow for multiple authors and more creative content entry methods. We certainly heard a desire for multiple users to collaborate around a single content item. But ‘Google Docs in the editor component’ is not the only possible meaning of collaborative creation… and may not even be the main one. ## Revisions need work. The current implementation of Revisions predates blocks, and is barely usable given the amount of code now held in post_content. One agency demonstrated work they have done for a major European newspaper, refined over several years, which offers 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.-compatible 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. comparison, with red and green highlighting of changes. They are open to the idea of sharing their code with Core; and are investigating how this might happen. It was noted that collaborative editing may have unintended consequences for the current Revisions model. Right now, when only one user can edit and save at any one time, we know exactly who made each change, and when. This can be important for corporations in regulated industries. We lose that simple attribution to an individual, if multiple users are editing simultaneously. (Also noted in [@leogermani](https://profiles.wordpress.org/leogermani/)‘ s [GitHub discussion thread](https://github.com/WordPress/gutenberg/discussions/56954).) ## In conclusion * Core currently lacks channels for communicating and engaging with the agency ecosystem. * Collaboration on aspects of the website often happens away from the website, and involves people who never touch the website. * WordPress cannot realistically be the sole collaboration space for many enterprises and publishers, even as relates to a WordPress-based publishing workflow. * The ability to collaborate across different components of a post is currently a greater priority than collaborating within the post_content itself. * Beware of unintended consequences – for example, collaborative editing breaking our current Revisions model. ## Where next? Outside of immediate steps I can take, like supporting the agency mentioned to package its work on revisions for Core or arranging future sessions with agencies who expressed interest, we wanted to open the floor to hear from others around ways to improve uptake for enterprise agencies. * What do you think would help? * What should we try next to spark these conversations and bring feedback into this next phase? _My thanks to _[@annezazu](https://profiles.wordpress.org/annezazu/)_ and various members of the Core team for participating in this initiative; and to enterprise agency Big Bite for sponsoring my time in organising and running these sessions._ [#feedback](https://make.wordpress.org/core/tag/feedback/), [#phase-3](https://make.wordpress.org/core/tag/phase-3/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/) 8:11 am _on_ October 23, 2023 Tags: [feedback ( 3 )](https://make.wordpress.org/core/tag/feedback/), phase 3, [summary ( 981 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Summary and Insights of Phase 3 related conversations](https://make.wordpress.org/core/2023/10/23/summary-and-insights-of-phase-3-related-conversations/)󠁿 Over the last few months, I’ve had 20+ conversations with various folks across the WordPress ecosystem, from developers implementing WordPress at scale to folks working in large newsrooms to one-person operations. After leaving comments on the various [Phase 3 posts](https://make.wordpress.org/core/tag/phase-3/), it felt advantageous to write a quick summary of the feedback to help inform our future work, akin to the efforts of the FSE Outreach program, and encourage others who might be having similar conversations to continue to share for the entire project to benefit from. ## **Overview** Most conversations lasted about 45-60 minutes, with very few running into the two- hour range.  The conversations were open ended with folks broadly sharing their content process from ideation to completion and ended talking about the various phase 3 related posts with encouragement to engage. Of the 24 conversations, I have roughly grouped them across the following categories: * 3 individual developers with either experience implementing WordPress at scale or building collaborative tooling. * 1 person representing higher education. * 2 people running their own individual projects/sites. * 10 larger newsrooms or organizations. * 8 smaller newsrooms or organizations.  These were sourced from a variety of connections including: GitHubGitHub 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. [https://github.com/](https://github.com/) issue creators, [WordPress VIP intros](https://wpvip.com/), [Newspack clients](https://newspack.com/),“ cold emailing”, folks from the FSE Outreach Program, and more. In full disclosure, I am sponsored by Automattic to do this work and leveraged these connections to reach out to a broader range of folks. For many, they are using a suite of tools to get the job done, often without deep integration, and usually landing in WordPress when the copy is nearly complete. Phase 3 would/could shift that experience, allowing folks to land and work within WordPress sooner and with that comes a list of features and requirements. Read on! **Collaborative editing & asynchronous collaboration ** At a high level, I repeatedly heard from folks in larger organizations more of an interest in collaboration in the form of the ability for multiple people to be in different parts of an article over true collaborative editing. Especially for larger to medium-sized publishers, there’s less of a need for real-time collaboration and more of a need for different sets of folks in an article simultaneously with blocks locked individually. The same applies to the experience of editing the details of a post, like a categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. or featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. while not having access to edit the entire post itself. For example, someone from the photo team can place images without having the ability to edit the content blocks, or a handful of folks being able to edit tags directly without getting in the way of the writers.  * Multiple people editing a doc at once. * Role-specific permissions allowing some folks to accept/deny various edits. * More granular ability to edit specific parts of a post/page at once without having full access to everything, including 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. leveling locking. * Commenting functionality, including the ability to @ folks. * Public preview link for folks, regardless of whether they have access to the site.  **Workflows** No one I spoke with manages everything in WordPress with a wide range of additional tools and workflows in use from extraordinarily complex and manual to some setups with deeper automatic integration (status changes in X which automatically updates Y at the next step) to more manual organizing before adding anything into WordPress( adding images to a folder on a desktop before uploading). A need for a dashboard/ task manager is clear as well as a need for integration with other tooling.  * Support for tasks that can be customized depending on the post type and have a built-in “severityseverity The seriousness of the ticket in the eyes of the reporter. Generally, severity is a judgment of how bad a bug is, while **priority** is its relationship to other bugs.” type (required vs nice to have). For example, a task might be more of a nice to have than a necessity, but both are worth calling out for the person to act on.  * Seeing changes that have occurred since you last opened a document ([related to my note on revisions](https://make.wordpress.org/core/2023/07/05/revisions/#comment-45240)). * Tie notifications into different tasks and the status of articles to reduce the need to pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of“ Ping me when the meeting starts.” someone in a separate system. For example, perhaps legal needs to be emailed about an article, or the media team needs to be notified that a post is ready for images. * Ability to see open tasks/open notifications with ease (task manager), along with an at-a-glance view of where something might stand (editorial calendar). * Section level locking for different parts of a post, like the post content vs. post title vs. featured image, tied into task management with perhaps reviews needed for each before publishing. * Solid integration options with other tools, like 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/)/ TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the make.wordpress.com/marketing team uses for example: [https://trello.com/b/8UGHVBu8/wp-marketing.](https://trello.com/b/8UGHVBu8/wp-marketing)/ Asana, for notifications and state changes (draft to pending review, reminding folks about assignments, etc). * Easy draft sharing for varying permission levels including stakeholders without access to the site itself. * Ability to publish with multiple authors. **RevisionsRevisions 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.** The most commonly requested items proved to be more visual revisions and the ability to track more than just post content changing. These stood out amongst the rest as the most broadly useful items.  * More visual revision history, perhaps with the option to toggle between code views. * Ability to track more than just post content, including changes to tags, a featured image, SEO, and other custom fields (like managing multiple headlines). * Ability to split out a revision to develop it separately from the main draft and keep track of how the current version continues with some form of track changes( this is likely more in an async workflow, but it relates). * Ability to see a notice of an audit trail when coming into a post after a few revisions, including who made which changes. For example, if an editor went through and made a number of changes to a post so the writer can see the difference. * A way to focus on a particular part of an article to see how it might have changed, rather than the entire piece. * Improved management of posts with numerous revision history events (think 50+). It’s currently pretty painful to try to go through revisions at scale. * [Ability to readily schedule mass changes](https://github.com/WordPress/gutenberg/issues/29575) across the site.  Tied to this, I’ll note from the FSE Outreach Program that feedback has come in very positively around the Style Revision experience both in terms of the visual nature and easy to understand timeline with a [request to have that in place for templates and template parts](https://github.com/WordPress/gutenberg/issues/52138). **Block library** [The ability to configure more granular control](https://github.com/WordPress/gutenberg/issues/49592) over blocks continues to come up as a pain point, especially as more support is added by default in different ways that cause folks to feel a level of uncertainty and scrambling to keep up. Anything we can do to consolidate the methods for controlling block access and support would go a long way. For example, even if you use 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. to lock down all support and settings for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress./media-text, block settings still appear in the block 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. due to that being defined in core/media-text’s component code and inserted in a custom panel. Tied to this, folks want the ability to see where patterns are used across a site(“ this pattern is used on x number of posts”) as a better way to gauge the impact of changes, particularly for synced patterns. Finally, [the ability to have theme.json partials on groups of blocks](https://github.com/WordPress/gutenberg/issues/53705) would be a huge step forward to provide a locked-down experience for folks who are in the position of simply trying to put content into a specific layout. **Media Library** Media management, from the ability to add folders to controlling copyright information, are big concerns for folks, especially in larger organizations where many images are uploaded per day. * Way to manage and view image attribution and copyright information. This was repeated often as a high priority item and major pain currently.  * Improved alternative text management.  * Ability to add folders. * Improved searchability.  * Ability to upload photos designed for a specific post and having those photos surfaced when working on a post.  **Adminadmin (and super admin) redesign** There was a lack of overall feedback here as folks mainly focused on wanting the experience to be “more modern” without a lot of specific feature requests.  * The ability to reorder, hide, and favorite menu items for greater customization. * Desire for a redesign to modernize the experience. This was nonspecific but repeated feedback that [ties into Data Views work](https://github.com/WordPress/gutenberg/issues/55083). ## **Going forward** As more conversations occur and work progresses, I’ll continue to bring feedback into appropriate GitHub issues and/or create new ones. For more open ended feedback, like the above, I’ll do recap posts as appropriate. If you’re chatting with folks about Phase 3 efforts, please do the same! Similar to Phase 2, we’ll need folks across the WordPress community to have conversations, educate, and bring others along. **Want to chat about phase 3 in the future? Comment below.** If you’re interested in joining future hallway hangouts on the topic, please leave a comment below and I’ll @ your username for any future hallway hangouts I run going forward.  **Want to get involved today?** These conversations centered around the already public post on each topic so keep chiming in on those: [Real-Time Collaboration](https://make.wordpress.org/core/2023/07/03/real-time-collaboration/), [Workflows](https://make.wordpress.org/core/2023/07/04/workflows/), [Revisions](https://make.wordpress.org/core/2023/07/05/revisions/), [Media Library](https://make.wordpress.org/core/2023/07/07/media-library/), [Block Library](https://make.wordpress.org/core/2023/07/10/block-library/), and [Admin Design](https://make.wordpress.org/core/2023/07/12/admin-design/). _Thank you to [@cbringmann](https://profiles.wordpress.org/cbringmann/) [@chanthaboune](https://profiles.wordpress.org/chanthaboune/) for reviewing this post. _ [#feedback](https://make.wordpress.org/core/tag/feedback/), [#phase-3](https://make.wordpress.org/core/tag/phase-3/), [#summary](https://make.wordpress.org/core/tag/summary/) # Post navigation [← Older posts](https://make.wordpress.org/core/tag/phase-3/page/2/?output_format=md)