Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Benefits Accordion Login Block for React

A split sign-in page for a freelancer back office: the form with Remember me beside five benefits as an accordion, one open at a time and the first open to start, with ruled rows.

Framework
UI library

Preview

Preview width

Installation

Part of Pro
Pro unlocks the code and one-line install of every Pro button and text effect, plus the MCP for your AI editor.
Have Pro already? Sign in to open it.Opens here as soon as you're Pro.

Overview

Put the reasons to stay beside the sign-in with this benefits list login block for React with Base UI. It's the sign-in of Solobench, a back office for freelancers: the page's two side rails run its full height and one band crosses the screen between two rules. The form sits at the start of the band: a Field with the email Input, another with the Password Input and a "Forgot password?" link, a Checkbox for Remember me, and the Shine Button, the only colored control. At the end, behind a divider that meets both rules at a plus mark, five benefits sit in an Accordion: each row has a check mark and a title, opens one line of detail under it, and is ruled by a hairline that runs from the divider to the rail. Only one is open at a time and the first starts open. On a phone the accordion is gone and the form takes the screen. It's built from Accordion, Checkbox, Field, Input, Password Input, Shine Button and Guides, with a CSS entrance only. For a sign-in that gives reasons to come back.

FAQ

What happens when I sign in, and what stays in the page?

Nothing leaves the page. Sign in waits under a spinner for less than a second, then shows "You're signed in" with the address you typed and, if you ticked Remember me, "Stays signed in on this device"; a polite status message says nothing was sent. Sign out brings the form back with your email still filled in. To wire it for real, post the email, the password and the Remember me choice to your auth endpoint where the code says so, keep the busy state until it answers, then redirect, or show its error under the field it concerns. The benefits are typed copy about a made-up product: write your own, and keep each one true.

How does the accordion behave?

It's a single accordion: opening a row closes the other, the first starts open, and the open row can be closed again. Each trigger is a button inside an h3 with the check mark and the title, and pressing it or Enter or Space toggles it. In this version the arrow keys don't move between triggers: Tab goes from one to the next. A closed row's detail stays in the page, hidden.

Does Remember me do anything?

It sets one choice and shows its effect in the result, as a real form would send it: ticked, the sign-in lasts on this device; unticked, only until the tab closes. Nothing is stored. When you wire it up, pass the value to your auth call so the session cookie gets the longer or the shorter lifetime. The checkbox is a real labelled control in the foreground tones, so the Shine Button stays the only primary-colored element.

Why is the Sign in button never disabled?

A disabled button can't explain itself, and keyboard users can't reach it. Here it stays enabled: pressing it with an empty or malformed email, or no password, marks those fields invalid, writes one sentence under each and moves focus to the first, which reads its problem out. Typing clears that field's problem. The browser's own validation bubbles are turned off with noValidate, so the messages look the same in every browser, and each field keeps a line for its problem even when there is none, so a problem never pushes the page.

Can I put real claims in the benefits?

Yes, and only true ones: the rows are the typed BENEFITS list, with a title and a line of detail each. A trial length, a price or a security claim is a promise a visitor will hold you to, so keep it in step with your pricing page, and add or remove rows freely; the heading names the count in words, so change "Five reasons" if you do.

What do phone visitors see?

The accordion is hidden below 1024 px (max-lg:hidden), so a phone shows the product's mark, the heading, the form and the Sign in button, which ends on the first screen.

  • Pro

    Feature Tour Login

    Split with a panel

    A split sign-in page for a spreadsheet that works like a database: the form beside a wide three-tab tour (Boards, Timeline, Reports), each tab a drawn greyscale view of one table and a sentence.

  • Pro

    A split sign-in page for a product analytics tool: the form beside a What's new list of three releases with a slanted edge, each release a disclosure that opens its detail, and one GitHub row.

  • Pro

    Split Product Sketch Login

    Split with a panel

    A split sign-in page for a grocery delivery service: the form at the end beside a drawn sketch of the product (a basket, a delivery slot and a total in an inset frame), with Remember me and a simulated sign-in.

  • Pro

    Principles Rail About

    Principles and process

    A split about section for a release-management tool: a sticky title at the start, and six principles as stations on a hairline rail, each opening to what it means and how it shows up.

  • Pro

    A split sign-in page for uptime monitoring: the form at the start and four figures on hairline cells at the end, with a 30 days and 12 months switch that rolls the digits to the other period's numbers.

  • Pro

    App Download Login

    Split with a panel

    A reverse split sign-in page for a running tracker: a real QR code of a download link with an iOS and Android switch that re-encodes it, a copyable link, and the sign-in form beside it. On a phone the code gives way to a Get the app link.