[WIP] feat/489: Add Rewrite Tone feature

[Sidsector9]

Description of the Change

Closes #489

Screencast

The Tone Rewriting options are preserved in local storage so that the admin does not have to perform the same selection every time.

Screen.Recording.2025-03-03.at.4.57.22.PM.mov

How to test the Change

Changelog Entry

Added - Rewrite Tone feature.

Credits

Props @jeffpaul @Sidsector9

Checklist:

• I agree to follow this project's Code of Conduct.
• I have updated the documentation accordingly.
• I have added Critical Flows, Test Cases, and/or End-to-End Tests to cover my change.
• All new and existing tests pass.

[dkotter]

I agree that the Chat UI experience should be part of a top-level ClassifAI plugin component that features could inherit into. And if no features are enabled that utilize the ChatUI, then it won't appear in the editor. But having the ChatUI exist within the Content Generation feature that other features like Rewrite Tone need to inject into feels sub-optimal.

Yes, this is correct. We'll need to refactor the code that renders the experience right now to make it not dependent on the Content Generation Feature. My thought would be to go with the slotfill approach where each Feature can register what they need within the experience (and properly enqueue that) and then each Feature will also be responsible for enqueuing the default ChatUI code (with WordPress being smart enough to not load that multiple times if multiple Features are in use)

[Sidsector9]

My thought would be to go with the slotfill approach where each Feature can register what they need within the experience (and properly enqueue that) and then each Feature will also be responsible for enqueuing the default ChatUI code (with WordPress being smart enough to not load that multiple times if multiple Features are in use)

@dkotter This is exactly how it is currently implemented. If you disable Content Generation but keep Rewrite Tone enabled, the ChatUI would still show, but the downside to this approach is that it makes it difficult to implement the UI that Fabian is suggesting.

[jeffpaul]

Noting optimal approach for 3.8.0 is to add this functionality in via button iteration on block toolbar / top toolbar / sidebar panel. In future release we can consider a chat-based experience, but for now looking to have this function in-context within the authoring/editing experience is the preference.

[github-actions]

@Sidsector9 thanks for the PR! Could you please rebase your PR on top of the latest changes in the base branch?