WordPress Development: Collaboration Phase

The new WordPress 6.2, which focuses primarily on the Site Editor customization experience, will be released next week. Phase three of the Gutenberg development is said involve Collaboration, and project lead architect Matias Ventura outlines what this phase involves. 

The Gutenberg project has undergone several phases since its inception. It began with the introduction of the block editor in WordPress 5.0, which allowed users to create and edit content using modular blocks. It then followed with a second phase, bringing the block editing experience to the rest of the site.

As the project evolved, new features were introduced to enhance the user experience further. Patterns, for instance, allowed users to reuse predefined block combinations and layouts, helping streamline the design process. Block themes enabled creators to fully embrace the blocks for an entire website, from header to footer. The community’s collaborative spirit has fostered an ever-growing library of resources that empower users to create stunning and highly functional websites.

Ventura writes that the next phase of Collaboration will focus on making content management flows more efficient and making collaboration easier. The rest of the admin experience will be looked as well. The followings are some of the key focus areas of phase three:

  • Real-time collaboration. The goal is to provide all the necessary infrastructure and UI to handle multiple users working together on the same content simultaneously, making it easier to create, edit, and customize web pages and posts as a team.
  • Asynchronous collaboration. The goal is to enable users and larger teams to collaborate on projects and its different parts at their own pace and based on their workflows.
  • Publishing flows.This includes the various processes, requirements, and steps involved in creating, editing, reviewing, and publishing content within WordPress.
  • Post revisions interface. Make them more visual, aware of individual blocks, and explore adding the ability to schedule revisions across multiple parts of a site.
  • Admin design. Begin the process for an admin design update and navigation work, with plugins and customized user flows in mind. Admin notices and the UI library of design components will be a major part of this effort to ensure use cases are supported while respecting the user experience.
  • Library. Introduce an admin section or “library” for managing blocks, patterns, styles, and fonts. As part of this work, also look at what improvements can be done to enhance the media library design, interactions, and extensibility.
  • Develop a global search & command component that’s extensible.

Here is link to the original Phase 3: collaboration post.