Introducing Automated WordPress Plugin Boilerplate

I’ve created a forked version of the popular WordPress Plugin Boilerplate. This new version uses a python script/GUI that completely automates the renaming of every file, every function, and every class name. No more missing a file name or function to match your new plugin name.

Check out the README and follow the instructions on the repo to get started. Questions, comments, feature requests are all welcomed.

WordPress and Automating – Using Gulp for WordPress Automation

Gulp can help you automate daily routine tasks. In this article you will see basic stuff you can automate doing WordPress development. Lets see how gulp can save you a healthy amount of time every day and improve the quality of your product too. | Difficulty: Beginner; Length: Short; Tags: WordPress, CMS, Web Development, JavaScript, WordPress Plugins

Source: Using Gulp for WordPress Automation – Tuts+ Code Tutorial

[WordPress] Resource – Loading Parent Styles for Child Themes

The always insightful Justin Tadlock has posted a great post on how best to handle stylesheets in child themes. Though there are many options for this, including the infamous @import technique, Justin recommends loading the styles directly from the parent theme itself. It’s a simple but effective solution that should work for 99% of cases.

Loading Parent Styles for Child WordPress Themes.

Adding Custom Header Images to WordPress.org Plugins

While reading WPCandy’s “Recap: Matt Mullenweg’s 2012 State of the Word“, I came across a note about custom plugin header images.

This may not be news to some plugin devs, but you are now able to use your own custom header image for your WordPress plugins hosted on WordPress.org.

If you don’t spend much time browsing the actual plugins directory, you may not have noticed this. A great example of a custom plugin image in use is the infamous “Hello Dolly” plugin hosted on WordPress.org.

Hello Dolly WordPress Plugin Showing Custom Header
Hello Dolly page showing custom header image in use. Click for larger view.

The image needs to be a 772×250 pixel jpeg or png. This goes into your plugin’s SVN directory with the path assets/banner-772x250.(jpg|png).  Resources to get started with custom header images for your WordPress plugin:

Be warned, Matt has stated that this will most likely change in the future. If anyone has any more up to date details or resources, please let me know in the comments.