...
You can override this mechanism by providing specific template to use by given category (i.e. using rule #1). The following template keys can be used out of the box from the default storefront theme.
| Template | Version | Description | ||||||
|---|---|---|---|---|---|---|---|---|
| products | 3.0.0+ | Default behaviour (category with products), display products listed in this category | ||||||
| category | 3.0.0+ | Default behaviour, display category description in the page's main body | ||||||
| subcats | 3.0.0+ | Default behaviour (category with sub categories), display category description in the page's main body | ||||||
| catcontent |
| Uses category description field as placeholder for content URI. Body of this content is displayed in page's main body |
| Tip |
|---|
| Custom themes can define more templates that can provide alternative behaviours |
...
The following configurations are available:
| Configuration | Version | Description | ||||
|---|---|---|---|---|---|---|
| brands | up to
|
| flag enables brands filtered navigation block. Brand values are accumulated from products that are assigned to given category (and its sub categories if "search in sub categories" flag is enabled). Note that in versions 3.4.0+ brand value is "proxied" by brand attribute so that it can be added to generate attributes filter navigation block and thus use some of the features such as sorting and alternative naming | ||
| price | flag + per currency price range settings enable price filtered navigation block. The configurations are set using "price tiers edit" button. The tiers have to be set for each currency separately. This is not limitation of YC but rather best practices approach. Business marketing department has to set correct ranges for product prices that will be balanced and will be suitable to target customer groups. For example if there are many products grouped with middle tier prices it would make sense to create "up to X" price range, then make granular ranges for middle range prices and then last range to have "more than X". Another reason is there are sometime "gaps" in price ranges thus creating 0 counts, so marketing department may choose to group this range with adjacent one to prevent 0 value ranges. Sometimes it makes sense to create different ranges based currency since currency may refer to geo location customer group with different price perception due to local mentality. Price range counts are accumulated from products prices that are assigned to given category (and its sub categories if "search in sub categories" flag is enabled). | ||
| attributes | flag enables attribute filtered navigation blocks that require default category product type to determine which attributes should be part of the navigation. For each attribute a separate navigation block will be created subject to sorting and navigation rules defined by selected product type. Attribute values are accumulated from products that are assigned to given category (and its sub categories if "search in sub categories" flag is enabled). |
Attributes
As stated in the attributes management section attributes allow to add additional data to category object. Some of these represent flags and configurations used on the storefront.
| Attribute | Version | Purpose | ||||||
|---|---|---|---|---|---|---|---|---|
| Category Description (multiple attributes) | 3.0.0+ | Allows to set long descriptions that are language specific. In default theme this is used by simple category rendering template as body of the page | ||||||
| Quantity of featured items | 3.0.0+ | Number of products in featured item component. In default theme this is used by category featured products template | ||||||
| Quantity of new arrival items | 3.0.0+ | Number of products in new arrivals tab. In default theme this is used by category new arrival tab template | ||||||
| New arrival tag days offset | 3.0.0+ | Number of days in the past for product to be identified as new arrival product if it does not have "newarrival" tag. In default theme this is used by category new arrival tab template to determine which products to show | ||||||
| Items per page CSV | 3.0.0+ | Pagination settings for category with products. In default theme this is used by product lister category template to display options for number of products to be displayed on a single page | ||||||
| Category sort options CSV | 3.0.0+ | Product sorting settings for category with products. In default theme this is used by product lister category template to display options for products sorting for listing or search result | ||||||
| Search include sub categories | 3.0.0+ | Flag that allows to alter search engine behaviour. If this is set to "on" then listing or searching products in this category will also include products from sub categories. | ||||||
| Quantity of category pods in one row on category page | 3.1.0+ | Quantity of product pods in one row to show on category page | ||||||
| Quantity of category pods in one row on category page | 3.1.0+ | Quantity of category pods in one row to show on category page | ||||||
| Filter navigation records limit | 3.2.0+ | Filter navigation records limit per group. Default is 25. If there are less records than limit they are alphabetically sorted, otherwise sorted by most hits descending and over the limit are discarded | ||||||
| Flag to exclude this category from meganav |
| Used by YCE default theme to skip this category when rendering mega nav |