Tom McFarlin

Software Engineering in WordPress, PHP, and Backend Development

Page 245 of 428

User Onboarding with WordPress

Recently, Stephen shared an interesting site with me – User Onboarding – in which, as the site states, seeks to do the following:

User Onboarding is the process of increasing the likelihood that new users become successful when adopting your product.

Learn some lessons from how popular web apps do it!

It’s a really simple, straightforward site that highlights how various applications sign up, sign in, and continue using a product. Not only that, it also looks at what’s bad about the process, too.

User Onboarding

In short, it’s a great site to peruse (or to throw in your RSS reader) if for no other reason to check out some of the ways in which other companies attempt to garner customers.

But principles, by nature, tend to be transferrable (not always, but many times). This means that some of the lessons explored throughout the various teardowns the site does are applicable to onboarding users with WordPress.

Continue reading

The Planned Obsolescence of WordPress Themes

Last week, I shared a few thoughts on how I think that major updates to an existing WordPress theme are actually more analogous to a new product rather than an update of the existing product.

That is, if a theme is identified by the way it presents the content of the blog, then it stands to reason updating the look and feel of the theme is changing the very thing that gives the theme its identity.

So, from there, it’s reasonable to ask the question: Once a theme’s design is locked in, should it ever change?

Continue reading

Updated WordPress Themes Are Different WordPress Themes

Designers and developers, by their nature I think, are attracted to new things if for no other reason than to see how it’s designed, how it’s put together, how it functions, and so on. I don’t consider that a positive or a negative – it’s just a trait that some people have (and certain types of people exhibit it more than others).

New and Different WordPress Themes

That curiosity matched with the desire to constantly be improving at one does do for a living (or for a hobby) is what separates those who see the gig as “just a job” and those who see it as what they’re dedicating their lives to doing.

Yes – it can be expensive: Some like to purchase new devices as soon as they are released or new products as soon as they are released in order to familiarize themselves with them, and then to try to bring back what they’ve seen, learned, and experienced and build it into whatever they’re focused on creating.

But when you bring this approach into something like WordPress theme design and/or theme development, it has the obvious potential to improve future work but it can also negatively impact existing work.

Continue reading

Organizing WordPress Meta Box Code

When working with themes or public-facing views for a website, WordPress components can generally be thought of in three distinct areas:

  1. Templates are used for rendering the view (that is, the markup and the styles) of data.
  2. Partials are reusable fragments of templates.
  3. Helper Functions are used to help process, format, and generally work with data.

As far as templates and partials are concerned, these are relatively common with themes or working with anything on the front-end, but we don’t see it as much as we do when talking about the context of the Dashboard.

But when it comes to working with the back-end, all of these things are still applicable. Sometimes you’ll see them in isolation – like with helper functions – other times, all three things can work together such as in the case of meta boxes.

That is, you have a function for defining the meta box, a function for rendering the meta box (which can include a template), and then the template may have multiple parts – or partials – such as the contents for various tabs.

Continue reading

Display Post Meta Data Error Messages in WordPress

One of the things that’s nice bout working with post types – custom or standard – in WordPress is that it’s really easy to hook into the serialization process in order to handle the data. This means that we have the ability to sanitize, format, read, access, modify, verify, etc. all of the data with the post type and with the post type’s meta data before it’s written to the database.

WordPress has a pretty consistent way of displaying error messages throughout the application. Really, it’s pretty consistent in how it displays all types of messages – success, updates, and errors – throughout the  system.

Let’s say that you’re working with a WordPress meta box, several of its fields are required, and you want to:

  • verify the input has been specified
  • either display an error message if it’s not specified
  • or write the data to the database if it checks out

The serialization process is pretty standard stuff, but if you’re looking to make sure required fields aren’t empty and that a error message is displayed whenever they’re not entered, then you’ll need to do some additional work.

Continue reading

« Older posts Newer posts »

© 2026 Tom McFarlin

Theme by Anders NorenUp ↑