-
Notifications
You must be signed in to change notification settings - Fork 219
Product Elements: Make sure design tools and global styles work well with element blocks #8086
Comments
ApproachI approach the research by checking the styles application on a three levels:
Design controls on a Product Elements levelI didn't find any problems with style applications here if the element allows changing some styles. However, there's a quite big inconsistency in what particular elements allow to change, e.g. Sale badge
Suggestion: even though design controls are working correctly, seems like such inconsistency can be an improvement point. Appearance vs Font weight
Suggestion: once again, there's no bug per se, but the options could be aligned. Product SKU
Suggestion: expose design controls on the element level for consistency. There are more examples like that, which I believe are important to address for a better UX, however, before proceeding and addressing or creating issues for them, I'd like to consult the general guidelines:
Design controls of Product Template (should be inherited by Product Elements)There are a number of bugs in this area, which will be assessed case by case (either addressed or issue created). They are gathered in the table below (
Global stylesTBC - the same exercise as above will be performed |
Hey, @kmanijak, I appreciate the thorough research you conducted on design controls. It is very well-written and organized. 🙌🏻
Just to confirm, are you proposing that
To me, it's kind of feature because user can change Typography settings for both from Product Template level. Also, User can change Typography settings individually on
It makes sense to me 🤝
Agreed that we should also have controls on the element level.
As per my discussion with @sunyatasattva, the aim of this issue is to make sure all product elements have the correct design tools, fix small things, and report the rest. AFAIK These inconsistencies fall into the scope of this task but I am not 100% sure if we should prioritize these over other tasks. Maybe we can fix inconsistencies that are quick to fix & report the rest.
I am not sure about this. Maybe @sunyatasattva can comment on this? |
Firstly I think you've done a great job at highlighting the inconsistencies between all the blocks/product elements and asked some pretty important questions @kmanijak! On top of that, the format you've communicated them in is so easy to digest! I personally think this deserves some input from UX/design to help guide us in how to address these inconsistencies. As for my two cents: Sale Badge
Regarding sale badges you've highlighted some good points around some elements such as the Sale Badge. Ideally anything that can be styled on the Sale Badge block should be available on the sale badge within the Product Image because from a users perspective they are the same thing and serve the same purpose, so should be able to be customised in the same way. Appearance vs Font weight
Regarding typography settings, these should be consistent across all blocks with typography available to allow the user that granular control over how their typography looks, whether thats on the product element block, product template block or both. I don't see a use case for where we would only make some typography settings available in some product element blocks, and not others? Open to being wrong here. Product SKU
Again, I think my above point covers this in terms of typography settings. Especially if it's reactive to the Product Template settings. Product TemplateI think another point worth raising is why does the Product Template offer only font size settings and not style/weight/color etc? To us working within the detail of the block we might easily be able to explain this away but from a users point of view it is quite confusing. Again, this is valuable information you've highlighted as this kind of flexibility and customisation is what we want to offer our merchants/users and will make the difference in terms of user experience! Thanks again @kmanijak and @imanish003!
I agree with this, lets work out what is the most important to fix based on the time and resource we have. |
Thank you both for the responses! 🙌 I see we all agree that consistency and flexibility for merchants are important, so I'll keep that in mind when working further on this task.
Apologies if some areas of my post were misleading. To clarify this one, Product Template allows changing the whole set of Typography and Color settings (as per screenshot below), but many Product Elements don't react to these changes. Also, I realized that change applied in the Editor doesn't mean it works in the frontend 😅 so that extends the research a bit. But I believe it will bring a lot of value to recognize the gaps and untangle these settings! |
My bad, by default the product block only exposes font size unless I enable the others hidden behind the Typography menu of the block, probably another issue to address maybe. |
Oh, I assumed the options are hidden by design 🤔 but I cannot find a good reason for that. I didn't consider it an issue until you pointed it out, I'll raise an issue for that as well! 🙌 |
Testing approachThe approach was the following. Each block was checked:
Outcomes - spreadsheetThe outcome of the research has been gathered in a Google Spreadsheet Outcomes - epic and issuesAs a result, I created a bunch of issues. To avoid polluting the main Products epic, I decided to create a new one that would gather all of them: woocommerce/woocommerce#42443 There are 23 issues, divided into three “categories”. Each issue is per single Product Elements
Issues cover Colors and Typography options. They don’t cover Dimensions (Margin, Padding) and Border (Width, Radius), which can be improved as a next step. Ref: pdnLyh-3kh-p2 |
This issue represents a research spike to make sure that all design tools available in the inspector controls and global styles work correctly for Product Elements blocks within the context of the “Products (Beta)” block.
If an issue is small enough, please do fix it in the context of this issue, otherwise, feel free to create another issue and add it to the Epic (#6793).
The text was updated successfully, but these errors were encountered: