Skip to main content

Stats · Values ring

The section title in a circle, a large dashed ring turning slowly behind four values placed above, beside and below it, their titles in the brand color along the circle.

Stats · Values ring

Full-page views: desktop, phone and dark mode

Stats · Values ring, desktop at 1440px wide

At 1440px wide.

Stats · Values ring, on a phone at 390px wide

At 390px wide.

Stats · Values ring, with the site in dark mode

With your site in dark mode.

See it live: Stats · Values ring 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 pause button is hidden here (it needs the script); the ring still turns. 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.

Values ring
Container
Values
Values · Circle
Intro (FBK Intro)
Value · Trust
Value · Trust (FBK Icon item)
Value · Responsibility
Value · Responsibility (FBK Icon item)
Value · Commitment
Value · Commitment (FBK Icon item)
Value · Service
Value · Service (FBK Icon item)
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 Value · Trust, Value · Responsibility, Value · Commitment (+1 more) (FBK Icon item) › Properties: Icon, Title, Title tag, Text · Show or hide group: Hide icon, Hide text · Style group: Layout, Look, Tone, Shape, Size, Alignment, HTML tag, Background.
  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.

/* «Values» · class .fbk-values */
.fbk-values {
/* Circle size, ring color, ring size (times the circle) and the time of one
turn */
--fbk-t-circle: clamp(13em, 20vw, 16em);
--fbk-t-ring: var(--primary);
--fbk-t-ring-size: 1.8;
--fbk-t-turn: 150s;
}

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​

  • Edit each value (FBK Icon item): title and text. Keep four values: the grid places them top, start, end and bottom (.fbk-values__value, in order); the side titles run upright along the circle.
  • Circle size, ring color, ring size and the time of one turn: --fbk-t-circle, --fbk-t-ring, --fbk-t-ring-size and --fbk-t-turn on .fbk-values. The ring is .fbk-values__center::before; the texts carry the section background (--fbk-bg) so the ring passes behind them.
  • The endless turn is the class fbk-values--spin (remove it for a still ring), with the common pause button (it also stops off screen; nothing turns with reduced motion; needs "Execute code" for the button).

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-values, .fbk-values__center, .fbk-values__pause (+1 more), .fbk-intro.
  • 767px and below — .fbk-values, .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​

  • Infographics values 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.