Overview
Breakdance exposes WordPress actions and filters for extending its behavior. Actions run your callback at a particular point; filters pass a value to your callback and use the value it returns. Register them in your custom plugin with add_action() or add_filter().
The canonical Actions API points to the public hooks documentation on GitHub. This reference groups those hooks and shared-code hooks by purpose.
| Reference | What it covers |
|---|---|
| Lifecycle | Plugin loading, activation, and condition registration. |
| Saving | Document saves and filters controlling global data writes. |
| Rendering | Element and document markup, classes, attributes, and dependencies. |
| Loops | Post/Term Loop Builder and Posts List output. |
| Fonts | Font registration and Google Fonts URLs. |
| Queries | Query arguments produced by the query control. |
| Settings & Admin | Admin tabs, API-key fields, and visitor tracking. |
| Forms | Form markup, email, validation, and submissions. |
| Builder Vocabulary | Controls, shape dividers, variables, macros, and library providers. |
Callback argument counts matter. A filter documented with three arguments needs add_filter($hook, $callback, 10, 3) if the callback uses all three. Return the filtered value after making your changes so other extensions' values are preserved.
PHP namespaces remain Breakdance in both products. Hook aliases apply only to hooks dispatched through the shared compatibility helpers; see Breakdance & Oxygen Compatibility.