Oh, right.  We’re also experimenting with Twitter.  And Facebook.

Right now, you should be able to see an announcement for this post @emanagr.  If that works out, we’ll investigate using Tweets as an interface to eManagr like many of us are using e-mail right now.

I assume that you can also see us on Facebook.  This isn’t my field at all, so I’m curious what this does. Stand back:

Anyway, it turns out we were in the Dark Ages with our version, so much so that we’re wondering how nothing has blown up in our faces, but we’re now at 2.8.1, just in time for the 3.0 announcements, I guess.

Upshot:  If anything looks broken, scream.  I think everything’s back where it’s supposed to be, but may have missed some things.

In the “credit where credit is due” department, we’ve added WP Greet Box.  Presumably, most of you won’t see it, but if a major content provider directs you here, the blog acknowledges it.  I find that sort of interaction helpful and hopefully you will, too.  Also, the aforementioned Twitter interface is handled via Twitter Tools.  Unless it doesn’t do what we expect, in which case we’ll be replacing it very soon with something else.

First, the main system is programmed using Ruby on Rails. Ruby is nicely flexible and the Rails framework does a relatively nice job of hiding web-specific programming. The code is mostly custom, however, other than a few non-standard plugins such as Restful Authentication, WillPaginate (link is sometimes flaky), and auto_complete. The interface relies rather heavily on AJAX, by way of the Scriptaculous libraries.

Artwork, to the extent that we can call it that, happens in either Paint.NET or the GNU Image Manipulation Program, depending on the specific need. We still haven’t uploaded them at this writing, but the movies to be added to the system walkthrough are recorded using Wink; we discussed how to display them (or any Flash video) automatically at the correct size last week, which probably tipped off a few people that Ruby on Rails is involved.

One module not written in Ruby is the code that helps you invite your associates from social networking platforms and e-mail address books. This is handled with Open Inviter, with only slight modifications to match the site layout.

As most people will quickly identify, this blog runs on the WordPress engine, with the following plugins:

• Akismet filters out comment spam.
• The All-in-One SEO Pack is more important for cleaning up the interface than search engine results, but that aspect is also appreciated.
• Author Highlight makes it easier for a casual reader to find official responses to comments.
• Broken Link Checker decreases the likelihood that a link-heavy post like this will become useless to a future reader.
• Google XML Sitemaps help with the aforementioned search engine results, but also help to keep articles straight internally.
• I Love Social Bookmarking helps you, our readers, get the word out, should we happen to say anything useful.
• WordPress Mobile Edition is terrific for making this blog accessible on tiny devices. It’s a shame that the entire web can’t degrade this way automatically.
• WordPress Thread Comment lets you respond to someone’s comment directly, rather than trying to refer to the comment in absentia.
• WP-PageNavi definitely goes a long way to cleaning up the standard WordPress interface.
• Finally, WP Super Cache makes me feel like an idiot when I tweak a setting and it doesn’t show up, but the return in the form of speed makes it worthwhile; there’s nothing worse than a text-only page that loads slowly.

Finally, the community and support forum is the very nice Vanilla package. It’s not perfect, and we’re still (clearly) settling in, but it’s easy to use without sacrificing any significant features.

Oh, and for planning and managing development, we use some web-based system called eManagr. Perhaps you’ve heard of it.

Would anybody else running a software project like to talk about their setup? How is it working out for you?