Plugin Builder

1. 

   The list of built plugins. You can open the plugin build settings form, make changes and rebuild, or you can build with a different slug (which makes a new plugin).

2. 

   The main settings form; the advanced section is hidden by default.

3. 

   The form to create Custom Post Types. You can add as many CPTs as you want.

4. 

   The form to create custom classes. You can add as many custom classes as you want.

5. 

   The form to add optional includes.

Why did you create Plugin Builder?

I’m a big fan of the WordPress Plugin Boilderplate, but the tedious manual work required to get a plugin started annoyed me. I wanted to develop plugins in a standard way more quickly.

Is Plugin Builder an official part of WordPress Plugin Boilerplate?

No. It’s built on top of the Boilerplate, but it’s not part of that project.

Why not just get the latest version of the Boilerplate from Github? Why have it in the Plugin Builder plugin itself?

Because loading executable code for inclusion in a WordPress installation goes against the WordPress Plugin Guidelines. Having the files for the Boilerplate in Plugin Builder means they are diff-able, and therefore can be checked by the WordPress team. The Plugin Repository is their place, after all, and needs to be kept secure (as do people’s WordPress sites who use this plugin).

Where’s the LEGO image from?

It’s from Flickr. The photo was taken by Paul Wilkinson and shared with a Creative Commons Attribution licence. Thanks, Paul.

1.0.1

• Tested up to WordPress 4.7.1
• Fixed bug if util.php was included in more than one built plugin.

1.0

• The first release