Replies: 1 comment 5 replies
|
Hi @Hlavtox, I think this is a good idea, but I’ve identified a few drawbacks. Currently, in Hummingbird v2, subcategories are displayed only on small devices. The reason is that in the Back Office, we don’t have the possibility to choose whether we want to display subcategories or not. On many websites, displaying subcategories at the top of the category page is not always desirable, especially for stores with a large number of subcategories. Displaying them on mobile only, in a single horizontal line with scrolling, was a good compromise, since the category module is frequently enabled on stores. That said, as you mentioned, for some websites, your car parts store example is a good one, navigation with subcategories (especially with images) can be very beneficial. In those cases, it really helps users find what they need faster. It’s almost like a step-by-step search. However, I strongly believe we are missing a configuration switch in the Back Office to control whether subcategories should be displayed or not. Without this, it’s difficult to find a solution that fits all use cases. What do you think? More generally, I think a small global configuration page should be implemented, for example, under Shop Parameters → Theme Settings, to introduce conditional rendering options like this. To sum up, I don’t think we can go much further without having a conditional switch in the Back Office. What do you think @Hlavtox, @ga-devfront ? |
Uh oh!
There was an error while loading. Please reload this page.
The problem
Depending on a merchant and product sortiment, there are often categories where you just don't need a thumbnail, or it would not bring additional clarity, or good ones are just not available. It would make the theme more universal. :-)
It often looks something like this.
The solution
In category-header.tpl where subcategories are defined, we could possibly do a small tweak. Display the images only if at least category has a thumbnail.
Then it would look like this, in the example category.
What do you think guys? @tblivet @ga-devfront
Additional context
Technically, something like:
Do you plan to work on this subject?
All reactions