How to build FeatherPanel addons. Raw .md files are the best source for indexing.
Primary contract for generating or modifying plugins. Follow every rule unless the user overrides it.
These are **real addons** that ship with / are developed against FeatherPanel. Use them as pattern references — copy structure and idioms, n
Replace `helloplugin` / `HelloPlugin` consistently. Prefer studying [examples.md](./examples.md) for production shapes.
Ship selectable colors (and optional CSS) under Preferences → Appearance → Theme packs. No panel rebuild when someone installs your pack.
UI packs can replace shell regions, hide slots, swap whole pages, and register toolbar actions. Create with Dev template **`ui-pack`** (`Plu
Runtime host API for plugins — events, cancellable actions, toasts, modals, search, shortcuts. Source: `frontendv2/src/lib/plugin-sdk/` (hos
Frontend integration is mostly **declarative JSON** under `Frontend/`, plus static HTML/JS/CSS published from `Frontend/Components/` (URL pr
During boot, each loaded plugin’s `processEvents(PluginEvents $event)` runs. Register listeners with `$event->on($eventId, $callback)`.
Mixins are reusable PHP capabilities that plugins can opt into. Core code lives under `backend/app/Plugins/Mixins/`.
Unauthenticated (or publicly reachable) plugin pages are declared in: