jfb-form-sidebar-panel

Bind JetFormBuilder form settings to REST-visible post meta in Gutenberg.

21|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/Lonsdale201/wp-agent-skills --skill jfb-form-sidebar-panel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jfb-form-sidebar-panel
Source: https://github.com/Lonsdale201/wp-agent-skills/tree/main/jetformbuilder/jfb-form-sidebar-panel
Command: npx skills add https://github.com/Lonsdale201/wp-agent-skills --skill jfb-form-sidebar-panel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

JetFormBuilder forms often require per-form configuration to apply settings that vary from site-wide defaults, such as file size limits or target upload directories.

Core Features & Use Cases

  • Inject a per-form panel in the Gutenberg editor sidebar to bind settings to the form's post meta.
  • Expose a REST-visible JSON blob stored on the form CPT for per-form configuration.
  • Trigger per-form overrides for use cases like different upload targets, separate validation rules, or integration targets.

Quick Start

Install the companion plugin and open a JetFormBuilder form in the Gutenberg editor to see the per-form panel in the sidebar.

Frequently Asked Questions about jfb-form-sidebar-panel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add per-form settings to JetFormBuilder in the Gutenberg editor?

Per-form settings are added by injecting a sidebar panel in the Gutenberg editor that binds form-level options to a REST-visible post meta key on the JetFormBuilder custom post type. This stores configurations as a single JSON blob.

Can I set different upload folders or file size limits for individual JetFormBuilder forms?

Yes, you can set different upload folders or file size limits by triggering per-form overrides through the custom Gutenberg sidebar panel, which saves these specific configurations to the form's post meta.

What do I need to configure JetFormBuilder per-form options in WordPress?

You need WordPress, the JetFormBuilder plugin, and Gutenberg editor assets. The implementation relies on an editor-assets/before hook to render the sidebar panel and REST-visible post meta to store the JSON blob.

How does JetFormBuilder per-form configuration integrate with the WordPress REST API?

JetFormBuilder per-form configuration integrates with the WordPress REST API by binding the form-level options from the Gutenberg sidebar panel to a REST-visible post meta key on the jet-form-builder CPT.

Are there limitations to storing JetFormBuilder per-form settings as a single JSON blob?

Storing per-form settings as a single JSON blob in post meta means all form-level overrides are contained in one field, which simplifies REST exposure but limits granular meta querying for individual configuration keys.