Advantages and Disadvantages of WordPress Frameworks

The concept of a WordPress Frameworks is something that’s very common both within the modern web and within the software development environments. For the front-end, we have frameworks like Bootstrap and Foundation, for web applications, we have frameworks like Yii and Rails, and for desktop (and even some web applications) we have frameworks like .NET. And these are just to name a very small and select few.

WordPress Frameworks

Generally speaking, WordPress Frameworks are good: They provide a level of abstraction with which we, as developers, can work with in order to easily create generic functionality – such as user login and authentication – along with more specific code, such as logic that’s specific to whatever the problem is that the software is aiming to solve.

In short, Wikipedia defines a framework as follows:

A software framework is a universal, reusable software environment that provides particular functionality as part of a larger software platform to facilitate development of software applications, products and solutions. Software frameworks may include WordPress Support programs, compilers, code libraries, tool sets, and application programming interfaces (APIs) that bring together all the different components to enable development of a project or solution.

As with many modern platforms, WordPress is no different. Of course, WordPress itself is not a framework – it’s an application that can be extended through the use of its many APIs. But there are a number of different frameworks that are available all of which aim to help ease the burden of writing a lot of repetitive code.

But is this a good thing? That is, does it make sense to have so many choices of frameworks from which to choose as it relates to building WordPress themes, WordPress plugins, or web applications based on the platform?

Usually, it depends on what you’re trying to do.

Throughout the Tuts+ properties, we try to cover as many frameworks as possible – some for WordPress, some for the various languages and platforms that were mentioned earlier – but in this article, we’re not going to be looking at a specific framework.

Instead, we’re going to be looking at the advantages and disadvantages of selecting a framework when working with WordPress to help make better decisions as it relates to building sites, applications, and other projects on top of WordPress.

With WordPress, it’s completely possible to mix various frameworks in order to achieve your end result, this article assumes that you’re evaluating whether or not to use a single framework in order to help with your work.

As far as WordPress is concerned, there are currently (and generally) two types of frameworks:

  1. Drag and Drop Frameworks
  2. Options Frameworks

Drag and Drop WordPress Frameworks are usually related to building the user interface of a website. Often times, these come in the form of various pages in the WordPress forum Dashboard that allows you to arrange pre-defined elements on a page and have them render in a said arrangement for the user to see.

Options WordPress Frameworks, on the other hand, are usually used for code-specific functionality and usually provide some type of abstraction for one or more of the WordPress APIs. This includes, but is not limited to, the Settings API, the MetaData API (for Posts, Users, Comments, and so on), and even some of the APIs related to templates.

Whatever the case, there are both advantages and disadvantages that come with choosing a framework all of which are important to consider when determining whether or not you’re going to work with or without a framework.

One of the major advantages of using a framework is the speed at which you’re able to assemble functionality.

Sometimes, people will refer to this as rapid prototyping, but WordPress Frameworks have matured to a point such that you can often get away with creating full-on interfaces, sites, and applications – not just prototype – when working with the API.

Though building content-driven sites with WordPress out-of-the-box is straightforward enough, many frameworks – especially drag and drop frameworks – make it that much faster to create more elaborate page layouts.

For frameworks that primarily deal with WordPress’ APIs, frameworks can provide a nice level of abstraction such that much of the repetitive code that we’re used to writing is tucked away within the framework.

Perhaps one of the best examples comes when looking at frameworks for the Settings API. The Settings API, although powerful, is also verbose and cumbersome when it comes to getting elements to display on the screen. Frameworks seek to solve this problem by providing a way to more easily create settings, options, and settings with fewer function calls and clearer code.

Of course, abstractions comes not just with the Settings API but for other APIs, as well. Opting to use one of these frameworks can save a lot of time and help ease the tedious nature that comes with working with some of the more repetitive aspects of the WordPress-based code.

Another advantage of using WordPress Frameworks is that it helps bridge the gap between what we’re expecting to happen and what really happens.

This is most easily seen within drag and drop frameworks: You have a predefined set of regions with which to work such as headers, sidebars, content areas, and footer areas, and then you place the regions where you’d like within a container. Once done, said regions appear exactly on the front-end as you’ve arranged them on the back-end.

The same can also be said for API-specific frameworks, too. Although the visual nature of writing code isn’t as clear as working with a page template editor, good frameworks can often provide clear classes, function names, and other facilities all of which help to more easily understand how all of the moving pieces of the software fit together.

One such example may come in the form of creating a setting in the WordPress Dashboard. Say, for example, you want to introduce a textarea that is only going to support plain-text (that is, no markup or scripts allowed), and you need to label it, sanitize its data, validate its data, and display its data.

Using a framework, what may take three different function calls and at least two callbacks to do can be done in a single function call with perhaps one or two callbacks. On top of that, the function names are a bit clearer and are more indicative of the work they’re doing and the type of elements with which they’re doing it.

On the flip-side, if you opt to use a framework then you’re automatically creating a dependency between yourself, third-party code, and WordPress.

This means that if your code is based on a framework, and that framework is based on WordPress, then the abilities of the framework are limited only by the most recent version of WordPress that it WordPress Support.

If the framework stays up to date with WordPress as it undergoes development, and the framework is released along with the major updates of WordPress, then keeping your code in sync with the most recent developments is easy.

On the other hand, if the framework lags behind the most recent version of WordPress, then your code can only be as updated (and as secure and reliable) as the most recent version of WordPress that your framework supports.

Another challenge that comes with using frameworks is that many times, frameworks are elaborate wrappers for existing functionality that exists within WordPress. To that end, there are going to be times where frameworks provide access to functions that may not always be available as WordPress is updated.

Say, for example, you have a framework that provides access to a certain API that becomes deprecated in the latest version of the core application. Furthermore, the framework does not properly deprecate its code until another release cycle.

This means that the code that you’ve written based on the framework is using deprecated function calls. For a release or two, this may not be a big deal, but once that functionality is gone from the core application and the framework hasn’t addressed this, then you may not be able to use the latest version of WordPress or some of its newer features because the framework hasn’t properly deprecated its code with that of core.

WordPress Frameworks can be really powerful, but when it comes to using them, it’s often times a good idea to go “all-in.” That is to say that when you use a framework, it’s usually nice to write all of your code using the framework rather than some of the code using the framework and some of the code using the WordPress APIs.

In other words, you don’t want to mix the code that you’re writing such that you have a bit of a hodgepodge of code that’s sort of based on a framework and sort of, you know, not based on a framework.

After all, the purpose of a framework as defined earlier is to provide an abstraction for generic functionality.

To that end, if a framework is an incomplete or lacking functionality specifically for something that’s provided with WordPress core, then you’re left with one of two options:

  1. Forgo the feature that you want to use and wait for the framework to make it available,
  2. Side-step the framework and use core WordPress code alongside your framework-based code in order to achieve the desired result.

Initially, it seems clear that if the framework doesn’t offer something that you need, then simply use what WordPress provides. But when you do this, you’re mixing the type of code that you’re writing such that you’re introducing a level of complexity when it comes to maintaining the software.

If a framework later introduces a set of features that cover what you once wrote as vanilla WordPress code, you’ll be tasked with updating said code to conform to that of the framework. From there, if the framework isn’t continually updated to stay current with WordPress, then you’re back at the dependency and deprecation problems.