Skip to content

Add the Content Summarization UI #147

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
dkotter wants to merge 22 commits into
base: develop
Choose a base branch
from
Draft

Add the Content Summarization UI #147

dkotter wants to merge 22 commits into from

Conversation

@dkotter
Copy link
Collaborator

@dkotter dkotter commented Dec 18, 2025 •
edited by github-actions bot
Loading

Important

The code here is branched from #136.
Once that PR is merged, I will rebase this and then open this for review.

What?

Closes #12

The base Content Summarization Experiment and Ability were added in #136. This PR builds on top of that to add in the actual UI to trigger content summarization within the post editor.

Why?

With #136 merged in, you can manually trigger summarization by using the Ability but there isn't a way to trigger that from the UI. This PR adds in that UI, making that Experiment more useful.

How?

  • Ensure we properly build the needed assets for the Content Summarization Experiment and then load that properly in the admin
  • Add a component that renders in the Post Status section of the block editor. This will render a button that can be clicked to generate a summary
  • When that button is clicked, hit the Content Summarization Ability endpoint and if successful, store the summary in post meta and also render that in the editor
  • Create a block variation of the paragraph block that we use to render the summary
  • Add a custom button to the toolbar of this block that can also be used to re-generate a summary
  • Also updates our NPM dependencies to their latest versions

Testing Instructions

  1. Go to Settings > AI Credentials and ensure you have a valid AI provider configured
  2. Go to Settings > AI Experiments and ensure you have the Content Summarization Experiment enabled
  3. Edit a post that has content (or add new content) and ensure you see a Generate AI Summary button in the Post Status sidebar
  4. Ensure you can click on this button, a loading state shows and once it completes, a block is automatically inserted into the editor with a summary
  5. Click into that block and ensure you see a Regenerate button in the toolbar
  6. Click on that button and ensure it works as expected

Screenshots or screencast

Generate Summary button showing in the Post Status section of the block editor
AI generated summary being rendered in the AI Summary paragraph block variation
Re-generate Summary button showing in the Post Status section of the block editor
Regeneration button working in the AI Summary block variation

Test using WordPress Playground

The changes in this pull request can be previewed and tested using this WordPress Playground instance:

Click here to test this pull request.

Open WordPress Playground Preview

dkotter added 11 commits December 17, 2025 14:24
@dkotter
Load the assets on the post edit screen
e7b5109
@dkotter
Build our assets
5f8e927
@dkotter
Add the base plugin registration and render component
12d8d47
@dkotter
Wire up the generation of a summary when the button is clicked
a400786
@dkotter
Insert a paragraph block with the summary after it is generated. Make…
bb17301 
… the description dynamic
@dkotter
Store the summary in post meta after it is generated
d4940db
@dkotter
Update outdated dependencies
bc96c0f
@dkotter
Create a paragraph variation block and use that when we insert the su…
d0392cf 
…mmary
@dkotter
Check if we have an existing summary block and if so, pull the conten…
74acd10 
…t from that to update our state. And when inserting the summary block, replace the existing one or insert at the top if there isn't an existing one
@dkotter
Add custom toolbar controls to paragraph blocks marked as AI summaries
b0a099f
@dkotter
Move shared functionality into a hook so we can easily pull that in w…
96ed39f 
…here it's needed. Use this in the block controls regenerate button
@dkotter dkotter added this to the 0.2.0 milestone Dec 18, 2025
@dkotter dkotter self-assigned this Dec 18, 2025
@codecov
Copy link

codecov bot commented Dec 18, 2025 •
edited
Loading

Codecov Report

❌ Patch coverage is 50.00000% with 11 lines in your changes missing coverage. Please review.
✅ Project coverage is 47.96%. Comparing base (f21fd0c) to head (9474974).
⚠️ Report is 8 commits behind head on develop.

Files with missing lines Patch % Lines
...cludes/Experiments/Summarization/Summarization.php 50.00% 11 Missing ⚠️
Additional details and impacted files 
@@              Coverage Diff              @@
##             develop     #147      +/-   ##
=============================================
+ Coverage      47.93%   47.96%   +0.03%     
- Complexity       243      247       +4     
=============================================
  Files             22       22              
  Lines           1431     1453      +22     
=============================================
+ Hits             686      697      +11     
- Misses           745      756      +11
Flag Coverage Δ
unit 47.96% <50.00%> (+0.03%) ⬆️

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.

@jeffpaul
Copy link
Member

jeffpaul commented Dec 20, 2025

@dkotter perhaps a docs page for this experiment like done in https://github.com/WordPress/ai/pull/155/changes#diff-f70665388390657902e73741dea03efcdadc4bd0ceb4432959f8903ae015c042?

@jeffpaul
Copy link
Member

jeffpaul commented Dec 20, 2025

Note we'll want to update the screenshot numbers when this gets merged in, I left it with a hash instead of a number depending on when this versus other experiments get merged in.

@jeffpaul jeffpaul modified the milestones: 0.2.0, 0.3.0 Jan 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@dkotter dkotter

Labels

None yet

Projects

None yet

Milestone

0.3.0

Development

Successfully merging this pull request may close these issues.

Content Summarization

2 participants

@dkotter @jeffpaul