mirror of
https://github.com/supabase/supabase.git
synced 2026-10-05 09:25:06 +03:00
Saxon Fletcher
cb35e1f98e
Our UI Library registry is expanding to include blocks that go beyond UI and in some cases focus purely on back-end. This PR is a precursor to adding more back-end related blocks. This PR includes the `ui-library -> library` rename plus redirects and small UI copy updates. Since this is a rename we'll need to update Vercel configuration. ## Vercel rollout Keep the Library project Root Directory as `apps/ui-library` 1. In the **Library** Vercel project, set: `NEXT_PUBLIC_BASE_PATH=/library` Apply it to Preview and Production, then redeploy the Library project. 2. In the **www** Vercel project, add: `NEXT_PUBLIC_LIBRARY_URL=<current value of NEXT_PUBLIC_UI_LIBRARY_URL>` Apply it to Preview and Production. Keep `NEXT_PUBLIC_UI_LIBRARY_URL` during the migration, then redeploy the www project. 3. Deploy in this order: 1. Library project 2. www project 4. Validate: - `/library` - `/library/docs/nextjs/password-based-auth` - `/ui` redirects to `/library` - `/ui/docs/nextjs/password-based-auth` redirects to `/library/docs/nextjs/password-based-auth` - `/ui/docs/ai-editors-rules/*` still uses its existing Docs redirects No Vercel dashboard redirect rules are needed. Environment-variable changes require a new deployment. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Supabase UI Library has been renamed to **Supabase Library** across navigation, pages, documentation, and resource links. * The Library is now available at `/library`, with updated descriptions covering components, blocks, and developer tools. * **Bug Fixes** * Added permanent redirects from legacy `/ui` URLs to corresponding `/library` paths. * Updated links throughout the site and documentation to prevent broken navigation and references. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
49 lines
1.7 KiB
Plaintext
49 lines
1.7 KiB
Plaintext
---
|
|
title: Introduction
|
|
description: Components and patterns that you can copy and paste into Supabase apps. Accessible. Customizable. Open Source.
|
|
---
|
|
|
|
Welcome to the Supabase Design System!
|
|
|
|
## FAQ
|
|
|
|
<Accordion type="multiple">
|
|
<AccordionItem value="faq-1">
|
|
<AccordionTrigger>
|
|
Why copy/paste and not packaged as a dependency?
|
|
</AccordionTrigger>
|
|
<AccordionContent>
|
|
The idea behind this is to give you ownership and control over the code, allowing you to decide how the components are built and styled.
|
|
|
|
Start with some sensible defaults, then customize the components to your needs.
|
|
|
|
One of the drawback of packaging the components in an npm package is that the style is coupled with the implementation. _The design of your components should be separate from their implementation._
|
|
|
|
</AccordionContent>
|
|
</AccordionItem>
|
|
<AccordionItem value="faq-2">
|
|
<AccordionTrigger>
|
|
Which libraries do you use?
|
|
</AccordionTrigger>
|
|
<AccordionContent>
|
|
We use the following libraries as a basis. Anywhere we use additional libraries, we document them in the individual component pages.
|
|
|
|
- [tailwindcss](https://tailwindcss.com)
|
|
- [shadcn/ui](https://ui.shadcn.com)
|
|
- [lucide-react](https://lucide.dev)
|
|
- [react-hook-form](https://react-hook-form.com)
|
|
|
|
You can find the full list of dependencies in the [package.json](https://github.com/supabase/design-system/blob/main/package.json) file.
|
|
</AccordionContent>
|
|
|
|
</AccordionItem>
|
|
<AccordionItem value="faq-3">
|
|
<AccordionTrigger>
|
|
I was looking for Supabase Library
|
|
</AccordionTrigger>
|
|
<AccordionContent>
|
|
You can find Supabase Library [here](https://supabase.com/library).
|
|
</AccordionContent>
|
|
</AccordionItem>
|
|
</Accordion>
|