Tag: WordPress (Page 37 of 219)

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

Triggering Angular Events with jQuery (As Weird As That May Sound)

August 23, 2018 / Tom

One of the things that I enjoy about working with WordPress is the ability to bring in third-party libraries and tools with which to work.

This doesn’t mean they don’t come without their learning curve (they all do, right?), but it’s often fun – albeit frustrating, at times – to incorporate and then manipulate what you’re doing.

As far as third-party technologies go, I’ve seen people bring things in such as the Laravel Illuminate package with WordPress.

Triggering Angular Events with jQuery: Illuminate

And I know, especially in recent years, many have brought in components such as React and Vue.

Triggering Angular Events with jQuery: React

In one such instance, I’ve been doing some work with Angular. And if you’re used to ES6, vanilla JavaScript, or using jQuery, then triggering Angular events with jQuery can seem a bit weird at first.

Triggering Angular Events with jQuery: Angular

But once you understand the markup and how Angular handles its events, it’s not so bad.

Now Offering Two New Benefits for Site Members (With More to Come)

August 22, 2018 / Tom

One of the things on the backlog of things that I’ve been working to do is to put together a list of benefits for members. Here’s the thing, though: The WordPress economy is vast, so what one person can do or from what they may benefit is not going to be the same as what another person can do or benefits.

What’s to be done about that?

Regarding providing solutions for the site, the current state of memberships on this site is easy to define:

offer object-oriented introductions and practices,
practical tips for how to achieve specific tasks,
how to apply all the above in your day-to-day work.

But that’s not all I want it to be. In addition to all of that, I also want to provide members with access to software, courses, and more than help them get better at what it is you do on a day-to-day basis.

And that’s what today’s post is about: Finally announcing a couple of benefits for site members.

Organizing WordPress Types, Views, and Subscribers

August 15, 2018 / Tom

One of the things that I find myself trying to do on a regular basis is to streamline how I’m building WordPress-focused functionality. I’ve recently talked about this but thought I’d expand on it a little bit more.

That is, I thought I’d lay out the approach I take when building things such as custom post types, taxonomies, meta boxes, and so on.

Generally, think of this as a strategy that I follow for building out aspects of a project that interfaces directly with WordPress but may require a few components such as:

classes that register themselves with WordPress through various hooks,
classes that require calls to certain WordPress APIs
and classes that require a custom view.

Sure, not every thing that interfaces with WordPress will need all of the above (for example, does a custom post type need a view? No. But a meta box does.)

On Writing Readable WordPress Functions

August 14, 2018 / Tom

One of the things that I find consistently interesting (both from a programming standpoint and from a WordPress standpoint), is this:

I like keeping code separated such that code responsible for interacting with WordPress is relegated to its namespace while the rest of our code is namespaced appropriately elsewhere.

I think this is obvious, though.

When it comes to writing code, though, this doesn’t mean it has to be left simply to the how we write our classes and then organize them. What about things at a slightly more granular level?

That is, what if we were to look at methods as part of the larger whole and make sure they’re doing their job well, too? Sure, people like Bob Martin have been writing about this kind of stuff for the majority of their career and preaching it to people like us.

But these concepts are something that you simply start doing and then apply them for good. Paradigms shift, we’re better today than we were yesterday, and there may be multiple ways to achieve the same kind of thing.

So when it comes it comes to creating readable WordPress functions for a specific domain, what might that look like?

A Simple Guide for Organizing WordPress-centric Classes

August 9, 2018 / Tom

One of the things that I’ve been making a much more concerted effort, likely more so than I’ve ever done before, is managing separation of concerns between the classes responsible for interfacing with WordPress and those responsible for working with the problem domain.

For instance, let’s say that you’re working on a plugin and it’s going to communicate with a third-party API. Additionally, this plugin will also offer menus, post types, taxonomies, and so on within the WordPress administration area.

There are two areas of responsibility here:

the area responsible for generally solving the problem,
the area responsible for interfacing with WordPress.

You can make the case that it’s important to unit test areas that communicate with WordPress, but I also know these are tried and true APIs that have their own set of tests.

Instead, we should be focusing on unit testing and separating our business logic away from WordPress.

But that’s not the point of this post. Instead, it’s more about a way to potentially lay out a project when a portion of it will be interfacing with WordPress.