Systematize Plugin Development? OK, now based on the article title, you may be thinking that I’m actually smoking dope right now.
Like, come one now Andrew… there is no way to systematize plugin development since each product requires a custom solution, right?
True… to a point (not about smoking dope – but about a custom solution). 🙂
The fact is in every project there are always some repetitive processes that can be standardized.
And plugin development is no different.
For example, most plugins that have some degree of back-end functionality require an admin panel with navigation. One way to streamline development effort is to maintain the same general layout/look/feel between your plugins.
In this way your programmer just needs to start out with a template that already has the same snippets of code for the basic framework structure of your plugin. This will also save you time in creating a design mockup of your plugin to give to your programmer.
Another advantage to this approach is that your customers become accustomed to your style/branding and it won’t require as much time to understand how to navigate and use your plugins.
Take some time to develop a great looking back-end with a standard (but still flexible) layout and it will save you money in development costs, and give your products a signature brand that stands out against your competition. That’s one way you can systematize plugin development.