(Note: If you are subscribed to one of our plans, you can grab this file from the forums. Don’t worry we have many other Thesis 2 skins and Genesis child themes – check out the full list here.
Let’s shift gears and consider Word Press Themes, which are essentially just a combination of structural templates (HTML) and style (CSS). If you examine any Word Press Theme in detail, you’ll notice a of repetition between various templates and template parts.
Because of this repetition, attempting to change one thing in a Theme often necessitates changes to many different templates.
And as we’ll soon discover, the utility of Boxes isn’t limited to templates and HTML output.
In reality, Boxes are the perfect way to deliver —simply having options appear in an interface—isn’t the full picture.
No matter where you’d like to convey options, you are going to be working with these basic input types.
Instead of leveraging these natural patterns and accepting a single, intelligible syntax for options, Word Press accepts a different syntax depending on where you’d like to convey your options.
This is grossly inefficient and fails to leverage patterns that could make this process easier.
To rectify this, the Thesis Options API establishes a single syntax for options elements called the Thesis Options API Array Format.
Here’s how the basic process works: by having an inconsistent and disorganized approach to options that appear in different locations.
For example, there are 4 major locations within Word Press where a developer might want to add options: In what can only be described as pure madness, Word Press accepts options in a wildly different format for each location. The HTML specification consists of a finite number of input elements, and you only need a few of these elements to do practically anything: There are very clear patterns in play here.