{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "signup-social",
"title": "Signup — social first",
"description": "Signup that leads with GitHub and Google provider buttons, falling back to an email/password form.",
"registryDependencies": [
"card",
"input",
"label",
"button",
"separator"
],
"files": [
{
"path": "registry/blocks/signup-social.tsx",
"content": "import {\n Card,\n CardHeader,\n CardTitle,\n CardDescription,\n CardContent,\n CardFooter,\n} from '@/components/ui/card'\nimport { Input } from '@/components/ui/input'\nimport { Label } from '@/components/ui/label'\nimport { Button } from '@/components/ui/button'\nimport { Separator } from '@/components/ui/separator'\n\n// Official brand marks — inlined because icon fonts (rightly) don't carry\n// third-party logos. GitHub's mark is monochrome and follows the text color;\n// Google's G keeps its brand colors per their sign-in guidelines.\nfunction GitHubMark({ size = 16 }: { size?: number }) {\n return (\n \n )\n}\n\nfunction GoogleG({ size = 16 }: { size?: number }) {\n return (\n \n )\n}\n\n/** Signup that leads with GitHub and Google provider buttons, falling back to an email/password form. */\nexport function SignupSocial() {\n return (\n \n \n Create your account\n Start with a provider, or use your email.\n \n \n
\n \n \n
\n
\n \n or with email\n \n
\n
\n \n \n
\n
\n \n \n
\n \n \n \n
\n By continuing you agree to the team terms and privacy note.\n
\n \n \n )\n}\n",
"type": "registry:component",
"target": "components/quill/signup-social.tsx"
}
],
"meta": {
"intent": [
"auth"
],
"use_when": "You need signup that leads with OAuth providers and falls back to email/password.",
"not_for": "you don't have OAuth providers configured, or want email/password as the primary path, not a fallback → signup; this is sign-in, not new-account creation — login-oauth is the matching pattern for returning users → login-oauth"
},
"docs": "Signup that leads with GitHub and Google provider buttons, falling back to an email/password form. Do: Put the provider buttons above the divider and the email/password fields below it, matching login-oauth's provider-first order. Don't: Bury the provider buttons below a full email/password form — that defeats the point of offering them. Use signup when you don't have OAuth providers configured, or want email/password as the primary path, not a fallback. Use login-oauth when this is sign-in, not new-account creation — login-oauth is the matching pattern for returning users.",
"categories": [
"auth"
],
"type": "registry:block"
}