Header · Shop

A shop header in two rows: the logo, a live product search (matching products appear under the field as you type, with photo, name and price), the support phone, the account link and the mini cart; under it, a band with Categories (every product category with its subcategories in a large dropdown) and the menu.

Full-page views: desktop, phone and dark mode

At 1440px wide.

At 390px wide.

With your site in dark mode.

See it live: Header · Shop on fancybricks.co — the live preview, and the button that copies it.

In the builder

Preview on the front end. Scripts don't run inside the builder, so here you only see the layout: the search shows its first products under the field here; on the front end the results panel opens over the page only while you type (3 letters or more), and the cart and the categories open there. Save and open the page to see the full result.

Structure

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

Header · Shop
  Container
    Header · Shop row
      Nav · Logo
      Product search
        Product search · Field row
          Product search · Icon
          Product search · Field
        Product search · Count
        Product search · Results
          Product search · List
            Product search · Result
              Product search · Card   (FBK Product card)
          Product search · Foot
            Product search · See all
      Header · Tools
        Header · Support
          Header · Support label
          Header · Support number
        Header · Account
          Header · Account icon
        Header · Mini cart
    Nav
      Nav · Brand
        Header · Categories
          Categories · Panel
            Categories · Grid
              Categories · Category
                Categories · Category link
                Categories · Subcategories
                  Categories · Subcategory
                    Categories · Subcategory link
            Categories · Foot
              Categories · Shop all   (FBK Button)
      Nav · Menu
    Header · Cart and search keyboard (JS)

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 Product search · 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.
3. Select Categories · Shop all (FBK Button) › Properties: Text, Link, Tone, Shadow on hover · Icon group: Icon, Icon position · Style group: Style, Size, Width, Hover effect.
4. Select Product search · Field › Content › Target query: the query loop it filters.
5. Select Nav · Menu › Content › Menu: pick your WordPress menu (Appearance › Menus).
6. Select Product search · Result (query loop) › Query: post type, number of posts, order and filters.
7. Select Categories · Category, Categories · Subcategory (query loop) › Query: taxonomy, number of terms and order.
8. 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.

/* «Header · Shop row» · class .fbk-hshop */
.fbk-hshop {
  /* Widest the search field gets (it sits in the middle of the row) */
  --fbk-hshop-search-w: 36em;
}

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.
• Code execution. Needs "Execute code" enabled for the role in Bricks → Settings → Custom code, or the JS block shows as plain text instead of running.

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

Finish by hand

• Product search: turn on Bricks > Settings > Performance > Query filters, then save this template once in the builder so the search starts filtering. Product search · Field is a Bricks Filter - Search bound to the query loop Product search · Result (products, 5 at a time, Live search on): as you type (3 letters or more) Bricks fetches the matches by AJAX and shows them in Product search · Results under the field; a click outside or an empty field hides it. Each result is an FBK Product card (Horizontal, Compact; change its properties there). Enter and See all results open the WooCommerce search results page (the filter's URL parameter is s; Redirect to on the field and on See all is /?post_type=product). The script adds Escape and the arrow keys.
• The results panel (Product search · Results) is hidden in the builder so it doesn't cover the header while you edit: to see or style it, click the eye icon next to it in the Structure panel (Hide in builder), then click it again when you are done. It always works on the front end.
• If the search field is missing in the builder, your user role needs the Filter - Search element: Bricks > Settings > Builder access (the builder says lacks the add_element_filter-search builder permission).
• Mini cart: Bricks' Mini cart element with the house look (class fbk-woo-minicart; dropdown width --fbk-woo-minicart-w). It opens each time a product is added with Bricks > Settings > WooCommerce > AJAX add to cart on (Open on add to cart on the element).
• Categories: a Bricks Dropdown with Mega menu (as wide as the bar). Categories · Category loops over the top-level product categories (empty ones hidden), Categories · Subcategory over the children of each one (up to 6); change the number or the order in their Query. It opens on hover or click.
• Account: Header · Account links to the WooCommerce My account page (log in or the dashboard).
• Support phone: Header · Support (set its link to your tel: number); it hides on phones.
• Hover effects (on by default): the classes fbk-nav--line (a line grows under each menu link) and fbk-nav--sub-line (submenu links) on Nav; remove them to turn them off.
• This header is FBK Header unlinked: the same elements and classes as the component, as plain elements (Bricks can't run a live search inside a component slot: it renames the results loop but not the search field's target). Header · Shop row is the row over the bar, Header · Categories sits in Nav · Brand and the menu in Nav. Its options are classes on Nav (fbk-nav--band: the soft band; sticky: add fbk-nav--sticky) and on the section (fbk-section--light).
• The menu is the Bricks Nav Menu (Nav · Menu): pick your WordPress menu in its settings (Menu). Here it shows the demo menu Fancy Bricks demo, with submenus and sub-submenus; on your site, until you pick one, Bricks shows one of your menus. Its sizes and colors are Nav Menu settings saved in the class .fbk-nav__menu (Top level, Sub menu, Mobile menu).
• This is a Bricks header template: in your site set where it shows (Template settings > Conditions), or paste its section into your own header template.

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-nav, .fbk-nav__menu.
• 767px and below — .fbk-hshop, .fbk-hshop__catgrid, .fbk-hshop__support, .fbk-nav__menu, .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-atomic, aria-hidden, aria-label, aria-live).

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--light, fbk-section--dark.

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

Replaces

• 01 - Woo header from Fancy Bricks 2.0

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