Elements · Section menu
A menu of icon-and-label links in a bar above four stacked blocks; it stays fixed on screen while the blocks scroll past, each link jumps to its block and the block in view marks its link. The blocks alternate photo and text with a centered title over a wide photo. On phones the menu is one row that scrolls sideways.
![]()
Full-page views: desktop, phone and dark mode

At 1440px wide.

At 390px wide.

With your site in dark mode.
See it live: Elements · Section menu on fancybricks.co — the live preview, and the button that copies it.
Preview on the front end. Scripts don't run inside the builder, so here you only see the layout: the link of the block in view isn't marked here (that needs the script). 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.
Section menu
Container
Intro (FBK Intro)
Section menu
Menu
Link · Islands
Link · Icon
Link · Text
Link · Valleys
Link · Icon
Link · Text
Link · Waterfalls
Link · Icon
Link · Text
Link · Coast
Link · Icon
Link · Text
Blocks
Block · Islands (id route-islands)
Block · Photo (FBK Image)
Block · Content
Block · Intro (FBK Intro)
Block · Button (FBK Button)
Block · Valleys (id route-valleys)
Block · Intro (FBK Intro)
Block · Photo (FBK Image)
Block · Waterfalls (id route-waterfalls)
Block · Content
Block · Intro (FBK Intro)
Block · Button (FBK Button)
Block · Photo (FBK Image)
Block · Coast (id route-coast)
Block · Intro (FBK Intro)
Block · Photo (FBK Image)
Section menu · Marks the block in view (optional, deletable)
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.
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.
- Paste the template in Bricks first — see Copy and paste.
- Select Intro, Block · 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.
- Select Block · Photo ×4 (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.
- Select Block · Button ×2 (FBK Button) › Properties: Text, Link, Tone, Shadow on hover · Icon group: Icon, Icon position · Style group: Style, Size, Width, Hover effect.
- 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.
/* «Section menu» · class .fbk-secnav */
.fbk-secnav {
--fbk-t-sticky-top: var(--wp-admin--admin-bar--height, 0px);
/* height of the bar above the blocks (the script measures it; this is the
value without the script) */
--fbk-secnav-bar: 6em;
/* space between the bar and a block you jump to (a little air) */
--fbk-secnav-gap: var(--space-s);
}
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
- Each link points to the id of its block (an "id" attribute in Style > Attributes, also shown in the block label): #route-islands goes to the block with the id route-islands. If you rename one, change both. IDs must be unique on the page: if you paste this template twice, give the second copy new IDs and update its links.
- Change the link icons and labels, and the photo (with its alt text), eyebrow, title, texts and button of each block. Add a block by duplicating one, giving it a new ID and adding a link to it.
- Each piece has its own class (menu, link, icon, label, blocks, block, eyebrow, title):
edit its styles in the panel. The menu's distance from the top of the screen is
--fbk-t-sticky-topon the main class (below the WordPress admin bar by default; add your sticky header's height). - Active and hover styles are in the Custom CSS of the class
.fbk-secnav__link(Style > CSS): %root%[aria-current] is the link of the block in view (brand frame) and %root%:hover the link under the mouse. The space left above a block when you jump to it is scroll-margin-block-start in.fbk-secnav__block; the smooth scroll is in.fbk-secnav. The eyebrow's accent line is %root%::before in.fbk-secnav__eyebrow. - The code block only marks the link of the block in view (it needs "Execute code" enabled for the role); without it, or if you delete it, the menu still works as plain links.
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-secnav__link,.fbk-secnav__menu,.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
- 02 - Fancy Tabs - Floating 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.