I’m not one to usually start a blog post with “it’s been a while since I’ve last blogged” because it’s usually followed by an apology as if the people who consistently read the blog or follow the blog have been waiting with bated breath for the next post to come out.
But is that ever really the truth? I can’t imagine that scenario.
That doesn’t mean I’m not doing that with this post, though. Because it has been a while since I’ve blogged. I’m not going to be making any apologies for it, though.
Instead, how about a few updates as to what’s been going on and what I’m planning to do with the rest of the year?
One of the things that are all too common, though, especially as it relates to the administrative area, is loading assets in WordPress on screens where they aren’t needed.
It’s completely possible to make an argument that given the file sizes or the functionality that each present, the files are only impacting a minimal amount of load time at best, right?
But match this mentality with who-knows-how-many plugins, and you’ve got more than a heavy impact happening on a given payload.
So what can we do?
As with many other blogs, shops, products, and services during this time of year, I’m offering discounted memberships on this blog from Black Friday thru Cyber Monday.
What does this really get you, though?
As is the same with every single year (well, save for last year when I forgot to write a post – or simply neglected to do so 🤷🏻♂️), we’re celebrating Thanksgiving in the United States.
I dig this time of year and continue to do so the more our family grows, and the more time we’re able to spend together.
You’d think in 2018 we’d have a standard way to do browser detection or that the majority of browsers would handle standard idiosyncracies around CSS properly.
But here we are, and it’s still not happening.
Don’t get me wrong: It’s not as bad as it used to be, but there are times in which I’ve recently encountered errors with Chrome and Firefox, specifically.