Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Required label: Any label starting with [Type].
• Labels found: [Type] Enhancement, [Type] Copy, Connectors screen.

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

Size Change: 0 B

Total Size: 7.66 MB

_{compressed-size-action}

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: t-hamano <wildworks@git.wordpress.org>
Co-authored-by: gziolo <gziolo@git.wordpress.org>
Co-authored-by: jorgefilipecosta <jorgefilipecosta@git.wordpress.org>
Co-authored-by: jeffpaul <jeffpaul@git.wordpress.org>
Co-authored-by: dkotter <dkotter@git.wordpress.org>
Co-authored-by: justlevine <justlevine@git.wordpress.org>
Co-authored-by: jonathanbossenger <psykro@git.wordpress.org>

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

Flaky tests detected in f9882bb.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/23438847953
📝 Reported issues:

• [Flaky Test] post title and content are editable and blocks can be inserted #76524 in /test/e2e/specs/editor/various/post-content-focus-mode.spec.js

On this scenario where there is no connector connected the banner says: "The AI plugin is installed. Connect a provider below to generate featured images, alt text, titles, excerpts, and more. " but then we include a button "Enable features in the AI plugin". I think the button should only appear after a connector is connected otherwise we have to calls to action one to enable AI features another to connect.

We could also apply the @gziolo suggestion as if we say Control, the issue is not as prominient.

But I think the ideal UX would be to enable some features by default, and not force users to go to yet another settings page to get a feature working.

We're not enabling RTC by default in this release, so I don't see why we should enable something by default from a plugin either.

Thanks for the review! Is there anything I should update in this PR before merging?

But I think the ideal UX would be to enable some features by default, and not force users to go to yet another settings page to get a feature working.

We're not enabling RTC by default in this release, so I don't see why we should enable something by default from a plugin either.

It would still not be enable by default for WordPress users, user would explicitly press a button to install activate ai features, and connect a provider to get AI features. I think pressing the button and connection some provider is already enough optin, I don't see the reason to besides doing that also need to go to a settings page and enable the AI features. Like people already pressed install to get them, connected a provider why make then need to go to a other place?

In that case, I'd want VERY SPECIFIC copy on the button label noting what's going to be enabled. We cannot break user trust here, especially for sites with more than 1 user where their AI usage costs would jump noticeably if lots of users started generating images etc.

RC1 is being released today, so can we merge this PR as is?

We cannot break user trust here, especially for sites with more than 1 user where their AI usage costs would jump noticeably if lots of users started generating images etc.

This is a separate discussion, but we might need to add some kind of warning to the AI plugin itself.

We definitely have to land it today. We can always follow up if there is agreement to change wording.

Okay, for now let's merge this and consider it again in the follow-up.

I just cherry-picked this PR to the wp/7.0 branch to get it included in the next release: 17ed7be