Author: Tom (Page 101 of 428)

Configuring Composer for WordPress, Part 1

September 12, 2017 / Tom

Okay, so after talking through all of the various libraries that can help improve the code quality of your work, it still raises a question:

How do we get these projects working against our code base?

In short, it requires Composer. If you’ve never used it, I’ve written briefly about it before, but I intend to provide the basics of what you need to get started using it and the aforementioned libraries in your work.

In both this post and the next, I’ll share how to set up everything locally in the most basic form and then how it integrates with Git so you can start using it in your day-to-day.

Libraries for WordPress Plugins, Part 3

September 11, 2017 / Tom

In the last three posts, I’ve talked about libraries for WordPlugins that I find to be extremely helpful in writing high-quality codebases.

If you’ve not been following along, you can either catch-up by reading the previous posts:

Or you can just review the list of tools I’ve listed thus far:

This post will wrap up the series with the final set of tools that we typically use when building solutions for others.

Libraries for WordPress Plugins, Part 2

September 8, 2017 / Tom

Yesterday, I started a short series of posts covering tools that I think make for writing high-quality code in a WordPress project (specifically those that are plugins built using an object-oriented approach).

If you haven’t read the post, the first set of tools mentioned are as follows:

There are about five more tools that I like to keep running on my projects. So here’s the next three with the final two coming in the next post.

Libraries for WordPress Plugins, Part 1

September 7, 2017 / Tom

The more you work with WordPress, especially if you employ tools like Composer and the like, the more you’re likely going to find certain libraries, tools, and similar things that form the foundation of projects on which you work.

Sometimes you may find them when looking through other people’s code, maybe you’ll find them when browsing GitHub, or maybe someone you work with will suggest a library (or a few) depending on a project.

Personally, I’ve had the experience of all of the above, and the more I work on building solutions for myself or others, the more I find myself setting up the same foundation for each project (which is typically a plugin of some sort).

Should We Let Tools Dictate Our Projects?

August 31, 2017 / Tom

Does it make sense to use a different development stack or set of tools depending on the type of project you’re using even if it’s built on WordPress?

To give a little more context, I’ve written both about using tools like CodeKit (that bundles a variety of tools together to help streamline development).

Let Tools Dictate Your Project: CodeKit

And I’ve also talked about using things like CircleCI which are used in more enterprise-grade environments (but work just fine for smaller projects, too).

Let Tools Dictate Your Project: CircleCI

So when it comes to working on something alone or with a team, what’s the best thing to do?