-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Improve block inserter #34
Comments
Interesting idea, thanks for sharing a mockup also 🌟 The design is definitely in need of further love. The most recent mockup looks like this: Maybe it does need to be bigger, I know @melchoyce has some thoughts on this as well. Probably prudent to keep in mind though: there are many (once all is said and done it's likely there will be 50+ outside of plugins alone), so we can't possibly show them all (which is why there are emoji-like tabs in that mockup). The balance we need to find is between showing a big friendly insert dialog that's keyboard accessible (type |
I really like the idea this takes up more space. I feel the current implementation is a little small. I understand wanting it to be minimal and I'm not totally sold on it being full width either. I think exploring different sizes would be great. We probably also increase accessibility for users as we make larger. |
This inserter will likely undergo iterations as well, hence this ticket is valuable. I know that both @melchoyce and @folletto have thoughts on how to improve this. |
I've a couple of hypothesis, but more in general I'd try to explore a set like:
I lean more toward 4-5-6 because:
|
Took the liberty of renaming the ticket to be the canonical "inserter improvements" ticket. |
Please see also #323, as that will be the task ticket for the inserter. Edit: actually closing this one to keep all the conversation on a single ticket. |
tests: Use the generic domain `example.com` in tests
…perty iOS: Expose and wire onChange propType for Aztec.
If more options are available, changing the width of the .insert-block__menu feels like a better experience.
The text was updated successfully, but these errors were encountered: