Proposal: Add ClassifAI button in the editor Toolbar
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reviewing the Gutenberg Block Toolbar and Editor Toolbar entry points, then compare how the existing Content Resizing and Rewrite Tone controls are exposed through the Block Toolbar and Document Panel. Done means an extendible toolbar area makes those multi-block controls available when different block types are selected, without requiring a switch to the Document/Post panel.
Written by the indexing model from the issue text.
Description
Is your enhancement related to a problem? Please describe.
Currently the Content Resizing and Rewrite Tone features only work on multiple blocks if and only if the blocks selected are of the same type.
This is due to the limitation that Gutenberg doesn't display the button added to the Block Toolbar when multiple blocks of different types are selected.
Example:
Same types:
Different types:
We can add buttons to the Document Panel but this introduces poor UX when multiple blocks are selected.
- When multiple blocks are selected, the "Block" panel is selected by default.
- The user has the click the "Document/Post" panel to access the ClassifAI panel.
Designs
I propose adding an extendible plugin area at the top inside the Editor Toolbar like the following:
https://github.com/user-attachments/assets/2961ca1f-8a99-4b24-b3b3-e706383d0dfa
In the example, I have added the controls for the existing features, but in practice this will contain controls for features like Content Resizing, Rewrite tone and any feature that has to work on multiple blocks.
@10up/open-source-practice open to hear your thoughts on this!
Describe alternatives you've considered
No response
Code of Conduct
- I agree to follow this project's Code of Conduct
- Dominant language
- PHP
- Stars
- 714
- Forks
- 68
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 23
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from 10up/classifai
-
wpvc
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
wpvc
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Register ClassifAI functionality with the Abilities APIPossibly taken @nhrrob claimed this 10 days ago. Openhelp wanted
Difficulty 4/5 3-5 days Newbie friendliness 48/100
10up/classifai#1249 · 1 assignee ·
Maintainers usually reply within 1 day
-
OpenAI usage tracking: Project ID setting is ignoredPossibly taken @dajiaohuang claimed this 30 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
BYOK Openai modelsOpen
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
Exclude module `require-dev` and `autoload-dev` from the generated `composer.json`Possibly taken @keiserjb claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
uiowa/uiowa#10310 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mailcow/mailcow-dockerized#7677 · 1 comment ·
Maintainers usually reply within 1 day
-
a11y
Difficulty 2/5 1-3 hours Newbie friendliness 67/100