Skip to main content

Contact · Log in and register

A card with two tabs, Log in and Create account, each with a Bricks form that really logs in or registers the user, beside a photo. When the visitor switches to Create account, the card and the photo change sides and the photo fades to another.

Contact · Log in and register

Full-page views: desktop, phone and dark mode

Contact · Log in and register, desktop at 1440px wide

At 1440px wide.

Contact · Log in and register, on a phone at 390px wide

At 390px wide.

Contact · Log in and register, with the site in dark mode

With your site in dark mode.

See it live: Contact · Log in and register 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. 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.

Contact · Log in and register
Container
Log in and register
Card
Tabs
Tab menu
Tab · Log in
Tab · Log in · Text
Tab · Create account
Tab · Create account · Text
Tab content
Pane · Log in
Log in · Intro (FBK Intro)
Log in · Form
Log in · Forgot password
Pane · Create account
Create account · Intro (FBK Intro)
Create account · Form
Photo
Photo · Log in (decorative)
Photo · Create account (decorative)
Tabs · sliding line (JS, optional)

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 Log in · Intro, Create account · 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 Tabs › one tab = a title and its pane, in the same order: duplicate both to add one.
  4. Select Log in · Form, Create account · Form › Content › Fields (add, remove, required), Submit button and Actions (Email: recipient and subject; success message).
  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.

The Custom CSS field of this template's own element, with one of its variables as a real example.

/* «Log in and register» · class .fbk-logreg */
.fbk-logreg {
/* Height of the panel: the longer form fits, so switching tabs never changes
it */
--fbk-t-height: 40em;
/* Length of the swap (card and photo change sides) */
--fbk-t-swap: 0.8s;
/* Card color: white like every Outline surface (dark with the section's
scheme) */
--fbk-t-card-bg: var(--fbk-card-scheme-bg, var(--white));
}

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 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 Tabs 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).
  • Messages: the class fbk-form--notice on both forms shows Bricks' success and error messages in a soft box with an icon that fades in, lined up with the fields; remove it for Bricks' own colors.
  • Log in form: Bricks action User login (fields: Email or username, Password, Remember me). Bricks shows the success message and keeps the visitor on the page; to send members somewhere (their account, the shop), add the action Redirect in the Form element and set its URL.
  • Create account form: Bricks action User registration (First name, Last name, Email, Password of 8 characters or more; WordPress sends its welcome email). Important: Bricks creates the account even when Settings > General > Anyone can register is off, with the New user default role of that screen (keep it at Subscriber). If your site should not take sign-ups, delete the Create account tab and its pane.
  • Make this your login page: put the template on a page, then in Bricks > Settings > General > Custom authentication pages choose it as Login page (and Registration page). Link Forgot your password? to the page with the Contact · Lost password template.
  • The tabs are the Bricks Tabs (Nestable) element with the fbk-tabs pattern (keyboard and roles from Bricks), the house tab row: the 2 px line under the open tab slides from one to the other (code block Tabs · sliding line; delete it and the open tab draws its own line); the panes fade with fbk-tabs--motion (remove it for an instant switch).
  • Swap (removable class fbk-logreg--swap on Log in and register): when Create account is open, the card and the photo change sides and the photo fades to the second one (.fbk-logreg__photo--reg). Remove the class for a still layout; the photo still changes. The panel height (--fbk-t-height) leaves room for the longer form so nothing jumps when switching tabs.
  • Photos: two Image elements in Photo (decorative, alt empty): replace them with yours.

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-logreg, .fbk-logreg__card, .fbk-logreg__media, .fbk-intro.
  • 767px and below — .fbk-logreg__card, .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​

  • 01 – Login / register from Fancy Bricks 1.0
  • Fancy Login/Register 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.