Author: Tom (Page 175 of 430)

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.

Preparing To Launch Pressware Plugins

March 8, 2016 / Tom

Pressware Plugins is something that I talked about at length a few weeks ago.

Pressware Plugins For a Better Blogging Experience

Maybe this goes on too much promotion for it, but we’re finally getting ready to launch the site – I’m excited – and I want to make sure that I’ve taken all available opportunities to share things on which we’ve been working.

The short of it is this:

We’re going to be launching the site later this week, and we’re going to be contacting everyone who has subscribed to the mailing list about it first.

If you’re interested, head over to the site and sign up.

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.

Digest For February 28, 2016

March 5, 2016 / Tom

I typically don’t post on Saturdays, and I usually let those who have signed up to receive emails via Postmatic get their summary via email once a week.

Time

But not everyone reads blogs the same way, and not everyone subscribes via email, so I thought I’d try something new. That is, this is an experiment (and I invite your critique at the end of the post).

With that said, here is a summary of the posts from this week.

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.