I’ve released my first plugin for WordPress, WP-Prowl. You can download it at it’s WordPress Plugin page. If you’re interested, please try it out and let me know what you think!

If you want to know more about it, please visit my WP-Prowl page. You can leave me a comment here if there’s anything you’d like to say about the plugin. I welcome all criticisms and suggestions!

I’m working on a WordPress plugin, my first one. The goal is to integrate Prowl notifications into WordPress. If you aren’t familiar with Prowl, it’s a fantastic utility for sending Growl notifications as push messages to your iPhone.

That’s great, if you want to send messages from your Mac over to your iPhone. I use it on my headless media server to give me information about what it’s up to, such as finished downloads, trouble with services it’s running, etc. Better yet though, is that the developer released Prowl API, so that any internet connected service can send messages to your iPhone if it has your API key. PHP scripts, Linux servers, whatever. Fantastic possibilities.

So I decided to write a WordPress plugin that interfaces with it. Why? I could see someone being interested in it. If not, it’s great practice. What’s better, is that I got it running in a day. Big thanks to WordPress’s developer docs.

It’s actually up and running on my blog now, I’m making this post to test out a couple of features. It’s incomplete, has little error checking, and the configuration is terribly ugly, but it’s a start. Hopefully everyone’ll see this up on the WordPress Extend site in a week or so.

If there’s an idea you have for the plugin, please let me know! So far it only does the following:

• Notification on new comments/trackbacks
• Notification on new posts/pages

Obviously this isn’t much, but it’s pretty neat to get the notifications right on your phone!

I’m giving a new CMS a try, this time Concrete5. The feature that really grabbed me (besides being written by Portland natives!) was the in-line editable website, so that a user can click exactly what they want to edit, and change that content right from there. Also, the same for adding new pages, and content direct from where they want to add it.

I think this solves a big usability problem with a lot of CMS systems, where a user is expected to understand the difference between a frontend and a backend. This isn’t a problem for myself—or other tech savvy users—but this division caused a lot of confusion for users in the past:

Them: I want to edit this page! Me: OK, click the “Login” link here, and now go to “Pages”, then edit this page… Them: Which one? I wanted to edit the “About” page. Me: Then go down the list, and select “Edit” under the “About” heading…

I think it gets far too confusing. For the average person, and inline edit makes so much more sense. Leave the back of the house to the persons configuring the app, not to the people using it.

I’ll see what I can come up with. I’m porting a static site that I worked on in the past over to it, to see how it goes. It’s got some unique things like different colors for different navigational paths that should be interesting to see if I can work into a concrete5 theme.

i’ve been doing some research into using wordpress as a backbone for a corporate website, and so far i’ve found a lot of “yeah!  do it!” style posts (here and here), but not a lot of explanations to go along with the success stories.  i’m more interested in the true pitfalls of the thing, or better yet one good story of absolute ruin (although, googling “wordpress ruined my life” got some entertaining results, yet worthless).

i’ve been evaluating wordpress for a while now, even used it to set up a site for a local coffee shop / bar (although work drew me away from it, but i’m back to working on it now).  i’m feeling pretty confident that it can be done, and done well.  the big things i need from this site:

1. consistent look and feel, even when being edited by multiple users
2. easy to use by people with different levels of experience, savvy
3. very little training necessary
4. robustness to user mistakes

i’d say wordpress wins on 1 through 3, but (possibly?) fails on 4.  i’m not sure the access controls are fine grained enough that i can set users loose on the site and expect them not to hose it.  it’s good when you work for a company that you can trust your users not to be malicious (i do, thankfully), but you can’t stop them from doing something wrong accidentally every now and again.

i need to research this further, for sure.  i set up a beta site tonight to try out different content management systems, and i’m going to run through a quick few just to make sure my familiarity with wordpress isn’t clouding my judgement.  ExpressionEngine is the first one i’m trying out, but i need to say i’m not very impressed so far (and it’s a tough sell when your budget is $0).

Anyone have experience?  I’d love to hear about it?