Category: Resources (Page 42 of 60)

A summary of useful links, applications, and tools that I find around the Internet.

Using CodeKit For WordPress Plugin Development

August 3, 2012 / Tom / 0 Comments

Earlier this week, I shared my approach to and the tools used for building a WordPress Plugin. In the post, I briefly touched on CodeKit, but I didn’t really talk about why I use it nor did I share how I configure it for my WordPress-based projects.

CodeKit is a platform-agnostic application – it’s meant for anyone who is doing web development – and it has been one of the single best tools that I’ve added to my WordPress toolbox in the past year.

The thing is, there’s a variety of ways to tailor CodeKit for your needs. It has support for LESS, Sass, a couple of JavaScript linting utilities, dependency management, minification, and so on.

Though there’s no single “right way” to configure it, here’s how I’ve been using CodeKit for WordPress plugin development.

Plugins For WordPress Developers

July 27, 2012 / Tom / 0 Comments

There are a number of plugins for WordPress Developers that I consider to be must-have for any local development environment. These include:

Theme Check
Log Deprecated Notices
RTL Tester
Debogger
Theme Unit Test even though is is technically import data

Each of these serves a unique purpose when working on themes and plugins especially if you care about localization and using the latest version of the WordPress API.

The downside is that it can be somewhat of a pain to install these each time you setup a new development environment (depending on how you actually setup your local machine).

But thanks to the guys over at WordPress VIP, this process for getting up and running with the necessary suite of plugins for WordPress developers is much easier.

WP Help For Creating Documentation Within WordPress

July 20, 2012 / Tom / 0 Comments

In my experience, one of the biggest pet peeves that others have with hiring developers to build a product for them, is that the client and the developer have completely different ideas as to what it means to be “done.”

By that, I mean developers (especially younger developers) consider a project to be done when the code has been written. But, come on, there’s so much more to it than that – aside from the usual staging enivronment, testing, and deployment, there’s also the issue of support.

Support looks different based on the nature of the product: Some may need on-going support via forums, some may need maintenance, others may need some form of documentation or a manual.

Up to this point, providing documentation for WordPress-based projects has normally been relegated to something like README files or websites, but as WordPress continues to become a more popular foundation for building not only sites and blogs, but applications, too, the need for solid documentation is only increasing.

Tips For Securing WordPress

July 13, 2012 / Tom / 0 Comments

I think that the general consensus is that WordPress is a secure platform – and in many ways, it is – but the truth is that it’s still software and that there will inevitably be bugs.

On top of that, if you’re in the business of building products – sites, themes, plugins, etc – on top of WordPress for others, then ultimately you – not the platform – become responsible for anything that goes wrong with the application or any security that arises.

But how do we know we’ve taken taken the necessary steps to make our work as secure as possible?

June 21, 2012 / Tom / 0 Comments

http://wordpress.stackexchange.com/a/55410/1014