Elements · Overflow carousel

A centered intro and a carousel of cards that runs past both screen edges and plays on its own; under it, segments that fill as each card plays, a pause button and the arrows.

Full-page views: desktop, phone and dark mode

At 1440px wide.

At 390px wide.

With your site in dark mode.

See it live: Elements · Overflow carousel 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 segments stay empty and the pause button does nothing here (both need the script). 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.

Overflow carousel
  Container
    Intro   (FBK Intro)
    Carousel + pause
      Carousel
        Story · A morning above the lake
          Story · Photo
          Story · Title (link)
          Story · Excerpt
        Story · Finding the hidden falls
          Story · Photo
          Story · Title (link)
          Story · Excerpt
        Story · Three days in the valley
          Story · Photo
          Story · Title (link)
          Story · Excerpt
        Story · The coast road, slowly
          Story · Photo
          Story · Title (link)
          Story · Excerpt
        Story · Driving the empty road
          Story · Photo
          Story · Title (link)
          Story · Excerpt
        Story · A day at the reserve
          Story · Photo
          Story · Title (link)
          Story · Excerpt
      Pause button
        Toggle · Pause icon
        Toggle · Play icon
    Carousel · autoplay progress and pause (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 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 Carousel › Content › Options (loop or fade, autoplay, items per page, gap), Arrows and Pagination; one slide = one child, duplicate it to add more.
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.

/* «Carousel» · class .fbk-overflow */
.fbk-overflow {
  /* Stories peeking past the edges: fainter and a little smaller */
  --fbk-t-side-opacity: 0.35;
  --fbk-t-side-scale: 0.9;
  /* Controls row under the cards */
  --fbk-t-controls-gap: var(--space-m);
}

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 photos (decorative: the title names the story, so alt stays empty) and link each title to its post.
• Add or remove cards by duplicating a slide; each one adds a segment. Keep at least four.
• Time per card: "interval" in the slider options. The filling segments and the pause button need "Execute code" enabled for the role; without it, autoplay still runs.
• Edge stories: --fbk-t-side-opacity and --fbk-t-side-scale on the carousel (.fbk-overflow). The in-view and edge states are in the Custom CSS of the story class .fbk-overflow__slide (Style > CSS): %root%:not(.is-active):not(.is-next) are the stories at the edges (photo only), %root%.is-next the second one in view.

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-overflow, .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

• 11 - Overflow carousel 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.