Skip to main content

Pricing · Plan and add-ons

One plan card and a form of optional extras: tick the add-ons you need, the monthly total adds them up and the form sends the request.

Pricing · Plan and add-ons

Full-page views: desktop, phone and dark mode

Pricing · Plan and add-ons, desktop at 1440px wide

At 1440px wide.

Pricing · Plan and add-ons, on a phone at 390px wide

At 390px wide.

Pricing · Plan and add-ons, with the site in dark mode

With your site in dark mode.

See it live: Pricing · Plan and add-ons 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 total stays at the base price here: on the front end it adds up the ticked add-ons. 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.

Pricing · Plan and add-ons
Container
Intro (FBK Intro)
Plan and add-ons
Form card
Form · Title
Form
Plan card (FBK Card)
Plan · Summary
Plan · Base
Plan · Base price (FBK Price)
Plan · Total label
Plan · Total
Plan · Total price (FBK Price)
Plan · Note
Add-ons total (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 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 Plan card (FBK Card) › Properties: Title, Title level, Text, Hide text · Style group: Highlight, Title size, Look, Tone, Shape, Photo overlay, Padding, Photo hover, Background · Layout group: HTML tag, Layout.
  4. Select Plan · Base price, Plan · Total price (FBK Price) › Properties: Currency, Amount, Period, Hide period, Old price, Hide old price, Note, Hide note · Style group: Size, Currency, Alignment.
  5. Select Form › Content › Fields (add, remove, required), Submit button and Actions (Email: recipient and subject; success message).
  6. 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.

/* «Plan and add-ons» · class .fbk-wf-addons */
.fbk-wf-addons {
/* Form card color: white like every Outline surface (dark or brand with the
section's scheme) */
--fbk-t-card-bg: var(--fbk-card-scheme-bg, var(--white));
/* An add-on row: its tint on hover and when ticked */
--fbk-t-row-hover: color-mix(in srgb, currentColor 4%, transparent);
--fbk-t-row-on: color-mix(in srgb, currentColor 7%, transparent);
}

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 add-ons are the options of a Checkbox field in the Bricks Form: write each one as Name · +$19 / month; the Add-ons total code block reads the number after the + of each ticked option, adds it to the plan's FBK Price (Plan · Base price) and writes the result in Plan · Total price (screen readers hear the new total). Change the base price in both prices.
  • The ticked add-ons go with the request (the Form's email action). The form is the Bricks Form element in the Fancy Bricks house style (class fbk-form: boxed fields with the label above, primary submit with the Sweep hover): set its fields, actions and messages in the Form element. While a field has focus the Form card card rises a little and casts a shadow (class fbk-focus-lift on it); remove the class for a still form. Other looks: add fbk-form--line (underline) or fbk-form--float (floating label).
  • Without JavaScript the form works the same and the total shows the base price.
  • Hover: each add-on row takes a light tint and, ticked, a tint and a stronger edge (CSS on .fbk-wf-addons, states li:hover and li:has(input:checked)); the submit button sweeps.

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-wf-addons, .fbk-intro.
  • 767px and below — .fbk-wf-addons__form, .fbk-price, .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-live).

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.