4e:I[707087,["/_next/static/immutable/chunks/2985g-hklwiee.js","/_next/static/immutable/chunks/0qkc3dps_9x_i.js","/_next/static/immutable/chunks/2nvof3-29tvc3.js","/_next/static/immutable/chunks/3thksmxn95rly.js","/_next/static/immutable/chunks/15bpbjna9-vr3.js","/_next/static/immutable/chunks/3tjobt77z_9dj.js","/_next/static/immutable/chunks/0agonoz1szsjm.js","/_next/static/immutable/chunks/1ynd3dcge2kn1.js","/_next/static/immutable/chunks/0krdn-21gkgjt.js","/_next/static/immutable/chunks/0n9w9riw96l80.js","/_next/static/immutable/chunks/0w75qangey2ys.js","/_next/static/immutable/chunks/1tge7vcvsb70s.js","/_next/static/immutable/chunks/35ju_ac0ysz07.js"],"RegistryDependencies"] 4f:I[512940,["/_next/static/immutable/chunks/2985g-hklwiee.js","/_next/static/immutable/chunks/0qkc3dps_9x_i.js","/_next/static/immutable/chunks/2nvof3-29tvc3.js","/_next/static/immutable/chunks/3thksmxn95rly.js","/_next/static/immutable/chunks/15bpbjna9-vr3.js","/_next/static/immutable/chunks/3tjobt77z_9dj.js","/_next/static/immutable/chunks/0agonoz1szsjm.js","/_next/static/immutable/chunks/1ynd3dcge2kn1.js","/_next/static/immutable/chunks/0krdn-21gkgjt.js","/_next/static/immutable/chunks/0n9w9riw96l80.js","/_next/static/immutable/chunks/0w75qangey2ys.js","/_next/static/immutable/chunks/1tge7vcvsb70s.js","/_next/static/immutable/chunks/35ju_ac0ysz07.js"],"Installation"] 50:I[314491,["/_next/static/immutable/chunks/2985g-hklwiee.js","/_next/static/immutable/chunks/0qkc3dps_9x_i.js","/_next/static/immutable/chunks/2nvof3-29tvc3.js","/_next/static/immutable/chunks/3thksmxn95rly.js","/_next/static/immutable/chunks/15bpbjna9-vr3.js","/_next/static/immutable/chunks/3tjobt77z_9dj.js","/_next/static/immutable/chunks/0agonoz1szsjm.js","/_next/static/immutable/chunks/1ynd3dcge2kn1.js","/_next/static/immutable/chunks/0krdn-21gkgjt.js","/_next/static/immutable/chunks/0n9w9riw96l80.js","/_next/static/immutable/chunks/0w75qangey2ys.js","/_next/static/immutable/chunks/1tge7vcvsb70s.js","/_next/static/immutable/chunks/35ju_ac0ysz07.js"],"FilesView"] 51:T1ea6,--- title: Plate UI description: Install, customize, and sync copied Plate UI components. --- Plate UI is the copied component layer for Plate. Use the shadcn CLI for the fastest setup, or install components manually when you need more control. ## CLI Installation (Recommended) This is the fastest way to integrate Plate UI's core dependencies and base styles. ### Install Plate UI If you are not using Next.js, refer to the official [shadcn/ui installation guides](https://ui.shadcn.com/docs/installation) for your specific framework before proceeding. ```bash npx shadcn@latest add @plate/plate-ui ``` ### Basic Usage With Plate UI's core installed, proceed to the guide specific to your framework: * **[Next.js Guide](./next)** - For server-side rendered applications (Next, Remix, etc.) * **[React Guide](./react)** - For single-page applications (Vite, React Router, etc.) ## Manual Installation If you prefer a step-by-step approach or are not using the shadcn CLI, follow these steps: ### Install Plate ```bash npm install platejs ``` When manually installing Plate, you'll need to add the specific packages for each plugin you want to use. For example, if you want to use the `AIMenu` component, you would need `@platejs/ai` and its dependencies. Check each component's documentation for its required packages, or use the CLI to automatically install the required packages. ### Configure CSS Variables Add the following CSS variables to your global stylesheet: ```css title="app/globals.css" :root { /* Base brand color for Plate UI components */ --brand: oklch(0.623 0.214 259.815); } .dark { --brand: oklch(0.707 0.165 254.624); } ``` ### Add Components With Plate UI's core installed, you can now add individual Plate UI components to build your editor interface. For example, to add the `FixedToolbar` and a `MarkToolbarButton`: ```bash npx shadcn@latest add @plate/fixed-toolbar @plate/mark-toolbar-button ``` Import and use them in your editor: ```tsx showLineNumbers title="components/editor.tsx" import { Plate } from "platejs/react"; import { FixedToolbar } from "@/components/ui/fixed-toolbar"; import { MarkToolbarButton } from "@/components/ui/mark-toolbar-button"; // ... other imports export function MyEditor() { // ... editor setup return ( B {/* ... other toolbar buttons ... */} {/* ... Editor component ... */} ); } ``` Explore the available [UI Components](/docs/components) and [Plugin Components](/docs/plugin-components) to customize your editor nodes (like paragraphs, headings, etc.) and build a feature-rich editing experience. ### Basic Usage With Plate UI's core installed, proceed to the guide specific to your framework: * **[Next.js Guide](./next)** - For server-side rendered applications (Next, Remix, etc.) * **[React Guide](./react)** - For single-page applications (Vite, React Router, etc.) ## Sync copied files Plate UI components live in your app after installation. Use this workflow when an agent needs to merge upstream registry file changes into local copies while keeping app-specific edits. For release review, use [Releases](/docs/releases). For scoped sync data, use the raw registry JSON. ### Install the skill ```bash npx skills add sync-plate-ui ``` ### Pick the JSON source Use the index for ordered update events. Use the component map when you need the events for one copied registry item. - [Index JSON](/registry/changelog/index.json) - [Components JSON](/registry/changelog/components.json) ### Prompt your agent ```text Use sync-plate-ui to sync code-block-node from: https://platejs.org/registry/changelog/index.json ``` ### Agent contract - Use `/registry/changelog/index.json` for ordered Plate UI update events. - Use `/registry/changelog/components.json` to find events by registry item. - Open event JSON for the PR, release dependency, target files, and migration notes. - Merge upstream file changes into the app copy; keep intentional local changes. ## Component Types When installing Plate UI components, you'll encounter different types of components with consistent naming patterns. Here's what they mean: ### Feature Kits Feature kits are the easiest way to add complete functionality to your editor. They bundle all necessary plugin configurations, UI components (including node renderers and toolbar items), and their underlying npm dependencies for a specific feature. ```bash # Install the complete AI feature suite, including configuration and UI npx shadcn@latest add @plate/ai-kit # Install drag and drop functionality with all its parts npx shadcn@latest add @plate/dnd-kit ``` When in doubt about what individual components you need, start with a feature kit. It's designed to provide a working feature out-of-the-box. You can always customize or remove parts later. ### Components #### Node Components These components are responsible for rendering specific types of content (elements or leaves) in your editor. If you need to create your own or customize existing ones, see the [Plugin Components guide](/docs/plugin-components). ```bash # Install the component for rendering blockquotes npx shadcn@latest add @plate/blockquote-node # Install the component for rendering code text npx shadcn@latest add @plate/code-node ``` #### Toolbar Components Toolbar components add interactive controls like buttons and dropdowns to your editor's toolbar. ```bash # Add an alignment dropdown for your toolbar npx shadcn@latest add @plate/align-toolbar-button # Add a toolbar button for AI features npx shadcn@latest add @plate/ai-toolbar-button # Add a color picker dropdown for your toolbar npx shadcn@latest add @plate/font-color-toolbar-button ``` #### Other Components Finally, Plate UI includes more advanced editor components as overlays, menus, block wrappers, etc. ```bash # Install a menu for AI features npx shadcn@latest add @plate/ai-menu # Install a draggable component for reordering blocks npx shadcn@latest add @plate/block-draggable ``` These components are typically included as part of their respective Feature Kits but can be installed individually for custom setups. ### Editor Templates These are pre-configured editor setups, often tailored for specific use cases or as a comprehensive starting point. You can explore all available [Editor Templates](/editors). ```bash # Install an AI-enabled editor template npx shadcn@latest add @plate/editor-ai # Install a basic editor template npx shadcn@latest add @plate/editor-basic ``` ### API Routes These items provide server-side components or API route handlers necessary for certain features. ```bash # Install AI-related API routes npx shadcn@latest add @plate/ai-api # Install file upload API routes (e.g., for UploadThing) npx shadcn@latest add @plate/media-uploadthing-api ``` ### Documentation Documentation files for various Plate features, guides, and API references can also be added to your local project. This is especially useful for keeping version-specific documentation alongside your code and for providing context to AI tools through MCP. Learn more about [setting up local documentation](/docs/installation/docs). ```bash # Add AI documentation npx shadcn@latest add @plate/ai-docs # Add Plate Plugin documentation npx shadcn@latest add @plate/plugin-docs ``` These items consists of Markdown files, which can be integrated into your own documentation system or made available for local search and AI consumption. 4a:["$","div",null,{"className":"flex flex-col gap-12","children":[["$","div",null,{"className":"pt-10 flex flex-col gap-4","children":[["$","ul",null,{"className":"flex gap-2 flex-wrap","children":[]}],["$","$L4e",null,{"registryDependencies":[]}]]}],["$","$L4f",null,{"sourceUrl":"https://platejs.org/r/installation-plate-ui-docs.json","proxyUrl":"https://shadcnregistry.com/r/plate/installation-plate-ui-docs","itemId":"@plate/installation-plate-ui-docs"}],["$","section",null,{"className":"flex flex-col gap-4","id":"files","children":[["$","h2",null,{"className":"text-lg md:text-2xl font-bold font-mono","children":"Files"}],["$","$L50",null,{"files":[{"path":"../../content/docs/installation/plate-ui.mdx","content":"$51","type":"registry:file","target":"content/docs/plate/installation/plate-ui.mdx"}]}]]}],"$L52"]}]

Plate UI

Installation

Files

content

Styles