feat: replace existing plugin API with plugin overrides

Author: chrisvxd

apps/docs/pages/docs/api-reference/components/puck.mdx

@@ -35,7 +35,7 @@ export function Editor() {
 | [`onChange()`](#onchangedata)   | `onChange: (data) => {}`               | Function                                           | -        |
 | [`onPublish()`](#onpublishdata) | `onPublish: async (data) => {}`        | Function                                           | -        |
 | [`overrides`](#overrides)       | `overrides: { header: () => <div /> }` | [Overrides](/docs/api-reference/overrides)         | -        |
-| [`plugins`](#plugins)           | `plugins: [myPlugin]`                  | Plugin[]                                           | -        |
+| [`plugins`](#plugins)           | `plugins: [myPlugin]`                  | [Plugin\[\]](/docs/api-reference/plugin)           | -        |
 | [`ui`](#ui)                     | `ui: {leftSideBarVisible: false}`      | [AppState.ui](/docs/api-reference/app-state#ui)    | -        |
 
 ## Required props
@@ -197,7 +197,7 @@ export function Editor() {
 
 ### `plugins`
 
-An array of plugins to enhance Puck's behaviour. See the [Plugin API reference](/docs/api-reference/plugins).
+An array of plugins to enhance Puck's behaviour. See the [Plugin API reference](/docs/api-reference/plugin).
 
 ```tsx {6} copy
 import headingAnalyzer from "@measured/puck-plugin-heading-analyzer";

apps/docs/pages/docs/api-reference/plugin.mdx

@@ -0,0 +1,36 @@
+# Plugin
+
+> **⚠️ The plugin API is highly experimental and is likely to experience breaking changes.**
+
+A plugins is an extensions that enhances the capabilities of Puck.
+
+```tsx showLineNumbers copy {3-9, 15}
+import { Puck } from "@measured/puck";
+
+const MyPlugin = {
+  overrides: {
+    componentItem: ({ name }) => (
+      <div style={{ backgroundColor: "hotpink" }}>{name}</div>
+    ),
+  },
+};
+
+export function Editor() {
+  return (
+    <Puck
+      // ...
+      plugins={[MyPlugin]}
+    />
+  );
+}
+```
+
+## Params
+
+| Prop                      | Example                                | Type                                       | Status |
+| ------------------------- | -------------------------------------- | ------------------------------------------ | ------ |
+| [`overrides`](#overrides) | `overrides: { fields: () => <div /> }` | [Overrides](/docs/api-reference/overrides) | -      |
+
+### `overrides`
+
+Override the render functions for specific portions of the Puck UI. Implements the [`overrides` API](/docs/api-reference/overrides).

apps/docs/pages/docs/api-reference/plugins.mdx

@@ -1,11 +1,55 @@
 # Plugin API
 
-Puck provides an experimental plugin API to create sharable extensions to Puck.
+> **⚠️ The plugin API is highly experimental and is likely to experience breaking changes.**
+
+The plugin API enables developers to distribute plugins to customize the Puck interface.
 
 ## Official plugins
 
 - [`heading-analyzer`](https://github.com/measuredco/puck/tree/main/packages/plugin-heading-analyzer): Analyze the heading outline of your page and be warned when you're not respecting WCAG 2 accessibility standards.
 
+## Community plugins
+
+Please see the [awesome-puck repo](https://github.com/measuredco/awesome-puck) for a full list of community plugins.
+
 ## Developing a plugin
 
-Please see the [API reference](/docs/api-reference/plugins) for documentation.
+Plugins implement the same [`overrides`](/docs/api-reference/overrides) API used to build [custom interfaces](custom-interfaces#ui-overrides):
+
+```tsx showLineNumbers copy {3-9, 15}
+import { Puck } from "@measured/puck";
+
+const MyPlugin = {
+  overrides: {
+    componentItem: ({ name }) => (
+      <div style={{ backgroundColor: "hotpink" }}>{name}</div>
+    ),
+  },
+};
+
+export function Editor() {
+  return (
+    <Puck
+      // ...
+      plugins={[MyPlugin]}
+    />
+  );
+}
+```
+
+## Plugin currying
+
+Plugins are rendered in the order they are defined. All overrides are _curried_, meaning that the return node of one plugin will be passed as `children` to the next plugin.
+
+This may result in some incompatible plugin combinations. To improve your chance of building a widely compatible plugin, consider:
+
+1. Implementing as few override methods as you need
+2. Always rendering `children` if possible
+
+## Custom fields
+
+Plugins enable full UI overhauls. If you're creating a field for a specific use-case, you might be better off distributing a [custom field](custom-fields).
+
+## Further reading
+
+- [Plugin API reference](/docs/api-reference/plugin)