PHPackages                             friends-of-wp/wp-dev-cli-ext-boilerplate - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility &amp; Helpers](/categories/utility)
4. /
5. friends-of-wp/wp-dev-cli-ext-boilerplate

ActiveLibrary[Utility &amp; Helpers](/categories/utility)

friends-of-wp/wp-dev-cli-ext-boilerplate
========================================

WP DevCli Extension that takes care of plugin boilerplate creation.

047PHP

Since Apr 27Pushed 3y ago2 watchersCompare

[ Source](https://github.com/friends-of-wp/wp-dev-cli-ext-boilerplate)[ Packagist](https://packagist.org/packages/friends-of-wp/wp-dev-cli-ext-boilerplate)[ RSS](/packages/friends-of-wp-wp-dev-cli-ext-boilerplate/feed)WikiDiscussions develop Synced 1mo ago

READMEChangelogDependenciesVersions (1)Used By (0)

`plugin:boilerplate:create`
===========================

[](#pluginboilerplatecreate)

This a an extension to the [Friends of WP Command Line Tool for Developers](https://github.com/friends-of-wp/wp-dev-cli). This command is included in the default tool.

Usage
-----

[](#usage)

The usage of the boilerplate creation command is very easy. As the only parameter the plugin output directory is needed. All other configuration is done via the creation process starting afterwards.

```
./wp-dev.phar plugin:boilerplate:create /path/to/plugin/plugin-name
```

How to create individual steps
------------------------------

[](#how-to-create-individual-steps)

It is possible to add individual steps to the boilerplate creation process. This is done via the config yaml file that can be handed over via the CLI parameter `-c`.

```
./wp-dev.phar plugin:boilerplate:create /path/to/plugin/plugin-name -c my-default-config.yml
```

[![CLI Output](docs/images/boilerplate.png)](docs/images/boilerplate.png)

The config file should have all the steps in there. All those steps will be processes in the order in that list.

```
steps:
  - \FriendsOfWp\BoilerplateDevCliExtension\Boilerplate\Step\InitializeStep
  - \FriendsOfWp\BoilerplateDevCliExtension\Boilerplate\Step\CopyTemplatesStep
  - \FriendsOfWp\BoilerplateDevCliExtension\Boilerplate\Step\ReplacingPlaceholdersStep
  - \FriendsOfWp\BoilerplateDevCliExtension\Boilerplate\Step\RenameMasterFileStep
  - \FriendsOfWp\BoilerplateDevCliExtension\Boilerplate\Step\RenamePluginDirStep
```

How to pre-define parameters
----------------------------

[](#how-to-pre-define-parameters)

When a custom config file is used it is possible to predefine the answers of some questions in the creation workflow. This helps for example if some answers are "always" the same like author or license.

```
parameters:
  core_plugin_name: "Acme Security"
  core_plugin_description: "This is the description for the Acme Studios Security plugin."
  core_plugin_version: "1.0.0"

  core_plugin_author_name: Nils langner
  core_plugin_author_email: nils.langner@startwind.io
```

Todos
-----

[](#todos)

- Create settings configuration ([RFC-FWP-01](https://github.com/friends-of-wp/rfc-fwp-01-settings))
- Create empty plugin admin pages
- Add author to plugin questions
- Select license
- Select menu images
- Extend config file to prefill as default "questions" (like license).
- Create config file from actual question answers (to reuse in the next run)
- Ask for license

###  Health Score

15

—

LowBetter than 3% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity8

Limited adoption so far

Community8

Small or concentrated contributor base

Maturity22

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

### Community

Maintainers

![](https://www.gravatar.com/avatar/f249250f50f750633718a189b04c381f79decacce4a73a47b180f5398bd69d5d?d=identicon)[friends-of-wp](/maintainers/friends-of-wp)

---

Top Contributors

[![phmLabs](https://avatars.githubusercontent.com/u/650537?v=4)](https://github.com/phmLabs "phmLabs (1 commits)")

### Embed Badge

![Health badge](/badges/friends-of-wp-wp-dev-cli-ext-boilerplate/health.svg)

```
[![Health](https://phpackages.com/badges/friends-of-wp-wp-dev-cli-ext-boilerplate/health.svg)](https://phpackages.com/packages/friends-of-wp-wp-dev-cli-ext-boilerplate)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
