wordplate.github.io

Plugins

WordPress Packagist comes straight out of the box with WordPlate. It mirrors the WordPress plugin and theme directories as a Composer repository.

Require the desired plugin or theme using wpackagist-plugin or wpackagist-theme as the vendor name. Packages are installed to public/plugins, public/mu-plugins or public/themes.

$ composer require wpackagist-plugin/hide-updates

This is an example of how your composer.json file might look like:

"require": {
    "wordplate/framework": "^7.1",
    "wpackagist-plugin/hide-updates": "^1.0"
},

Please visit WordPress Packagist website for more information and examples.

Must-use Plugins

With WordPlate you can enable standard plugins to be required just like must-use plugins.

_[Must-use plugins](https://wordpress.org/support/article/must-use-plugins/) (a.k.a. mu-plugins) are plugins installed in a special directory inside the content folder and which are automatically enabled on all sites in the installation._

Add the desired mu-plugins using wpackagist-plugin as the vendor name to installer-paths in your composer.json file.

"extra": {
    "installer-paths": {
        "public/mu-plugins/{$name}": [
            "type:wordpress-muplugin",
            "wpackagist-plugin/hide-updates",
        ]
    }
}

Require the desired plugin using wpackagist-plugin as the vendor name.

$ composer require wpackagist-plugin/hide-updates

The plugin is installed to the public/mu-plugins directory.

Third-party Plugins

Below we’ve put together a list of plugins we recommend using in your WordPlate project:

If you know of a plugin which would fit on this list, please open an issue on GitHub!