If you are looking for a solid foundation that follows WordPress Coding Standards and best practices from start to finish, look no further because Tom McFarlin developed and maintains WordPress Plugin Boilerplate which is ready to be adapted for your own plugins.
Each section of the boilerplate is commented in detail with links or instructions to why the code is being used which makes boilerplate very easy to follow.
If you do decide to use it, make sure to read through the comments and understand the reasons behind the code instead of doing a massive search and replace.
If you are developing for first time or even if you are an expert, WordPress Plugin Boilerplate is a quick way to get the foundation for your plugin quickly.
One issue that we constantly face while setting up Theme Demo for Avada is managing the huge multi-level menu for it from WordPress admin area. It takes ages to load and sometimes crashes the browser. It is really a huge time waste dealing with this.
Gladly, SevenSpark, author of Ubermenu has created a plugin to optimize the processing of WordPress menus area. You should read all about it on his blog post “Speeding up the Appearance > Menus Screen in WordPress 3.6” and give it a try.
If you do use this, consider supporting him by buying one of his great plugin.
If you offer sample content which is usually an XML file, for your WordPress theme, there is always a problem of either menu missing or theme menu using fallback method.
This can result in multiple supports tickets. The solution would be to automatically assign menu to theme menu location on after_setup_theme hook or on import_end hook.
Here is an example code which you can use to programmatically assign your registered menus to registered menu theme locations.
With the new guidelines set at ThemeForest and the continuous feedback from our users and the WordPress community, our job at ThemeFusion for the next 8-10 week is to make Avada a better theme.
Our primary goal with Avada 4.0 is to re-code it from scratch and follow the best practices and guidelines set by ThemeForest and WordPress community.
We are not going to kill features or stop adding new features for our users but we are going to change how we offer them.
Our goal is to change Avada into a neat framework to build upon for both general theme users and developers.
I’ll be making follow-up posts about Avada 4.0 and what I learn during the recode process which I hope can be helpful to other theme authors who are looking to make such changes.
If you have any suggestions, please feel free to post a comment or send me a tweet about it. You can follow me at @mharis on twitter.