Skip to main content

Text media · Split

A photo beside an intro with a button. Photo on the right, wider or narrower: FBK Media text properties.

Text media · Split

Full-page views: desktop, phone and dark mode

Text media · Split, desktop at 1440px wide

At 1440px wide.

Text media · Split, on a phone at 390px wide

At 390px wide.

Text media · Split, with the site in dark mode

With your site in dark mode.

See it live: Text media · Split 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.

Text media · Split
Container
Media text (FBK Media text)
Image (FBK Image)
Intro (FBK Intro)
Button (FBK Button)

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 Media text (FBK Media text) › Properties: Layout group: Media side, Columns, Vertical alignment, Order when stacked · Style group: Look, Tone, Shape, Overlap.
  3. Select Image (FBK Image) › Properties: Image, Alt text · Shape group: Proportion, Shape, Decoration, Border · Size and loading group: Loading, Width, Max width, Alignment · Caption group: Caption, Hide caption.
  4. 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.
  5. Select Button (FBK Button) › Properties: Text, Link, Tone, Shadow on hover · Icon group: Icon, Icon position · Style group: Style, Size, Width, Hover effect.

Finish by hand​

  • Replace the photo in the FBK Image properties (proportion and decoration are there too).
  • Media side, column widths, vertical alignment and the order on phones are FBK Media text properties.
  • The button's hover is its Hover effect property: Sweep (the same on every Fancy Bricks demo).

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

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​

  • 19 - Content from Fancy Bricks 1.0

What happened to the old libraries, and what to do with pages already built with them: Migrating from 1.0/2.0.