One thing I’ve struggled with in the past when creating WordPress sites, is where to draw the line between the code that should be added to a WordPress theme and what should go into WordPress plugins. It’s usually not an issue on a smaller sites such as my own site, but when you start developing larger and more complex sites, things can get a bit hairy. I’ve worked on projects where we built everything into the theme. I’ve also worked on the complete opposite where almost the entire site was created using plugins. Naturally, the majority of the projects that I’ve worked on have gone for a hybrid approach of using both. The hybrid approach is the one that causes the most confusion, because the line between what goes where doesn’t really exist and constantly changes. Although all approaches have their merits, these days I feel quite strongly about creating modular plugins rather than sticking everything in the theme or going hybrid. There are a number of reasons for this that we will get in to shortly. Again, this doesn’t really apply to smaller sites but bigger feature rich websites. The relationship between features and functionality Traditionally when we think of WordPress plugins,
Share This

We are using cookies on our website

Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.