Back to Supabase

Introduction

apps/design-system/content/docs/index.mdx

1.26.041.5 KB
Original 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 UI Library </AccordionTrigger> <AccordionContent> If you are looking for the Supabase UI, you can find it [here](https://supabase.com/ui). </AccordionContent> </AccordionItem> </Accordion>