WordPress 7.0 will introduce real-time collaboration in the block editor. Out of the box, the editor syncs changes between peers using an HTTP polling provider. However, an HTTP polling transport isn't the only option and it may not be the best fit for your infrastructure, especially if you are a WordPress hosting provider. The sync.providers…

WordPressCore's platform is a central hub for WordPress developers and contributors, offering insights into WordPress core development, plugin development, and theme customization. Through articles, tutorials, and community forums, WordPressCore offers insights into WordPress architecture, development best practices, and contributing to the WordPress open-source project. Readers can learn about WordPress coding standards, security guidelines, and performance optimization techniques to build powerful and secure websites with WordPress.

Make WordPress Core

WordPress 7.0 will ship real-time collaboration in the block editor using Yjs CRDTs, with HTTP polling as the default sync transport. A new client-side filter, sync.providers, lets developers replace that default with a custom provider. The post explains what a sync provider does (transport Yjs document updates between peers, report connection status), how to implement a provider creator function, and how to wrap existing Yjs providers like y-websocket. It also covers critical security considerations: token-based auth via a WordPress REST endpoint, per-document authorization, short-lived token rotation, and graceful disconnect handling. The open-source WPVIP Real-Time Collaboration plugin is cited as a reference implementation.

Building a custom sync provider for real-time collaboration