CTA · App download

An app download call to action: title, text, two store buttons and a star rating beside two phones made with CSS; on hover the front screen scrolls down.

Full-page views: desktop, phone and dark mode

At 1440px wide.

At 390px wide.

With your site in dark mode.

See it live: CTA · App download on fancybricks.co — the live preview, and the button that copies it.

Structure

This is what the Bricks Structure panel shows after you paste the template. Component instances say which component they are.

CTA app
  Brand slot (decorative, empty)
  Container
    CTA app
      Content
        Intro   (FBK Intro)
          Button · App Store   (FBK Button)
          Button · Google Play   (FBK Button)
        Rating
          Rating · Stars
          Rating · Score
      Phones
        Phone · Back
          Phone · Back · Screen
            Phone · Back · Screenshot
        Phone · Front
          Phone · Front · Screen
            Phone · Front · Screenshot

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 Button · App Store, Button · Google Play (FBK Button) › Properties: Text, Link, Tone, Shadow on hover · Icon group: Icon, Icon position · Style group: Style, Size, Width, Hover effect.
4. Select Rating · Stars › Content › Rating and Max rating.
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.

/* «CTA app» · class .fbk-ctaapp */
.fbk-ctaapp {
  /* Width of each phone */
  --fbk-t-phone-w: 15em;
  /* Dark frame around the screen */
  --fbk-t-bezel: 0.5em;
  /* Turn of the phone behind */
  --fbk-t-back-turn: 8deg;
  /* How long the screenshot takes to scroll down on hover */
  --fbk-t-scroll-time: calc(var(--fbk-hover) * 6);
}

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.

Finish by hand

• Replace the screenshots (long, phone-width captures; 600 × 2200 here) in Phone · Front and Phone · Back, and the front one's alt text. The phone behind is decoration (no alt text).
• The store buttons are two equal FBK Button (Primary, Sweep) with text: no store should look secondary. Link them to your App Store and Google Play pages, or swap them for the official badges as images.
• The stars are a Bricks Rating element with the house stars of FBK Quote (class fbk-quote__rating): change its Rating (4.8) and the text next to it to match.
• Phone width, bezel and the turn of the phone behind: --fbk-t-phone-w, --fbk-t-bezel and --fbk-t-back-turn on .fbk-ctaapp.
• Hover: the front screenshot scrolls to its end and the phone behind opens a little (class .fbk-ctaapp--scroll, Style > CSS: %root%:hover; its pace is --fbk-t-scroll-time). Remove the class for still phones.

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-ctaapp, .fbk-intro.
• 767px and below — .fbk-ctaapp, .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).

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.