Component catalog
The full catalog lives on the live demo site. Browse it at demo.auth.ryanweiss.net.
Every entry below links to its props-and-usage reference page in UI components.
What’s in the catalog
Atoms — @rw3iss/auth-client/preact/atoms
Headless / minimally-styled primitives — drop into any layout.
AuthStatusBadge— coloured pill showing the current session stateUserAvatar— initials + colour fromuser.emailUserMenu— dropdown with profile / settings / sign-outLogoutButton— single-action button that callsauth.logout()LogoutAllButton— sign out everywhere (revokes the refresh family)SsoButton·SsoButtonGroup— provider-specific (Google / Apple / GitHub / Microsoft)ProtectedRoute— gate that renders children only when authenticatedGuestOnly— opposite ofProtectedRouteRoleGate— gate by role code(s)PermissionGate— gate by permission code(s)TokenExpiryCountdown— live countdown to access-tokenexpAuthLoading— spinner aligned with the SDK’s bootstrap statePasswordStrengthMeter— inline strength indicator for password fields
Forms & views — @rw3iss/auth-client/preact/forms
Composed forms and admin views — assemble flows from these.
LoginForm·RegisterFormPasswordResetRequestForm·PasswordResetForm·ChangePasswordFormEmailVerificationNoticeTwoFactorEnrollment·TwoFactorDisableFormSessionsListMagicLinkRequestFormDeleteAccountFormAuditLogTableUsersTable·AdminUserEditPanelOrgCreateForm·OrgSettingsForm·OrgRoleEditor·OrgSwitcherMembersList·InviteMemberForm·InvitationsList·InvitationsAdminList·InvitationAcceptCardUserLookupTable·UserProfileCard
Flows — @rw3iss/auth-client/preact/flows
End-to-end multi-step flows. Drop one into a route and it handles the full UI.
CompleteLoginFlowCompleteSignupFlowCompletePasswordResetFlowCompleteSsoCallbackFlowCompleteAccountSecurityFlowCompleteImpersonationFlowCompleteOrgAdminFlow
Why a catalog?
Every component on the catalog page is rendered with realistic props + the source displayed inline. When adding auth to a new app, the shortest path is to find the equivalent demo page and copy the pattern — see How to use the playground for the recommended workflow.
The catalog also serves as a regression visual — any visual change to the SDK’s UI surface shows up on the catalog page first.