Software Engineering in Web Development, Backend Services, and More

Tag: WordPress (Page 145 of 220)

Articles, tips, and resources for WordPress-based development.

Use Source Control and Diff Tools with WordPress

Every now and then, developers will ask – or will be asked – what is one of the most important things I should learn in order to get involved when writing code?

Obviously, this assumes that the person already knows how to write code, likely knows how to upload a site or compile the source code into an executable or any of that, but maybe they’re looking for something to amp up their development process.

Whatever the case, the rest of this content is for those who have been working with WordPress for a while, but are looking for some additional tools to help improve their development-fu. If you’re an intermediate to an advanced developer, this may not be of much interest.

But for the rest of you, I can’t recommend source control and differential utilities enough when amping up your development.

Continue reading

Premium or Commercial Themes (Which is it?)

One of the discussions that I’ve seen crop up more than once is the debate as to which should those themes for which we pay be called Premium Themes or Commercial Themes.

Though I personally call them Premium Themes, there have been times in which I’ve casually referred to something as a Commercial Theme. And this is something that we could all debate ad nauseum and probably still not come up with a definitive answer, so I realize the potential futility of writing a post like this, but my curiousity is piqued:

What is the best term to use when talking about themes that much be purchased?

For me, it’s a matter of looking at the basic definitions.

Continue reading

The WordPress Post Editor Doesn’t Suck (Though We Might Be Lazy)

There was a great article written on WP Tavern yesterday entitled Why WordPress Doesn’t Need To Fear Ghost, Yet.

And before I go any further, I want to be absolutely clear that as much as I know that people who are involved in WorPress love a good dramatic story – especially one that involves mudslinging and controversial statements that generate all kinds of fun conversations in comments and on Twitter – this is not one of those stories.

WP Tavern

Don’t read it that way, don’t spin it that way, and don’t try to twist any of the words that are in here as that’s that the purpose of what I’m trying to say.

Instead, this is my take on two of specific topics that were discussed in the article.

Continue reading

A WordPress Theme Development Process

Although I still stand by the idea that we all have the ability to decide how complex or how simple we create our themes, I do think that there’s something to be said for identifying the core problem a given theme is trying to solve.

That is to say, is a given theme trying to:

  • Target landing pages for a certain type of niche business?
  • Create a reading experience that looks ideal on mobile devices?
  • Serve as a tumblr-esque type of blog?
  • Meant to serve as an online journal for, say, photos or music or videos or something similar?
  • …and so on

In short, I think that when someone asks you “what does your theme do?” or “who is your theme for?” then you should be able to quickly give an answer. Saying something like “this theme is for the small business owner who runs a restaurant, or a body shop, or a photography studio, or a convenience store” is too broad.

If we use personas as a way to identify who our themes are for, and a persona represents an actual type of person, then doesn’t it seem highly unlikely that a person who runs a restaurant may also be the type of person who is a mechanic and/or a photographer?

What I’m trying to say is that whenever we sit down to begin planning out and building our themes, I think that we need to do a better job of identifying both who the theme is for the and what the problem space is that we’re attempting to enter.

Some personas should be taken more seriously than others, I think.

Some personas should be taken more seriously than others, I think.

Of course, this isn’t to say that some teams don’t already do this. In fact, I can think of quite a few who do and who do it really well. Other times, though, I think that many try to create themes more or less to show off what they can do with WordPress rather than to truly serve a need that a potential set of customers may have.

So where do this leave us? That is, how can we do a better job of approaching theme development in such a way that’s it’s solving problems and catering to a certain type of customers rather than just trying to be the next flashy product that offers n-number of a features and m-number of options?

Continue reading

How To Remove TinyMCE Buttons From WordPress

Depending on the level of customization or the level of formatting your customer wants or you want to give your users as it relates to the WordPress post editor, you may need to remove TinyMCE buttons from the WordPress editor.

Although it’s relatively easy to remove all of the buttons and, say, focus only on the HTML view, it’s also possible to remove individual buttons from the post editor so that the user only has a subset of the options that are typically available.

TinyMCE Buttons

TinyMCE Buttons

Say, for example, you want to remove everything from the second row exception the formatting drop-down that let’s you select the heading size, paragraph, or pre elements. It’s easy to do this using one of the hooks that WordPress provides.

Continue reading

« Older posts Newer posts »

© 2026 Tom McFarlin

Theme by Anders NorenUp ↑