mirror of
https://github.com/supabase/supabase.git
synced 2026-10-05 17:35:10 +03:00
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 -->
35 lines
2.4 KiB
Plaintext
35 lines
2.4 KiB
Plaintext
---
|
|
title: Introduction
|
|
description: A flexible, open-source collection of Supabase components, blocks, and developer tools built on shadcn/ui and other portable foundations.
|
|
---
|
|
|
|
Supabase Library is a collection of UI components, full-featured blocks, and headless developer tools for Supabase projects. Many items build on the shadcn/ui registry system, while others—such as MCP blocks—ship portable integrations without a front end. It is designed to make new and existing Supabase-powered projects faster to build with ready-to-use solutions for authentication, file uploads, real-time updates, and more.
|
|
|
|
Supabase Library aims to solve these issues with:
|
|
|
|
- **Extensible components**: Modify and extend simple primitives as needed.
|
|
|
|
- **Composable Components**: Modular structure that makes components easy to integrate and combine.
|
|
|
|
- **Supabase Clients**: Interact with Supabase however you choose.
|
|
|
|
- **Scaffolding for Hard Problems**: Pre-built solutions for challenging features like sign-in/sign-up flows, file uploads, and real-time data sync.
|
|
|
|
- **New or existing projects**: Designed to work with brand new projects or to fit easily into existing ones.
|
|
|
|
### Extensible components
|
|
|
|
Our components are designed to be easily extensible. You can modify the code to fit your needs and use it as a starting point for your own components. You can change any of the code to fit your needs and use it as a starting point for your own components. The important part is that the code is designed to make the hard parts easy, and leave the easy parts for you.
|
|
|
|
### Composable components
|
|
|
|
Our components are designed to be easily composable. You can combine them to create new components that are tailored to your needs. If you want to change the design or behavior of a component, you can easily do so in your own codebase.
|
|
|
|
### Supabase clients
|
|
|
|
The Supabase clients are the backbone of your apps. They are designed to be easily integrated with your existing Supabase project. We provide both client-side and server-side clients for several major frameworks, and the code is designed to be easily integrated with your existing codebase.
|
|
|
|
### Scaffolding for hard problems
|
|
|
|
Setting up something like Auth should be easy, so we've done the hard work for you. Our components are designed to be easily integrated with your new or existing Supabase projects. Installing them drops the files into place so you can get the hard parts out of the way quickly.
|