Themes are for presentation, plugins are for fu... || When it comes to working with WordPress themes and plugins, there’s a general rule of thumb that most experienced designers and developers follow: Themes are for presentation, plugins are for functionality. Sure, there’s a little bit of blurring of lines, but this is the goal for which we strive when working through our code. And yes, there’s a lot that can be said (and has been said) about themes that include a ton of features, options, bundled plugins, and so on, but that’s not where this is going. Instead, I’ve been thinking about how this relates to general theme development, niche theme development, and using WordPress as a platform for application development. Theme-Specific Plugins I think the majority of developers agree that we need to be separating our presentation and our functionality as much as possible. Part of this is so that we have a logical separation of concerns, but another bit is that it makes it easier to port data between installations. By that, I mean that we’re able to take a given blog or WordPress-based site and change the theme without losing data or information at the presentation-level. Similarly,
Share This