Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Trusted Brands Login Block for React

A sign-in page for accounting software with a still strip of eight customer wordmarks under the form and a sector filter that dims the wordmarks outside the chosen sector instead of hiding or moving them.

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

Show who already signs in, without a marquee, with this trusted brands login block for React with Base UI. It's the sign-in of Sumwick, accounting software for small firms: the page's side rails run its full height, and one band crosses the screen between two rules with a plus mark where each meets a rail. The form is centred in the band, the product's mark over the heading, a Field for the email, a Password Input with its show and hide toggle and a "Forgot password?" link, and the Shine Button. Under it, still inside the rails, "Used by teams at" opens a strip of eight customer wordmarks, each a small drawn shape over a name in its own lettering. A Toggle Group of All, Retail, Finance and Health dims the wordmarks outside the chosen sector to a solid tint and softer text, with a line saying how many are left lit; nothing is hidden, nothing moves and nothing loops. It's built from Field, Input, Password Input, Toggle Group, Button, Shine Button and Guides, with CSS entrances only. For any sign-in page that wants proof of use without a testimonial.

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 a polite status message says nothing was sent; Sign out brings the form back. For real, post the email and password to your auth endpoint where the code says so, keep the busy state until it answers and show its error under the field it concerns. The eight customers are typed in WORDMARKS as fictional names with a shape each: replace them with customers who have agreed to be shown, and with their own marks if their brand rules allow it.

How does the sector filter work, and why does it dim instead of hide?

Each wordmark carries a sector, and the filter lights the ones that match and dims the rest to a solid 5% tint with softer text that still passes contrast. Nothing is removed or reordered, so the strip never changes height or width and nothing jumps under the pointer. A polite status message says how many are lit ("Retail: 3 of 8 shown, the rest dimmed."). The filter is a single-choice group: arrow keys move between the chips and one is always on.

Why isn't it a scrolling marquee?

A loop that never stops is hard to read, hard to click and a problem for people who are sensitive to motion, and a customer strip is not worth that. This one is a still row that wraps to two rows of four on a phone. If you have many customers, filter by sector, link to a customers page, or show the few that matter most to the person signing in.

Are the wordmarks pictures?

No. Each is a 24 by 24 path filled with the text colour and a name set in a typeface, a weight and a case of its own, so they follow your theme in light and dark and cost no image requests. The shapes are aria-hidden and the names are the text a screen reader reads, in a labelled list. To use real logos, swap the path and the name for an image with an empty alt and keep the name in text.

Is it usable with a keyboard and a screen reader?

Yes. Tab runs through the email, the password, its show and hide toggle, Forgot password, Sign in, the quiet link and the sector filter, where the arrow keys move between chips. Each problem is tied to its field, focus goes to the first, and after signing in it moves to the result's heading while a polite status message says what happened.

How does it look on a phone?

The form comes first and Sign in ends on the first screen. The strip sits under it as two rows of four wordmarks, with the filter chips above it, and the page keeps its height as the filter changes.

  • Pro

    A strip of eight customer names of a design-handoff product set as type alone, each in its own typeface treatment, with no icons, cells or lines but the page's top rule.

  • Pro

    A full-height sign-in page for a password manager with four hairline cells under the form, each a button whose hover card says what the safeguard is and where it stops.

  • Pro

    A split sign-in page for a project tool for makers: the form beside a narrow stepper of three customer quotes with Previous and Next buttons, a count and the arrow keys. It never turns by itself.

  • Pro

    A full-height sign-in page for a team chat app: the product's mark, Google and GitHub rows with lettermark tiles, an or rule, email and password checked on submit, and one Sign in button with a simulated wait and its result.

  • 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

    Custom Branding Login

    Split with a panel

    One sign-in page for three white-label customers: a demo rail picks the tenant, and the page re-skins from typed fields, with its own mark shape, name, welcome line, background pattern and sign-in methods, and no brand colour.