Kanvas Phoenix rebirth is a powerful library of pre-built components and features designed to simplify and expedite the development. Kanvas Phoenix rebirth streamlines the creation of attractive and functional user interfaces, allowing frontend developers to focus on business logic rather than reinventing the wheel in each project.
To start using Kanvas Phoenix rebirth in your project, follow these simple steps:
- Ensure you have installed Kanvas Core JS
- Install Kanvas Phoenix rebirth using npm or yarn:
npm install @kanvas/phoenix-rebirth
# or
pnpm add @kanvas/phoenix-rebirth
# or
yarn add @kanvas/phoenix-rebirth- Import the necessary components into your project and start using them.
import { Button } from "@kanvas/phoenix-rebirth/dist/components/base/button";Start building your dashboard!
Kanvas Phoenix rebirth integrates seamlessly into your project. Here's a quick example of how to use a button component:
import { PlusIcon } from "@kanvas/phoenix-rebirth/dist/components/base/icons";
import { Button } from "@kanvas/phoenix-rebirth/dist/components/base/button";
import { Input } from "@kanvas/phoenix-rebirth/dist/components/base/input";
function MyPage() {
return (
<div>
<Button onClick={doSomething}>
Do something <PlusIcon />
</Button>
<Input placeholder="Type..." value="some text" />
</div>
);
}Note: All components come from shadcn/ui you can check all of then.
import { createTailwindConfig } from "@kanvas/phoenix-rebirth/dist/config/tailwind";
module.exports = createTailwindConfig({
// ... your tailwind config
});in your main css file:
/* dont forget this ;) */
@tailwind base;
@tailwind components;
@tailwind utilities;
@layer base {
/* base ligth theme */
:root {
--background: 0 0% 100%;
--foreground: 240 10% 3.9%;
--card: 0 0% 100%;
--card-foreground: 240 10% 3.9%;
--popover: 0 0% 100%;
--popover-foreground: 240 10% 3.9%;
--primary: 240 5.9% 10%;
--primary-foreground: 0 0% 98%;
--secondary: 240 4.8% 95.9%;
--secondary-foreground: 240 5.9% 10%;
--muted: 240 4.8% 95.9%;
--muted-foreground: 240 3.8% 46.1%;
--accent: 240 4.8% 95.9%;
--accent-foreground: 240 5.9% 10%;
--destructive: 0 84.2% 60.2%;
--destructive-foreground: 0 0% 98%;
--border: 240 5.9% 90%;
--input: 240 5.9% 90%;
--ring: 240 10% 3.9%;
--radius: 0.5rem;
}
/* base dark theme */
.dark {
--background: 240 10% 3.9%;
--foreground: 0 0% 98%;
--card: 240 10% 3.9%;
--card-foreground: 0 0% 98%;
--popover: 240 10% 3.9%;
--popover-foreground: 0 0% 98%;
--primary: 0 0% 98%;
--primary-foreground: 240 5.9% 10%;
--secondary: 240 3.7% 15.9%;
--secondary-foreground: 0 0% 98%;
--muted: 240 3.7% 15.9%;
--muted-foreground: 240 5% 64.9%;
--accent: 240 3.7% 15.9%;
--accent-foreground: 0 0% 98%;
--destructive: 0 62.8% 30.6%;
--destructive-foreground: 0 0% 98%;
--border: 240 3.7% 15.9%;
--input: 240 3.7% 15.9%;
--ring: 240 4.9% 83.9%;
}
}
@layer base {
* {
@apply border-border;
}
body {
@apply bg-background text-foreground;
}
}Note: The variables within the global CSS file are those that control the behavior of the components such as their colors and border radius. To avoid conflicts between phoenix-rebirth and your tailwind configuration, it is recommended that you use other names to name your colors and other configurations.
theme: {
container: {
center: /* Reserved do not modify in tailwind */,
padding: /* Reserved do not modify in tailwind */,
screens: {
"2xl": /* Reserved do not modify in tailwind */,
},
},
extend: {
colors: {
border: "Reserved do not modify in tailwind",
input: "Reserved do not modify in tailwind",
ring: "Reserved do not modify in tailwind",
background: "Reserved do not modify in tailwind",
foreground: "Reserved do not modify in tailwind",
primary: {
DEFAULT: "Reserved do not modify in tailwind",
foreground: "Reserved do not modify in tailwind",
},
secondary: {
DEFAULT: "Reserved do not modify in tailwind",
foreground: "Reserved do not modify in tailwind",
},
destructive: {
DEFAULT: "Reserved do not modify in tailwind",
foreground: "Reserved do not modify in tailwind",
},
muted: {
DEFAULT: "Reserved do not modify in tailwind",
foreground: "Reserved do not modify in tailwind",
},
accent: {
DEFAULT: "Reserved do not modify in tailwind",
foreground: "Reserved do not modify in tailwind",
},
popover: {
DEFAULT: "Reserved do not modify in tailwind",
foreground: "Reserved do not modify in tailwind",
},
card: {
DEFAULT: "Reserved do not modify in tailwind",
foreground: "Reserved do not modify in tailwind",
},
},
borderRadius: {
lg: "Reserved do not modify in tailwind",
md: "Reserved do not modify in tailwind",
sm: "Reserved do not modify in tailwind",
},
keyframes: {
"accordion-down": {
// Reserved do not modify in tailwind
},
"accordion-up": {
// Reserved do not modify in tailwind
},
},
animation: {
"accordion-down": "Reserved do not modify in tailwind",
"accordion-up": "Reserved do not modify in tailwind",
},
},
},If you need to modify any of these parameters you must do so using CSS variables
To use the base components you just have to call the component or icon you want to use.
example:
import { PlusIcon } from "@kanvas/phoenix-rebirth/dist/components/base/icons";
import { Button } from "@kanvas/phoenix-rebirth/dist/components/base/button";
import { Input } from "@kanvas/phoenix-rebirth/dist/components/base/input";The components are designed to work on client side as server side, with nextjs 13^ app router, it is necessary to specify whether the client component, if nextjs throws you an error using a component for not specifying that it is client, you only have to change its import:
// with out "use client"
import { Select } from "@kanvas/phoenix-rebirth/dist/components/base/input";
// with "use client"
import { Select } from "@kanvas/phoenix-rebirth/dist/components/base/input.mjs";phoenix-rebirth includes utility components to improve the development experience, these components are:
- For
- Show
- Switch
- Match
Example How to use For Component:
// with out For
<ul>
[...].map((item, index) => (<li key="{index}">{item}</li>))
</ul>
// with For
<ul>
<For
each={[...]}
fallback={<> not elements </>}
error={<> some element throw an error </>}
>
{
(item, { key }) => (<li key={key}>{item}</li>)
}
</For>
</ul>With the For component, each element within it is rendered individually to the previous or next one, so if any element throws an error this does not break the application and an error message can be displayed.
Example How to use Show Component:
// with out Show
<ul>
{ (counter === 4) ? <li> true </li> : <li> false </li>}
</ul>
// with Show
<ul>
<Show
when={(counter === 4)}
deps={[counter]}
fallback={<li> false </li>}
>
<li> true </li>
</For>
</ul>The Show component improves the experience of using conditionals within jsx, making the code more readable and maintainable when you have nested conditions.
Example How to use Show Component:
// with out Switch/Match
<ul>
{(counter === 4) && <li> 4 </li>}
{(counter === 5) && <li> 5 </li>}
{(counter === 6) && <li> 6 </li>}
</ul>
// with Switch/Match
<ul>
<Switch
fallback={<li> no one </li>}
>
<Match when={counter === 4}>
<li> 4 </li>
</Match>
<Match when={counter === 5}>
<li> 5 </li>
</Match>
<Match when={counter === 6}>
<li> 6 </li>
</Match>
</Switch>
</ul>Switch and Match improve the experience when multiple cases must be evaluated for a single output, just like Switch in javascript.
We use a simple background and foreground convention for colors. The background variable is used for the background color of the component and the foreground variable is used for the text color.
The background suffix is omitted when the variable is used for the background color of the component.
Given the following CSS variables:
--primary: 222.2 47.4% 11.2%;
--primary-foreground: 210 40% 98%;The background color of the following component will be hsl(var(--primary)) and the foreground color will be hsl(var(--primary-foreground)).
<div className="bg-primary text-primary-foreground">Hello</div>Default background color of <body />...etc
--background: 0 0% 100%;
--foreground: 222.2 47.4% 11.2%;Muted backgrounds such as <TabsList />, <Skeleton /> and <Switch />
--muted: 210 40% 96.1%;
--muted-foreground: 215.4 16.3% 46.9%;Background color for <Card />
--card: 0 0% 100%;
--card-foreground: 222.2 47.4% 11.2%;Background color for popovers such as <DropdownMenu />, <HoverCard />, <Popover />
--popover: 0 0% 100%;
--popover-foreground: 222.2 47.4% 11.2%;Default border color
--border: 214.3 31.8% 91.4%;Border color for inputs such as <Input />, <Select />, <Textarea />
--input: 214.3 31.8% 91.4%;Primary colors for <Button />
--primary: 222.2 47.4% 11.2%;
--primary-foreground: 210 40% 98%;Secondary colors for <Button />
--secondary: 210 40% 96.1%;
--secondary-foreground: 222.2 47.4% 11.2%;Used for accents such as hover effects on <DropdownMenuItem>, <SelectItem>...etc
--accent: 210 40% 96.1%;
--accent-foreground: 222.2 47.4% 11.2%;Used for destructive actions such as <Button variant="destructive">
--destructive: 0 100% 50%;
--destructive-foreground: 210 40% 98%;Used for focus ring
--ring: 215 20.2% 65.1%;Border radius for card, input and buttons
--radius: 0.5rem;Note: for css use HSL color format
To add new colors, you need to add them to your CSS file and to your tailwind.config.js file.
app/globals.css
:root {
--warning: 38 92% 50%;
--warning-foreground: 48 96% 89%;
}
.dark {
--warning: 48 96% 89%;
--warning-foreground: 38 92% 50%;
}tailwind.config.js
module.exports = createTailwindConfig({
theme: {
extend: {
colors: {
warning: "hsl(var(--warning))",
"warning-foreground": "hsl(var(--warning-foreground))",
},
},
},
});You can now use the warning utility class in your components.
<div className="bg-warning text-warning-foreground" />