JPKCom DB
View on GitHub (opens in a new tab)

JPKCom Gutenberg Bootstrap Optimizer — Guide & Tips

Automatically fix and optimize Gutenberg and Bootstrap settings in WordPress — installation and practical notes for the JPKCom Gutenberg Bootstrap Optimizer.

JPKCom Gutenberg Bootstrap Optimizer fixes and optimizes settings for the interplay of Gutenberg and Bootstrap. The plugin works without a settings page — once activated, its adjustments take effect automatically.

Guide

Requirements

  • WordPress 6.9 or newer (tested up to WordPress 7.1)
  • PHP 8.3 or newer

Installation

  1. In your admin panel, go to Plugins → Add New and click Upload Plugin.
  2. Choose the plugin's ZIP file and click Install Now.
  3. Click Activate — the plugin is ready to use right away.

There is no settings page. Once the plugin is active, the optimizations apply automatically.

Tips & Tricks

  • Best in Bootstrap-based setups: The plugin targets projects where Gutenberg is used together with Bootstrap — for example themes or page builders built on Bootstrap.
  • Activate and forget: As there is no configuration, nothing needs to be set up after activation.
  • Reproducible updates: Since version 2.0.3 the plugin uses secure self-hosted updates via GitHub with SHA256 checksums and runs with declare(strict_types=1). Since 2.0.9 it also carries the Update URI header: the wordpress.org update API then no longer returns updates for this plugin, so a plugin published there under the same slug cannot pose as an update. Since 2.0.10 Dashboard → Updates shows the JPKCom logo as the plugin icon. Since 2.0.11 (updater 1.5.0) the plugin is offered updates even while deactivated — provided another JPKCom plugin with updater 1.5.0 or later is active, on multisite network-wide or on the main site: one loaded updater serves every installed JPKCom plugin with the update row, icon and "View details", and the SHA256 check applies just the same. The stored update list no longer contains JPKCom download URLs; they come back only while a JPKCom updater is loaded, so no unverified package can be installed without one. The check also verifies packages another plugin supplies and recognises every GitHub address of a release file. A Git or other version-control checkout and a renamed folder (such as jpkcom-gutenberg-bs-optimize-main, while the plugin is active there) learn about new releases but are never updated through WordPress — the update would delete the checkout or the folder. The updater fetches update information only for accounts that can update plugins, in the update cron and in WP-CLI, never for anonymous visitors.

Further reading