JetFormBuilder: form-level settings panel in the Gutenberg sidebar

JetFormBuilder forms are stored as a custom post type (jet-form-builder) edited in the standard Gutenberg block editor. Companion plugins add per-form settings by injecting a panel into the editor's document sidebar — the panel reads and writes post meta on the form, so each form gets its own configuration independently of the plugin's global Settings page.

This skill covers that subsystem. It is distinct from the global plugin Settings page covered in the jfb-settings-tab skill — that one uses Vue + cx-vui components, this one uses WordPress packages (@wordpress/components, React under the hood) and standard post-meta REST exposure.

A typical JFB companion plugin (e.g. media-storage-for-jetformbuilder) ships both: a global tab for site-wide defaults, and a per-form sidebar panel for overrides. See the Dual-mode pattern section below.

API stability note

The register_post_meta + REST exposure pattern is standard WordPress and stable since WP 4.9. The JFB-specific pieces — the 'jet-form-builder/editor-assets/before' PHP action, the 'jet.fb.register.plugins' JS filter, and the useMetaState hook exposed on window.JetFBHooks — are stable across the JFB 3.x line in the source observed. The plugin-version-tested field records last end-to-end verification only.

When to use this skill

• A JFB companion plugin needs settings that differ between forms.
• The user asks how to add a sidebar panel to the JFB form editor.
• The diff/files contain register_post_meta for the jet-form-builder post type, jet.fb.register.plugins, jet-form-builder/editor-assets/before, or useMetaState.

Architecture in one paragraph