Category / Articles

If you’ve ever used Bootstrap, you know it’s easy to setup; however, if you’re looking to introduce more complicated functionality such as having to make asynchronous requests whenever the pages tabs change and then you need to update the DOM accordingly, it can actually be a little frustrating in nature.

Sure, there are some ways in which you can track which tab is active – class names, using hidden fields, etc., but depending on how you’ve architected the front-end and what’s happening with the Ajax response, you may actually end up with needing to do something a little more advanced than that.

Generally speaking, whenever I’m working with JavaScript and I’m trying to handle an asynchronous event (or even synchronous events, for that matter), I want to use exactly that – events.

But when it comes to needing to handle when a tab has been changed to toggle a pane in Bootstrap, what event do we use?

Some of the developers and designers who I admire the most in the wider development community are really good about being open about various aspects of their businesses. Sometimes they talk about their challenges, sometimes they do financial reports, and other times they cover different topics.

I’ve slowly been trying to share some of my own experience as it relates to self-employment. It’s not meant to be prescriptive or meant to be a guide on how you should do anything, but it’s something that I hope proves useful if for no other reason than to show what’s worked for me.

So in this post, I thought I’d share how I’ve gone about managing my books – or how I’ve done self-employment accounting – since working out of Pressware.

If you’re a developer working in WordPress, then odds are you’ve spent time working with designers. Assuming you’re working with a good designer, it can be a lot of fun.

I think we’ve all had our share of experiences both good and bad (and luckily I’m at a point where I’m working with some really great designers), but I think there are things we – as developers – can do to help make our designers jobs a little bit easier.

I guess the question should be a bit more specific:

— How do you manage content ownership with photo sharing services?

Sure, we could talk a lot about a number of different services that allow you to share content – links, videos, short form content, even blog content – and so on, but photo sharing services are kind of all of the rage right now.

And I completely understand why, too. But I’ll come back to this in a minute.

With that said, I’m genuinely curious about everyone’s opinions as it relates to services like Instagram and other similar applications.

A couple of weeks ago, I worked through a series of posts on how to write a TinyMCE plugin for the WordPress editor (since the WordPress Editor is TinyMCE).

In a recent project, one of the things that I needed to a build was a feature that allowed users to highlight text such that they would select the text in the editor (you know, with their mouse), click on a “Highlight Text” button in the toolbar, then have the text highlight.

And, naturally, it would return to its normal state of being un-highlighted if the text is selected and then the toolbar button is clicked again.

Though there’s no reason to share how the plugin is built in its entirety, I thought I’d walk through how I added the new command to the toolbar and used the HTML5 `mark` tag to include this functionality.

/ August 19, 2015 / Comments Off on The Dangerous Nature of WordPress Comments (And What I’ve Learned)

The Dangerous Nature of WordPress Comments (And What I’ve Learned)

When it comes to posts like this, I often deliberate for weeks on whether or not I should write them because of the various discussions that it will inevitably cause and the blowback that can occur can often times be exhausting (even if it’s deserved).

But that’s not this kind of post. This is a retrospective of my own mistakes, my apologies, and what I’ve learned about moving forward in certain types of situations. More on that in a moment.

Right about now is when the defenses start to go up. Please don’t go into this post with that attitude as it’s not at all about anyone or anything but me. If you already feel like you’re on the defense, take a look at this cool picture taken at River Street in Savannah, Georgia.

One of the things that seems to be unique to open source is many opt to share their annual reports of their business regardless of how the business performed over the year. Others also talk a lot about their mental health – again, regardless of if it’s good or bad. And when you’re part of a larger group of people who are doing the same thing, it’s really inspiring, educational, and also prompts you to aim to be a better friend and peer. An amiable goal by any measure.

In short, it’s something that’s really cool to see even if you opt not to disclose that information yourself.

However, one thing that we don’t see as much of – not because people don’t share it, but because it doesn’t seem to be as popular to share – is the idea of developer fitness. I know people are involved in all kind of things offline. For example, I know Sean Davis hosts a number of workout contests and is also involved in a number of different sports (most recently, racquetball based on his Twitter feed). I also know that Sunny Ratilal shares his FitBit progress throughout the week giving insight into his level of activity.

Cool, right?

Anyway, the point is that I know we’re all active in different ways but we don’t blog about it as much for whatever reason. And I get it: Talking about health, fitness, and exercising is boring. Or it can be boring. It can also be a lot of fun depending on if you’re found the right kind of workout for you (more on this later).

/ August 13, 2015 / Comments Off on Hey Programmer: Don’t Be a Jerk

Hey Programmer: Don’t Be a Jerk

To be liked, respected, and treated well within the open source development community, I think a lot of it comes down to a single point:

Don’t be a jerk.

But, for whatever reason, human nature compels some of this to ignore it and some of us to carry on doing the same thing without any regard for the rest of the people that we’re targeting.

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.

Occasionally, I’m asked for two quick tips or suggestions that I have for those who are just getting started with writing WordPress plugins.

The assumption is that they’ve done all of the necessary leg work to get to the point where they are comfortable writing code and working with WordPress, but they want to avoid some of the pitfalls that many (or most?) of us experience when we first get started on our own projects.

There’s a plethora of tips that I could be shared so maybe this will end up with some additional comments, or maybe this will lead to a series of posts. Whatever the case, there are two completely arbitrary things that I think most developers should know if they’re writing WordPress plugins.

Starting with WordPress?
I recommend Array Themes
Array Themes
Hosted By
Hosted By SiteGround