Skip to content

Write: expand Write editor eligibility during gradual rollout#48730

Open
allilevine wants to merge 3 commits into
trunkfrom
add/write-editor-enable-for-a12s
Open

Write: expand Write editor eligibility during gradual rollout#48730
allilevine wants to merge 3 commits into
trunkfrom
add/write-editor-enable-for-a12s

Conversation

@allilevine
Copy link
Copy Markdown
Member

@allilevine allilevine commented May 12, 2026 •
edited
Loading

Related to RSM-2870

Proposed changes

  • Expand Write editor loading to include additional users during gradual rollout, alongside sites with the wpcom-write-editor blog sticker.

Related product discussion/links

  • RSM-2870

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

No.

Testing instructions

  • On a site without the wpcom-write-editor sticker, verify the Write editor is accessible at /wp-admin/admin.php?page=write for qualifying users.
  • On a site without the sticker and a non-qualifying user, confirm the Write editor is not accessible.

allilevine and others added 2 commits May 12, 2026 14:53
@allilevine @claude
feat(write): enable Write editor for Automatticians
3efe16f 
Expand Write editor loading to also trigger for a12s, in addition to
sites with the wpcom-write-editor blog sticker. Part of RSM-2870.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@allilevine @claude
changelog: add entry for jetpack-mu-wpcom write editor rollout
cf1cafb 
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@allilevine allilevine added the [Status] Needs Review This PR is ready for review. label May 12, 2026
@allilevine allilevine self-assigned this May 12, 2026
@github-actions github-actions Bot added the [Package] Jetpack mu wpcom WordPress.com Features label May 12, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 12, 2026

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!

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 12, 2026 •
edited
Loading

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 (WordPress.com Site Helper), and enable the add/write-editor-enable-for-a12s branch.
  • To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack-mu-wpcom-plugin add/write-editor-enable-for-a12s

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

@jp-launch-control
Copy link
Copy Markdown

jp-launch-control Bot commented May 12, 2026 •
edited
Loading

Code Coverage Summary

Coverage changed in 1 file.

File Coverage Δ% Δ Uncovered
projects/packages/jetpack-mu-wpcom/src/class-jetpack-mu-wpcom.php 24/389 (6.17%) -0.03% 2 ❤️‍🩹

Full summary · PHP report

@allilevine @claude
fix(write): use A8C_PROXIED_REQUEST for a12s check on Atomic sites
4ca1d53 
is_automattician() is only available on Simple; add A8C_PROXIED_REQUEST
check so Atomic sites also enable the Write editor for a12s.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
kbrown9
kbrown9 approved these changes May 13, 2026
View reviewed changes
Copy link
Copy Markdown
Member

@kbrown9 kbrown9 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The logic looks good to me! I did a quick test with an a11n account with simple/atomic and stickered/non-stickered sites, and I was able to access the Write editor on all of them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@kbrown9 kbrown9 kbrown9 approved these changes

Assignees

@allilevine allilevine

Labels

[Package] Jetpack mu wpcom WordPress.com Features [Status] Needs Review This PR is ready for review.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@allilevine @kbrown9