-
Notifications
You must be signed in to change notification settings - Fork 22
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.
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
[Spike] Action Menu on text highlight #9425
Comments
@Pashaminkovsky I recommend we put the UX considerations through a PRD. There's a lot to sort out with how this feature interacts with other features and how mods interact with each other. Or are you just looking for engineering to determine the feasibility for adding a draggable floating panel to the page? The kinds of things to sort out are:
|
This was my understanding. Also, is "draggable" a requirement? That wasn't clear to me based on the description |
Correct this is a feasibility spike; we'll have the PRD once we sync w/ customer on their requirements.
"Draggable" is in scope for this spike; I added it more explicitly to acceptance criteria of the spike. TBD whether it is actually a requirement for customer. cc @fungairino
Correct, this was my assumption as well. Based on what we've heard so far about the customer reqs I think this suffices and would be simplest to maintain. |
|
Motivation
We're looking to improve AI writing, translation, and summarization mods. The goal of this spike is to gauge the complexity of implementing an "Action Menu" similar to what Grammarly and moly.ai have implemented (see screenshot below).
The ideal flow would be:
Note: Compatability with Google Workspace is out of scope, the screenshot is meant to highlight the Action Menu.
The Action Menu would appear as an option in the "New Mod" selection in the Page Editor, and would be mutually exclusive with the Text Selection Menu (emojis that appear on highlight).
The exact naming of "Action Menu" is tbd -- we're open to suggestions.
Acceptance Criteria
Timebox
8 hours
The text was updated successfully, but these errors were encountered: