Tag: WordPress (Page 104 of 219)

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

CLI: A Cheatsheet For The Command-Line

March 11, 2016 / Tom / 0 Comments

The CLI is one of those tools that I think every developer should know how to use even if they don’t use it consistently. After all, we have plenty of applications for taking care of tasks, right?

The thing is, from time-to-time, it’s useful. During the process of working on projects, you may be hopping back and forth between an IDE, an SSH session, S/FTP, a task runner, debugging, and so on.

Sometimes, particularly in the beginning, it’s hard to juggle all of the commands in your head.

Though I love using applications to help take care of certain tasks, I’ve never fully let the command-line go. Sometimes, it’s just faster to type out a string of commands and let them do their work rather than poke around a number of different applications.

Maybe that’s stubborn. I don’t know. But what if you’ve not used the CLI? How do you maintain a quick reference to the available commands?

The Perfect WordPress Development Stack

March 9, 2016 / Tom / 0 Comments

The “Perfect WordPress Development Stack” is one of those topics that comes up now and again in various blogs (and here it is again – how meta, right?), talks, tweets, and so on.

And I think it’s a good point of conversation. If you’re working with WordPress in a professional capacity, then you should have a stack that maintains some level of professionalism.

But what does that look like? It’s likely that some of you know where I’m going with us and the answer may sound like a cop-out.

It’s not, though. It’s generally what I’ve found to be true.

Deregistering WordPress Stylesheets

March 7, 2016 / Tom

Deregistering WordPress stylesheets is one of those things that we don’t always have to consider.

If you’re starting a project from scratch, then it’s usually safe to say that you’re starting a project at ground zero and have control over most of the assets that are to be enqueued in the project.

On the other hand, if you’re coming into a project at a later date or you’re working on a plugin that has to work in conjunction with another plugin that might use a shared stylesheet then you may need to deregister an existing asset to make sure everything works well together.

Using PHP CodeSniffer with Atom

March 4, 2016 / Tom / 0 Comments

Using PHP CodeSniffer is one of those tools that is part of my workflow that I find utterly invaluable. I haven’t always used it, though.

Don’t get me wrong: If you’ve read this blog for any length of time, you know I’m big on Coding Standards. But when it came to the PHP CodeSniffer, there was an extended period I had gone before I installed it.

Why, though?

Simply put, it was because I didn’t know it existed, at least not for WordPress. When I discovered there was a ruleset for WordPress (and WordPress VIP), it became something that I believe should be a necessary tool in every WordPress developer’s toolbox.

Depending on your IDE, you may or may not be able to install a plugin or an extension that will automatically monitor your code while you’re writing.

I made the change to Atom some time ago, which I’ll share more about momentarily, and it has excellent support for incorporating PHP CodeSniffer into your workflow.

Sharing GPL Code and Its Ethics

March 2, 2016 / Tom / 0 Comments

“Sharing GPL Code” sounds like such a loaded title because the topic is forever hot. But hang with me because the purpose of this post has nothing to do with actually arguing for or against the GPL or code around it.

I know the simple answer is that all GPL code, by very nature of its license, it’s available for sharing, but there’s another aspect that plays into this I want to discuss.

Sharing GPL Code can be more about collaborating on code, right?

And that’s this:

What is the ethics of sharing the code for a project that you’ve built for someone else even if it maintains the GPL?

For the most part, I think it’s fine. But when you’re running a business and you’re building solutions for clients, there’s a little more to it.

At least, that’s my experience.