Description
{eac}Doojigger is a WordPress plugin framework: a base plugin that ships with a working set of security, debugging, encryption, session, and administration features, plus an architecture for building your own plugins and extensions on top of it without rewriting WordPress boilerplate each time.
If you build or maintain multiple WordPress plugins — internal tools, client work, or products — {eac}Doojigger's abstract classes and traits handle the repetitive plumbing (activation/deactivation, multi-site awareness, options storage, updates, settings UI, logging) so your code only has to handle what's actually specific to your plugin.
Three ways to build with {eac}Doojigger
-
Derivative plugins ("Doojiggers") — build your own plugin by extending {eac}Doojigger's abstract classes (
abstract_context,abstract_frontend,abstract_backend). You write a small loader file plus a class file; the framework handles the rest. -
Extensions ("Doolollys") — a PHP class dropped into the
Extensionsfolder (of the plugin or a child theme) that adds functionality to an existing Doojigger. Lowest-effort option for small, task-specific additions. -
Extension plugins ("Doohickeys") — an extension packaged as its own plugin, so it isn't at risk of being overwritten on the parent plugin's next update or reinstall. Can ship its own automatic updates via the included
plugin_updatetrait.
If you're customizing a WordPress site, code that needs to survive a theme change belongs in a plugin, not a theme. Themes should hold presentation code only — anything functional should live in a plugin or plugin extension so it isn't lost the next time the theme is updated or swapped.
