Skip to main content

Hero · Word card

Over a darkened full-bleed photo: the H1 and lead on the left, and on the right a tall white card with a label, huge words that run into a sentence and a brand-colored diagonal fill that slides away on hover.

Hero · Word card

See it live: Hero · Word card 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.

In the builder

Preview on the front end. Scripts don't run inside the builder, so here you only see the layout: the pause button of FBK Hero only works on the front end. 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.

Hero · Word card
Container
Hero (FBK Hero)
Hero · Photo (background, decorative)
Hero grid
Intro column
Intro (FBK Intro)
Card
Card · Eyebrow
Card · Big words
Card · Line
Card · Action
Card · Button (FBK Button)

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.

The classes this element carries, in the Bricks panel.

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

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

  1. Paste the template in Bricks first — see Copy and paste.
  2. Select Hero (FBK Hero) › Properties: Style group: Layer, Text colors · Layout group: Height, Content position, Width · Motion group: Effect, Time per photo.
  3. 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.
  4. Select Card · Button (FBK Button) › Properties: Text, Link, Tone, Shadow on hover · Icon group: Icon, Icon position · Style group: Style, Size, Width, Hover effect.
  5. 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.

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

/* «Hero grid» · class .fbk-wordcard */
.fbk-wordcard {
/* Height of the hero */
--fbk-t-height: max(34em, 70svh);
/* Width of the card */
--fbk-t-card-w: 22em;
/* Color of the diagonal fill (the button over it is white) */
--fbk-t-fill: var(--primary);
/* How high the fill's edge runs (share of the card's diagonal, from the
lower end corner) */
--fbk-t-edge: 42%;
--fbk-t-reveal: calc(var(--fbk-hover) * 3.5);
}

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​

  • 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​

  • Replace the photo in the hero's Background slot (decorative, at least 1600 px wide).
  • The card: Card · Eyebrow (the house Pill outline eyebrow), Card · Big words and Card · Line (they read as one sentence: We are constantly seeking out new opportunities.). The button sits in the card's lower corner (.fbk-wordcard__action).
  • Height of the hero --fbk-t-height, width of the card --fbk-t-card-w, color of the fill --fbk-t-fill and how high its edge runs --fbk-t-edge, how long it takes to slide away --fbk-t-reveal: on .fbk-wordcard. The fill is %root%::before of .fbk-wordcard__card (Style > CSS).
  • On hover (or keyboard focus inside) the fill slides away: the class fbk-wordcard__card--reveal on the card; remove it for a fixed fill. The button is white over the fill and turns back to the house primary when the fill slides away (variables on .fbk-wordcard__action, set in .fbk-wordcard__card and its --reveal class); if you change the fill color, change those too.
  • The button's hover is the FBK Button effect Sweep.

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-intro.
  • 767px and below — .fbk-wordcard, .fbk-wordcard__card, .fbk-wordcard__intro, .fbk-hero, .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​

This section is dark on purpose (class fbk-section--dark), so it looks the same whether your site is in light or dark mode.

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

Replaces​

  • 05 - 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.