Overview

With the Client Side Media feature being graduated to a core capability in WordPress 7.0, thorough documentation is needed for both developers and users. This documentation should cover:

• How client side media processing works within the block editor
• The benefits of using browser-based media processing versus server-side
• Supported image formats and processing capabilities
• Graceful fallback mechanism for unsupported browsers (and partially supported browsers without iframe credentialless support)
• Integration points and hooks for plugin developers (e.g., JS-side hooks analogous to existing server-side ones). which hooks no longer fire during uploads. how to disable the feature using a hook.
• Guidance on handling Cross-Origin Isolation and SharedArrayBuffer requirements
• Known risks and environment requirements

Tasks

• Draft new sections for the official Gutenberg and WordPress developer documentation detailing Client Side Media
• Create or update user-facing documentation to explain changes in media uploading workflow
• Add information for developers about how to extend or interact with the new system
• Document how to handle fallback scenarios and browser compatibility
• Ensure reference to roadmaps and tracking issues (e.g., Client Side Media iteration for WordPress 7.0 #74333) for additional context
• Draft a make/core post announcing the feature, linking to the documentation

References

• Core tracking issue: Client Side Media iteration for WordPress 7.0 #74333
• Current experiments: https://github.com/swissspidy/media-experiments

Acceptance Criteria

• Documentation is published in relevant developer and user guides
• Key architectural and UX changes are clearly explained with actionable examples
• Plugin developers can find guidance for adapting to JS-side hooks and fallbacks
• Documentation includes links to foundational PRs and background issues
• Draft created for make/core post