I’ve been working on a small project, more of a web application than a site, that’s required the development of both a custom-theme and tightly coupled, but very specific functionality.
This is a very narrowly focused project (about which I’ll likely talk about at some point in the future) but in working on it, it’s forced me to get back into the theme development aspect of WordPress development a little bit.
No, I’m not doing any design – thankfully – but I am having to work on theme customizations from a functional perspective. In doing this, though, it’s had me revisit the required functions.php and some considerations I’ve never had before.
Furthermore, it’s caused me to look more deeply at the use of mu-plugins and ask when they are necessary and why I haven’t used them more in the past (or even when one would truly need to use them).
So I’m going to wax poetic about that a bit.
Functionality tied directly to the theme and WordPress core goes into functions.php. Domain-logic that required by the entire solution to work goes in a must-use plugin.
In previous posts, I’ve talked about the idea of focusing on an area and going deep rather than wide. This is personal preference, of course, but it’s mine, nonetheless.
Over the last year, though, one of the byproducts that I’ve found is the longer you stay in a given industry, the more common certain problems become. (This shouldn’t come as a surprise as this is precisely why we have design patterns.)
But the thing about doing this is that you develop a sort of tunnel vision for ways to solve problems.
Case in point: Recently, I was tasked with needing to develop some functionality that was going to parse markup and convert it into a slightly different format.
I try not to use Chrome but, from time to time, various applications or projects necessitate its use.
I still like the speed of the browser and I really like its debugging tools but the data collection that Chrome performs is one that I dislike and I see no reason for the organization to change its practices. For more information see this, this, this, and this, and this.
And sure, some of the above advice is anecdotal but these are just some of the more common things that people are going to come across if they start looking into what the browser is doing. There are plenty of deeper analyses of what the browser does from a deeper technological standpoint.
But the purpose of this post isn’t to digress into all of the things that Chrome is doing (the when, how, and why), but instead its about sharing extensions that I’ve found to be useful when using Chrome.
I really have no idea how to even start writing out all of things that I want to cover in this post. It’s been a bit of while since I’ve written anything, really (and one of the last programmatic post I wrote was sometime ago – and no, I don’t plan to stop the series).
Over the past few years, I’ve written about taking time off of social media during certain parts of the year. I still plan on doing that, but this post is a bit different because it’s going to cover a lot of things.
If you’re interested in how I’ve done this in the past, take a look:
With that said, I think I’m going to leave that there and move on to issues that are more relevant to the blog. Namely, an update as to what’s up, some thoughts I’ve had around this blog, and some changes I’m aiming to make in the near future.