Woo · Hero with products

A shop hero in a white panel: a banner photo with a text card (h1, lead and button) and, beside it, a narrow column of recommended products in a vertical carousel of mini product cards with up and down arrows.

See it live: Woo · Hero with products on fancybricks.co — the live preview, and the button that copies it.

Or open the preview on its own — narrow the window to see it on a phone — and in dark mode.

Structure

This is what the Bricks Structure panel shows after you paste the template. Component instances say which component they are.

Woo · Hero with products
  Container
    Hero · Panel
      Banner
        Banner · Photo (decorative)
        Banner · Card
          Intro   (FBK Intro)
            Button · Primary   (FBK Button)
      Recommended
        Recommended · Header
          Recommended · Title
          Recommended · Arrows room (decorative)
        Recommended · Carousel
          Slide · Product loop
            Product card   (FBK Product card)

The template also pastes a dashed note above the section, with the short version of this page. It only shows inside the builder, never on the published page — see Builder notes.

How to adjust

Every step is the same move: pick the element in the Structure panel, change its Properties.

Where are those panels?

How to adjust a template shows every one of them in a screenshot of the real builder: the Structure and Properties panels, the classes on an element, a component's style families and the field where a CSS variable goes.

The classes this element carries, in the Bricks panel.

This template's own component, with its Style group open.

1. Paste the template in Bricks first — see Copy and paste.
2. Select Intro (FBK Intro) › Properties: Eyebrow, Hide eyebrow, Title, Title level, Lead, Hide lead · Style group: Eyebrow style, Highlight, Title size, Accent line · Layout group: Alignment, Layout, Background, Spacing · Motion group: Reveal in slider.
3. Select Button · Primary (FBK Button) › Properties: Text, Link, Tone, Shadow on hover · Icon group: Icon, Icon position · Style group: Style, Size, Width, Hover effect.
4. Select Product card (FBK Product card) › Properties: Show group: Hide category, Hide rating, Hide badges, Hide button · Style group: Look, Tone, Shape, Size, Title size · Layout group: Layout, Photo shape, Photo position, Rating position, Price style, Title level, HTML tag · Add to cart group: Button style, Button tone, Button icon, Icon only, Icon position, Button width, Button position, Quantity · Motion group: Photo hover, Card hover.
5. Select Recommended · Carousel › Content › Options (loop or fade, autoplay, items per page, gap), Arrows and Pagination; one slide = one child, duplicate it to add more.
6. Select Slide · Product loop (query loop) › Query: post type, number of posts, order and filters.
7. Spacing, sizes, color and timing with no property of their own: the CSS variables below.

CSS variables

These are the only values in the template meant to be changed by hand. Copy the block, paste it, edit the numbers.

The Custom CSS field of this template's own element, with one of its variables as a real example.

/* «Hero · Panel» · class .fbk-heroprod */
.fbk-heroprod {
  /* white in light, the dark surface when the site is dark (in CSS: a var()
     fallback breaks in a native control) */
  --fbk-t-aside: 1.4fr;
  --fbk-t-list: 26em;
  /* the carousel's up and down arrows: a step under the house size (a narrow
     column) */
  --fbk-slider-size: 2.25em;
}

Paste the block in the element's Style → CSS field (the selector is already in it), or set the same variables on the class itself to change every copy at once. The values are your framework's variables, so they follow your site: Choosing a framework.

Requirements

• WooCommerce. Needs WooCommerce active, with the products/fields this template queries already set up.

What each requirement is, and how to set it up once for the whole site: Requirements.

Finish by hand

• Replace the banner photo (Banner · Photo) and the title, lead and button of the card.
• Products: the query loop is on Slide · Product loop (one slide per product): featured products (Products > star a product), nine of them. Remove the featured condition (Query > Taxonomy query) to show the latest products.
• How many show at once: perPage in the carousel options (4); the list's height is --fbk-t-list and the column's width --fbk-t-aside, both on .fbk-heroprod.
• Card options are on Product card (component): Compact · Horizontal · Plain, with a text-link button and the long arrow after it.

On phones

The template is designed desktop first, the Bricks default, and only changes at the two widths the library uses:

• 991px and below — .fbk-heroprod, .fbk-intro.
• 767px and below — .fbk-heroprod__banner, .fbk-pcard, .fbk-section.

Those changes live in Bricks' own breakpoint fields, so you edit them where you always do: pick the breakpoint in the toolbar and the same fields follow.

Careful with the classes shared by the whole library (fbk-section, fbk-intro, the component classes): a change there shows up in every template that uses them.

If your site's breakpoints are set up mobile first, copy the mobile-first variant of the template instead — see Copy and paste.

Accessibility

In this template, keyboard focus is visible on every interactive piece; movement is cut back when the visitor's system asks for less motion; the state screen readers need is already set (aria-hidden, aria-label).

What is checked on every template, and what depends on your own palette: Accessibility.

Dark mode

With your site in dark mode this section turns dark too — the class fbk-section--auto-dark on the section does it. Remove the class to keep it light.

Its background is a modifier on the section, so you can swap it for any of the ones the template is checked with: fbk-section--soft, fbk-section--light, fbk-section--dark.

How the library follows your site's color scheme: Dark mode and preview.

Replaces

• 01 - Woocommerce Hero from Fancy Bricks 1.0

What happened to the old libraries, and what to do with pages already built with them: Migrating from 1.0/2.0.