Skip to main content

Elements · Fullscreen slider

One large photo per view across the full width. Each photo opens from a strip, then its title, text and button come in. It plays on its own: the dashes on the right fill as each slide plays; arrows with a progress bar and a pause button at the bottom.

Elements · Fullscreen slider

Full-page views: desktop, phone and dark mode

Elements · Fullscreen slider, desktop at 1440px wide

At 1440px wide.

Elements · Fullscreen slider, on a phone at 390px wide

At 390px wide.

Elements · Fullscreen slider, with the site in dark mode

With your site in dark mode.

See it live: Elements · Fullscreen slider 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 progress bar and the dashes stay empty and the pause button does nothing here (they need the scripts). 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.

Fullscreen slider
  Container
    Slider + progress
      Slider
        Slide · Guatapé
          Slide · Photo
          Slide · Content
            Slide · Intro   (FBK Intro)
              Slide · Button   (FBK Button)
        Slide · Open roads
          Slide · Photo
          Slide · Content
            Slide · Intro   (FBK Intro)
              Slide · Button   (FBK Button)
        Slide · Hidden falls
          Slide · Photo
          Slide · Content
            Slide · Intro   (FBK Intro)
              Slide · Button   (FBK Button)
        Slide · Quiet valleys
          Slide · Photo
          Slide · Content
            Slide · Intro   (FBK Intro)
              Slide · Button   (FBK Button)
      Progress bar
        Progress · Fill
      Pause button
        Toggle · Pause icon
        Toggle · Play icon
    Slider · progress bar (JS)
    Slider · autoplay 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.

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 Slide · Intro ×4 (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 Slide · Button ×4 (FBK Button) › Properties: Text, Link, Tone, Shadow on hover · Icon group: Icon, Icon position · Style group: Style, Size, Width, Hover effect.
  4. Select Slider › Content › Options (loop or fade, autoplay, items per page, gap), Arrows and Pagination; one slide = one child, duplicate it to add more.
  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.

/* «Slider + progress» · class .fbk-bigslide */
.fbk-bigslide {
  /* Height of every slide */
  --fbk-t-height: clamp(32em, 46vw, 42em);
  /* Accent: the line by the title, the progress bar and the active dash */
  --fbk-t-accent: var(--fbk-accent);
  /* Dark layer over the photo, so the white text stays readable */
  --fbk-t-shade: color-mix(in srgb, var(--base-ultra-dark) 55%, transparent);
  /* The photo opens from a centered strip this size (width, height) */
  --fbk-t-strip-x: 15%;
  --fbk-t-strip-y: 35%;
  /* Progress bar between the arrows */
  --fbk-t-bar: 12em;
  /* the arrows' size (style family M, 2.5em) for the progress bar, which sits
     outside the slider */
  --fbk-slider-size: 2.5em;
  /* The text comes in once the photo has opened, with the same accent */
  --fbk-reveal-wait: calc(var(--fbk-slider-duration) * 1.6);
  --fbk-reveal-accent: var(--fbk-t-accent);
  /* distance of the text and the controls from the screen edges */
  --fbk-t-edge: var(--space-xl);
  --fbk-t-controls-y: var(--space-l);
  --fbk-t-progress: 0;
  /* the dashes: centered on the end side; at the top on phones (the title
     takes the bottom half) */
  --fbk-t-dots-y: 50%;
  --fbk-t-dots-shift: -50%;
}

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 slide, so alt stays empty). Slide height: --fbk-t-height on the slider wrapper; the opening strip: --fbk-t-strip-x / --fbk-t-strip-y.
  • Add or remove slides by duplicating one; the progress bar counts them on its own.
  • The progress bar needs "Execute code" enabled for the role; without it, the slider still works.
  • Each piece has its own class (slide, photo, content, progress bar, fill): edit its styles in the panel. The opening of the active slide is in the Custom CSS of each class (Style > CSS): the photo opening from the strip in .fbk-bigslide__photo (.splide__slide.is-active %root%) and the dark layer in .fbk-bigslide__content (%root%::before, and .splide__slide.is-active %root%::before once open). The arrows and dashes are placed in the wrapper class .fbk-bigslide.

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-bigslide, .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​

  • 06 -Slider from Fancy Bricks 1.0
  • 06 - Slider (Class-based) from Fancy Bricks 1.0
  • 06 - Slider 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.