[heydemoura]

Fixes #

Proposed changes

• The Video Playlist block renders its title as a nested, locked core/heading inner block above the playlist, so the title can be edited in place and styled (level, typography, colors) like any heading.
• The heading and the existing playlistTitle attribute stay in sync both ways: typing in the heading updates the Title field in the "Playlist details" panel, and editing the Title field updates the heading.
• New "Show title as heading" toggle (showPlaylistTitle, on by default) in the "Playlist details" panel; turning it off removes the heading while keeping the title for the site's playlist listings.
• The block's save now stores the heading inner block (InnerBlocks.Content); the rest stays server-rendered. Existing playlists stay valid: the heading appears on the front end once the post is saved with it, and there is no fallback heading for content saved before this change.
• The front end renders the heading only when the toggle is on and the title is non-empty.
• Dynamic playlists are not editable: the Latest Videos Playlist block offers no title, description or toggle, and its render drops any stored title and inner content, so it never shows a heading.

Related product discussion/links

• Follows the playlist index (VideoPress: add a site-wide playlist index option #52729) and All Playlists block (VideoPress: add an All Playlists block #52724), which introduced playlistTitle / playlistDescription and the locked-heading pattern.

Does this pull request change what data or activity we track or use?

No.

Testing instructions

• Build the VideoPress package (jp build packages/videopress) and open a site with VideoPress enabled.
• Insert a Video Playlist block and add a couple of videos.
• In the sidebar's "Playlist details" panel, type a title: an H2 heading with the same text appears above the playlist.
• Click the heading in the canvas and edit it: the sidebar Title field follows. Change its level or typography from the heading's toolbar/sidebar.
• Toggle "Show title as heading" off: the heading disappears and the Title field keeps its value. Toggle it on again: the heading comes back with the title.
• Save and view the post: the heading renders above the playlist. Clear the title or turn the toggle off, save, and confirm no heading renders.
• Try the dark player (Styles → dark) and check the heading stays readable.
• Insert a Latest Videos Playlist block: there are no title/description fields or heading toggle, and neither the editor nor the front end shows a heading.
• Open a post with a Video Playlist block saved before this change: the block is valid (no recovery prompt).

🤖 Generated with Claude Code

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack), and enable the add/videopress-playlist-title-heading branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack add/videopress-playlist-title-heading

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

---

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

• WordPress.com Simple releases happen as soon as you deploy your changes after merging this PR (PCYsg-Jjm-p2).
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly:
  • Scheduled release: October 6, 2026

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

---

Videopress plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[jp-launch-control]

Code Coverage Summary

Coverage changed in 2 files.

File	Coverage	Δ%	Δ Uncovered
projects/packages/videopress/src/class-initializer.php	457/514 (88.91%)	0.20%	0 💚
projects/packages/videopress/src/client/block-editor/blocks/playlist/edit.tsx	155/157 (98.73%)	1.32%	-2 💚

2 files are newly checked for coverage.

File	Coverage
projects/packages/videopress/src/client/block-editor/blocks/playlist/index.tsx	3/3 (100.00%) 💚
projects/packages/videopress/src/client/block-editor/blocks/playlist/use-title-heading.ts	25/25 (100.00%) 💚

Full summary · PHP report · JS report