-
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
Image Block: Rename 'lightbox' feature to something more user friendly #52183
Comments
"Lightbox" has going for it a long history of specific semantic use. While it risks being jargony, that is also balanced by being recognizable and less ambiguous. |
I prefer 'expand' or 'enlarge'. I would actually go one step further and make it even more explicit by calling it 'Expand on click' (or 'Enlarge on click') in the UI select, so people reading it for the first time have a better idea of what this does. |
From a development perspective, I like that "lightbox" is concise and, from my perspective as a dev, pretty explanatory, at least code-wise, so perhaps leaving that in the code is for the best. @luisherranz Do you mean that we could just change the label to 'Enlarge on click' but leave the actual value in the dropdown as |
Keep in mind too that "lightbox" is not a term that come from software, but the software effect was built to mimic the effect of using a light box on some object. I only note this because the discussion sounds like a developer-vs-user conversation but the term itself comes more from the marketing and user end than it does from the software end. |
As far as I know, the best data we have on this is the 10+ years of lightbox plugins in the plugin directory, and pretty much most of them use "lightbox" in the title or description. There's a lot of history there, and I'd lean toward following what looks to already be working. With that in mind, I do like something like "Expand on click" when I start thinking about new users who are unfamiliar with the lightbox concept. |
No, that would be confusing for people that see In my opinion, the only thing that would be ok would be to call it |
My two cents: It may be because I am not used to these functionalities, but I wasn't aware of what "lightbox" meant before working on this project. In that sense, "Expand on click" seems clearer to me. I was wondering, is the "lightbox" term universal? Do non-English speaking users (not developers) understand the term "Lightbox"? Do you think "lightbox" will need to be translated into different languages? You might have more context than me, that's why I'm asking 🙂 |
I'm strongly voting for keeping it as lightbox. From a UX stand point I do not like "expand on click" for the following reasons:
|
Hi @pablohoneyhoney, do you by chance have any thoughts on this? This based on a suggestion you made that perhaps 'lightbox' wasn't a good indicator of the functionality a while back. |
My vote goes for keeping the lightbox naming, mainly because it's a widely adopted term in web development and, as Justin pointed out, especially in WordPress where we have 10+ years of plugins naming this same functionality as "lightbox". |
Agreed. Lightbox is likely the most familiar/understood convention for this behavior. |
Given all of the input so far, it seems like "lightbox" is a solid choice for moving forward. Will go ahead and close this. Thanks everyone! 🙏 |
We've been discussing how to surface this new setting in the site editor, and we've come to the conclusion that we don't need to use the "Lightbox" label in the settings panel. For more context see this comment. |
What problem does this address?
The image 'lightbox', as currently named, may be unintuitive and jargony. We should consider renaming the lightbox to something more user friendly.
What is your proposed solution?
I don't myself have many ideas for the moment, but perhaps something with 'expand' or 'enlarge' could work.
I'm also happy to go with 'lightbox,' but I understand there were varying opinions around this so thought I would open an issue to discuss.
The text was updated successfully, but these errors were encountered: