Skip to main content

Hero · Text layer

A huge name runs across the screen and through a central photo: solid outside the photo, outlined over it. A button over the photo fans out two photos behind it on hover. The H1 and lead sit below.

Hero · Text layer

Full-page views: desktop, phone and dark mode

Hero · Text layer, desktop at 1440px wide

At 1440px wide.

Hero · Text layer, on a phone at 390px wide

At 390px wide.

Hero · Text layer, with the site in dark mode

With your site in dark mode.

See it live: Hero · Text layer 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 name does not run here and the pause button is hidden (the builder does not run the code). 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 · Text layer
Brand slot (decorative, empty)
Container
Intro (FBK Intro)
Stage
Running name
Name
Name
Button (FBK Button)
Photo behind 1 (decorative)
Photo behind 2 (decorative)
Photo frame
Photo
Name over the photo (window)
Window · Counter-tilt
Running name (over the photo)
Name
Name
Pause button
Toggle · Pause icon
Toggle · Play icon
Motion · Pause script (needs Execute code)

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 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 (FBK Button) › Properties: Text, Link, Tone, Shadow on hover · Icon group: Icon, Icon position · Style group: Style, Size, Width, Hover effect.
  4. 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.

/* «Stage» · class .fbk-textlayer */
.fbk-textlayer {
/* The running name: size, how high it crosses the photo (share of its
height), time for one pass */
--fbk-t-size: clamp(4.5em, 12vw, 11em);
--fbk-t-top: 18%;
--fbk-t-time: 40s;
/* Color of the name over the photo, darkness of the photo */
--fbk-t-front: var(--white);
--fbk-t-shade: 30%;
/* Photo width; how far the photo tilts on hover, and the photos behind on
top of that */
--fbk-t-width: 40em;
--fbk-t-tilt: 5deg;
--fbk-t-fan: 8deg;
}

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​

  • The running name is decoration (hidden from screen readers): change it in both rows (Running name and Running name (over the photo)), two copies each, all four the same text.
  • Size, height over the photo and speed: --fbk-t-size, --fbk-t-top and --fbk-t-time on .fbk-textlayer. The run is in .fbk-textlayer__row (Style > CSS).
  • Over the photo the name is solid white (--fbk-t-front): it works with any font. For an outline instead, add the class fbk-textlayer--outline to the Stage, but only with a font drawn without overlapping strokes (many variable fonts show their inner strokes in outline). The name over the photo sits in its own window: the window tilts with the photo and turns its content back, so the name always runs straight.
  • Fan on hover (the photos behind open, the photo tilts and comes closer; also with the keyboard): .fbk-textlayer--fan (remove it for still photos). The button's hover is the FBK Button effect Sweep. The pause button is required while the name runs (WCAG 2.2.2); it needs "Execute code".
  • Replace the three photos; only the central one needs an alt text. Change the name in both rows (four copies, the same text).

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

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

Replaces​

  • Hero - Text layer 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.