Skip to content

Split Available Experiments into Editor and Admin sections#263

Closed
Ryujiyasu wants to merge 2 commits intoWordPress:developfrom
Ryujiyasu:feature/split-experiments-editor-admin
Closed

Split Available Experiments into Editor and Admin sections#263
Ryujiyasu wants to merge 2 commits intoWordPress:developfrom
Ryujiyasu:feature/split-experiments-editor-admin

Conversation

@Ryujiyasu
Copy link
Copy Markdown
Contributor

@Ryujiyasu Ryujiyasu commented Feb 28, 2026

Summary

Closes #218

  • Add a category field ('editor' or 'admin') to experiment metadata via the Experiment interface and Abstract_Experiment base class
  • Split the single "Available Experiments" section into two distinct sections: Editor Experiments and Admin Experiments
  • Reorder experiments to match the proposed structure in the issue
  • Extract experiment item rendering into a reusable render_experiment_item() private method to avoid duplication

Screenshot

Screenshot will be added in a comment below.

Test plan

  • Visit Settings > AI Experiments and verify experiments are grouped into "Editor Experiments" and "Admin Experiments" sections
  • Verify Editor Experiments appear in order: Title Generation, Excerpt Generation, Content Summarization, Image Generation, Alt Text Generation
  • Verify Admin Experiments shows: Abilities Explorer
  • Toggle global experiments off and verify the disabled notice appears in the Editor section
  • Enable/disable individual experiments and save — verify settings persist correctly
  • Run composer lint and composer phpstan to verify coding standards

🤖 Generated with Claude Code

Open WordPress Playground Preview

Add a `category` field to experiment metadata to group experiments
into "Editor Experiments" and "Admin Experiments" sections on the
settings page, improving clarity for users.

Closes WordPress#218

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown

github-actions bot commented Feb 28, 2026

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: Ryujiyasu <ryujiyasu@git.wordpress.org>
Co-authored-by: jeffpaul <jeffpaul@git.wordpress.org>
Co-authored-by: dkotter <dkotter@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@codecov
Copy link
Copy Markdown

codecov bot commented Feb 28, 2026

Codecov Report

❌ Patch coverage is 14.11765% with 73 lines in your changes missing coverage. Please review.
✅ Project coverage is 55.45%. Comparing base (530ae7e) to head (12ded43).

Files with missing lines Patch % Lines
includes/Settings/Settings_Page.php 0.00% 71 Missing ⚠️
includes/Abstracts/Abstract_Experiment.php 33.33% 2 Missing ⚠️
Additional details and impacted files
@@              Coverage Diff              @@
##             develop     #263      +/-   ##
=============================================
- Coverage      55.91%   55.45%   -0.46%     
- Complexity       509      513       +4     
=============================================
  Files             32       32              
  Lines           2611     2647      +36     
=============================================
+ Hits            1460     1468       +8     
- Misses          1151     1179      +28     
Flag Coverage Δ
unit 55.45% <14.11%> (-0.46%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@Ryujiyasu
Copy link
Copy Markdown
Contributor Author

SCREENSHOT is here
screenshot-settings

@jeffpaul jeffpaul added this to the 0.4.0 milestone Mar 2, 2026
@dkotter
Copy link
Copy Markdown
Collaborator

dkotter commented Mar 2, 2026

@Ryujiyasu There's already a separate PR open to solve this (#232). Curious if there's anything unique in this PR we should be considering or if this should be closed as a duplicate?

@Ryujiyasu
Copy link
Copy Markdown
Contributor Author

@dkotter Thanks for pointing that out! I wasn't aware of #232 when I opened this. This was a great learning experience for me, but since #232 already covers the same ground, I'll go ahead and close this as a duplicate. 🙏

@Ryujiyasu Ryujiyasu closed this Mar 2, 2026
@jeffpaul jeffpaul removed this from the 0.4.0 milestone Mar 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Split Available Experiments into Editor and Admin sections

3 participants