Perxel

WP Plugin Toolkit

An open-source foundation for building WordPress plugins: a template repo with autoloading, standards checks in CI and a release workflow, plus a shared admin UI kit. Perxel uses it for every plugin it builds.

Updated October 10, 2026 · Version 0.0.3

WP Plugin Toolkit is the open-source foundation Perxel uses to build WordPress plugins. It has two parts: a template repository for the backend and a shared admin UI kit for the frontend. It is the standard base for every plugin Perxel develops, including Perxel Image Optimizer, Perxel AI Translate and Perxel Accordion for TinyMCE, all approved for the WordPress.org plugin directory.

The problem

When you start a new plugin, most of the early time doesn't go to features but to rebuilding the scaffolding: folder structure, autoloading, activation and deactivation hooks, build setup and CI. Then comes rewriting the CSS and JS for the settings pages, and each plugin ends up a little different in layout and behaviour.

WP Plugin Toolkit puts both parts into one shared starting point, so the effort goes into the business logic.

The template repository: wp-plugin-starter

wp-plugin-starter is a GitHub template repository. Creating a new repo from it gives you a working plugin straight away: a codebase with a namespace and PSR-4 autoloading, a sample Settings screen rendered in the shared layout, PHPCS and WordPress Plugin Check running in CI, and a workflow that packages the install zip and releases it to WordPress.org.

Starting a new plugin from the toolkit

Every step is in the repo's README, with no extra tooling:

  1. Create a repo from the template. On GitHub, choose Use this template and clone it.
  2. Replace the six naming tokens (namespace, display name, slug, repo name, constant prefix and hook prefix) with one sed command, then rename the main file and the .pot file. There is no build step.
  3. Add the admin UI kit if the plugin has a settings screen. Run bin/update-ui.sh with the latest wp-plugin-ui version. A plugin that only runs in the editor or through a shortcode skips this.
  4. Check and package. composer run lint runs PHPCS, composer run build writes the install zip to dist/.
  5. Release. Once WordPress.org approves the first submission, every GitHub Release deploys to WordPress.org on its own.

The admin UI kit: wp-plugin-ui

wp-plugin-ui is a light admin UI layer rendered on the server with PHP and a little plain JS, with no framework and no build step. It provides a main layout with a feature sidebar and a content area, plus a few ready-made components that sit on top of wp-admin's own CSS instead of replacing it.

What it includes today:

  • The main layout. A feature sidebar, a sticky title bar with the Save button, and a footer with the version and support links.
  • Grouped settings lists. Each row has a label, a short description and its control on the right, with status dots and a separate zone for destructive actions.
  • Inputs. Toggles, multi-select pills, a colour picker and a Media Library picker.
  • Feedback. Notices, a progress bar, a compact inline meter and a spinner.
The Settings screens of Perxel Image Optimizer and Perxel AI Translate side by side, with the same sidebar, title bar and grouped settings list

One layout in two different plugins: Perxel Image Optimizer (left) and Perxel AI Translate (right).

The UI kit is vendored into each plugin at vendor/perxel-ui/, the same model as Action Scheduler: committed to the plugin repo, packaged in the zip and updated with a script. The runtime loader always picks the highest version among the active plugins, so an old copy in one plugin can't break or change the interface of another.

Within a major version the kit's API only grows, never shrinks. An old plugin running a newer kit, or a new plugin running an older one, never breaks; if a plugin needs a newer kit than the one running, it shows an admin notice.

Passed WordPress.org review

Every plugin submitted to WordPress.org has its code read by the Plugin Review team before approval, mostly for security and WordPress coding standards. Plugins built on this toolkit that have been approved:

The review team's feedback is fixed in the toolkit itself, so every plugin built later, including custom plugins for clients, starts from the same standard.

One base for every plugin

The toolkit shortens the time to start a new plugin and keeps Perxel's whole plugin catalogue consistent in both backend architecture and admin UI. An upgrade to a shared part reaches every plugin through a vendor update.

Both repos are public on GitHub so developers and agencies can read them or use them as a starter for their own projects. The toolkit is the base for Perxel's custom plugin development service.

Footnotes

Want a quote?
Get in touch with Perxel today.