Full rewrite is in order. Notes inside.

[danieliser]

The boilerplate as it is now is not very useful. It is both bloated and lacking at the same time. There is typically a lot of removal of code & extensive file building required after initial setup before a product can even become a reality.

Plans

Build a fully functional multi faceted boilerplate with a little bit of every type of extension we currently have including:

• Mailing list integration
• New Triggers
• Extra Global Settings
• Extra Theme Settings
• Extra Popup Metaboxes
• Extending existing settings
• Adding additional admin pages to our menus
• Custom Admin / Site CSS & JS files

Once this is done, a build process will be built to optionally enable/disable each of these items. The build will also collect plugin details and replace prefixes automatically. Once build is finished it will be saved in its own folder with the collected plugins slug. After build is complete the extension will be a raw & ready to add in your customizations. This means that within minutes a new extension can be ready for building, and the focus is only on the new functionality.

@fpcorso Thoughts?

[fpcorso]

I think the build process is a great idea. I like being able to run a quick build script to generate the raw extension I need. This would save quite a bit of time.

Are you thinking about having a complete build built and added to the repo or would you require 3rd party developers to have gulp experience to be able to run the build process to create the build using the options they need?

[danieliser]

Plans are to build it with an example of every item. If they don't check a box on the packages checkbox question then those items will be stripped out. The search and replace full plugin wide is done.

If they don't use gulp then they can simply replace things manually & strip out un needed stuff.

There are a dozen ways to do it really. We could make a separate branch for each feature set, then use gulp to download the right branches for the options chose and merge them.That also allows us to have a repo for each. So if you have to manually do it you could start from a blank with only one feature.

IDK, open to suggestions. Would like to make it easy to update & manage.

[danieliser]

If they don't have gulp, they should get it ;)

I mean I've been using it for like 2 weeks and was able to basically build a prototype for this that will already save hours per extension in less time than it usually takes to do it manually for one extension.