Modules¶

Feature modules are self-contained classes that use the Module trait for singleton lifecycle management. Each module calls init() once on first instantiation, where it registers WordPress hooks and boots sub-components.

Module pattern¶

use Barberklingen\BasePlugin\Traits\Module;

class MyFeature {
    use Module;

    public function init(): void {
        add_action('init', [$this, 'register_hooks']);
    }
}

// Boot it — safe to call multiple times, init() runs only once
MyFeature::get_instance();

The Module trait composes Singleton, so get_instance() always returns the same object.

Loader pattern¶

Larger features bundle sub-modules behind a Loader class. The loader's init() instantiates each sub-module:

class MyFeatureLoader {
    use Module;

    public function init(): void {
        SubModuleA::get_instance();
        SubModuleB::get_instance();
    }
}

Feature loaders are typically guarded by a feature flag before being booted:

if (get_option('my_feature_enabled')) {
    MyFeatureLoader::get_instance();
}

Available modules¶

Core modules (always active)¶

These are booted unconditionally by BasePluginSetup: