Matt Mullenweg, creator of WordPress and all-around web guru, has declared today “Thank a Plugin Developer Day” in honor of the 4000th official WordPress plugin.
Cool. I’ve developed one humble WordPress plugin myself: the simple, no-configuration registration spam blocker RegisTrap. If you’re a WordPress site owner plagued with bogus user registrations, give it a try!
I usually avoid mixing business and Blather, but I want to make an exception in this case. As of today, the new website for Wheeler Kearns Architects has gone live. Wheeler Kearns is an award-winning Chicago-based architecture firm. I love their clean, geometric designs and the open, welcoming spaces they create. I could spend hours looking through the vast archive of photos, sketches, models and renderings of their projects featured on the site.
But I have a special interest in this website as well, because I developed it. The project consisted of a custom, CakePHP-based CMS with a WYSIWYG editor (TinyMCE), extensive tagging and image management tools, and a polished user interface with lots of cool interactivity — fading slideshows, custom scrollbars, sliding navigation menus, etc. — courtesy of jQuery.
Web designers need a lot of tools at their disposal. Mostly this comes in the form of commercial software. If you don’t own the full Adobe Creative Suite, you at least have Photoshop (or, if you’re a FOSS contrarian, GIMP). If you’re on a Mac, you probably have BBEdit (or its free sibling, TextWrangler) installed, and if you’re on Windows… well… I don’t know. Does anyone who takes themselves seriously as a designer use Windows? I’m sure we’ll hear from them in the comment section.
But what I’m talking about here is not the commercial software applications you have installed on your desktop. I’m talking about the free libraries you probably need these days to get a “Web 2.0” site up and running.
I’ve been finding myself lately starting each new project by cobbling together the same set of these libraries, so this morning I decided to save myself some time on my next project by putting together a template set with all of them in place. Once I’ve had time to review all of the requisite licenses, I may post the complete package in a zip file here, but for now, here are some pointers to get you started.
Where better to start than with this easy-to-use, infinitely extensible JavaScript library? I can’t imagine working without jQuery anymore. It makes just about everything JavaScript-related several orders of magnitude easier to work with. And then of course there are a handful of plug-ins I like to bring along for the ride: color, dimensions, em, hoverIntent, lightbox, mousewheel and jScrollPane. (Actually, several of those are required just for jScrollPane, a complex and tricky-to-implement plugin, but if you need custom scrollbars, it’s worth it.)
I especially want to call attention to Lightbox for jQuery, based on the original Lightbox for Scriptaculous (see below). It’s a great way to add some nice polish to your site. Whenever a user clicks on a thumbnail to see a larger version of an image, you no longer need to subject them to an ugly and confusing plain browser window with the image in the upper left corner, or trigger a new pop-up window to appear. Lightbox uses CSS and JavaScript to elegantly apply a translucent mask over the existing page and present the image in a centered layer hovering over the rest of the page, in the same browser window. Slick!
On the other side of the JavaScript library fence, we have Scriptaculous, built upon prototype.js. It’s not quite as slick or as powerful as jQuery, but it handles AJAX without additional plugins. Honestly, I haven’t tried much AJAX with jQuery, but since CakePHP‘s built-in AJAX helper relies on Scriptaculous, I’ll probably still have a place for it, for a while. The snag is that jQuery and Scriptaculous, with their default settings, don’t play nicely; they both want to use the $ variable for themselves. But jQuery’s noConflict() method makes it easy to get these two powerhouse libraries to get along.
This is my least favorite of the tools described here, for two reasons: 1) it’s essentially just a patch for Internet Explorer without adding any new functionality for general use, and 2) it reminds me that Internet Explorer exists.
That said, it’s indispensable. The issue here is simple: IE6 doesn’t support a lot of “modern” features that other browsers do, and that are becoming increasingly essential to how the Web works, but unfortunately, IE6 is still one of the two most-used browsers in the world (the other being IE7). Firefox is growing rapidly in popularity; Safari is ubiquitous among Mac users; and the Web is increasingly experienced via mobile devices, but for now, IE is still king of the hill, and a large percentage of IE users can’t, won’t, or don’t even realize they can upgrade beyond version 6.
IE6 can be taught new tricks, however, and that’s the purpose of IE7.js. It’s a JavaScript library that “teaches” IE6 to behave more like IE7, fixing some common and infuriating CSS bugs, adding support for alpha channel transparency in PNG images, and various other “magic” that pretty much all just takes place seamlessly, behind the scenes. Just call this library and let it do its stuff.
If you’re using Flash at all, it’s helpful to bring along SWFObject, another JavaScript library whose sole function is to relieve the attendant headaches of working with <object> and <embed> tags and the suckitude of Internet Explorer browser inconsistencies.
In the past, whenever web designers needed text to appear in custom fonts (that is, any fonts that are not already installed on the user’s computer), there was only one option: make an image out of it. Maintenance nightmare. Enter sIFR, a JavaScript-and-Flash-based solution. You’ll still need a copy of Adobe Flash (the full application, not the browser plug-in) to make it work, but the end result is your font encapsulated in a SWF file, and some very clean JavaScript that seamlessly swaps your custom font in place of regular, plain vanilla HTML, and degrades gracefully to a standard font if the user is lacking either JavaScript or the Flash plug-in. And it’s fully semantic and validating.
The only downside of sIFR is that finding the latest version is a bit of a mess. But here’s a good place to start.
And finally we come to TinyMCE. At last we have a decent solution to the dilemma of allowing users who probably don’t know HTML to enter styled content on your site. It’s not without problems, especially where pasting from Microsoft Word is involved, but TinyMCE is a great WYSIWYG solution, a word processor in a browser window.
…but it’s a good thing.
From kottke.org: The country’s new robots.txt file.
Well, it’s probably easy to read too much into this. But the short story of it is that President Obama’s new whitehouse.gov website is blocking a lot less content from search engine “spiders” than that of Ex-President Bush (oh, that has a sweet ring to it).
Now there are plenty of reasons for putting things into your robots.txt file, and most of them have nothing to do with trying to withhold information from the public.
It’s rather odd, though, the set of directories Bush’s site was blocking from the spiders. I find expectmore and help especially amusing. The others aren’t quite so funny. What exactly about omb (Office of Management and Budget) did they need to hide? And… uh… well… 911 kind of goes without saying.
Why block these pages from being indexed by search engines? Good question. And here, I think, is the answer: to make it harder for the average citizen to keep track of changes that have been made to those pages by accessing Google’s cached versions (or, perhaps even more damning, the indefinitely-archived snapshots on the Wayback Machine).
But, it’s a new day. President Obama has promised a much more open and transparent White House, and if the visible underbelly of its website is any indication, he intends to keep his promise.
Also of interest: Here’s a comparison of the old and new whitehouse.gov sites.
The tech world is abuzz this week over the news that, despite his open letter from last week stating that he was going to stay on the job, Steve Jobs has announced that he will be taking a six-month leave of absence from Apple.
For those of you who don’t know, Steve Jobs has been battling pancreatic cancer since 2004. He underwent a surgery called the Whipple procedure in which large portions of various intestinal organs are removed, and has appeared mostly healthy since then. However, throughout 2008 he was observed to be losing an alarming amount of weight, which as he described in last week’s letter, is not (directly) related to the cancer.
I’ve been reluctant to delve into this topic here, because I have a personal connection with pancreatic cancer. Someone close to me has been battling the disease since 2005, and in fact underwent the same surgical procedure as Jobs. It led to a remarkable recovery, allowing her to travel internationally in 2006 and 2007. She’s still with us, but it’s been a hard-fought battle against both the disease and the effects of chemotherapy. So, in short, I probably have a better idea than most observers of just what Jobs is up against.
His cancer may or may not have returned, and he may or may not return to Apple in June as he has promised. But regardless of his health, it’s true and obvious that eventually he’ll be leaving Apple, regardless of the reason. And despite his role as the company’s founder, prodigal son, and visionary leader for the past dozen years, Apple will go on without him. But a lot of people seem not to be able to imagine how.
Apple went on without him from 1985 to 1997. It struggled, yes, and was the butt of many jokes. But I became a loyal Apple user in the darkest of those dark days: 1993. I witnessed the foibles of Gil Amelio, and yet Apple managed to soldier on.
Then of course came the return of Jobs. The past decade since his return as CEO has seen the company vault from laughable also-ran in the computer business to an innovative leader, not just in computers but in portable music players and now smartphones (though that name does a disservice to the fact that the iPhone/iPod touch is really a brand new, pocket-sized computing platform that defies the currently available categories). Their computers are more popular than ever for home users, and they’re even making inroads into the business world.
And yet, Apple fans are still viewed as something of a cult. It’s a cult of personality, largely, focused squarely on Steven P. Jobs. So, what happens to the cult of Apple without His Eminence?
It’s true that Steve Jobs is a uniquely skilled CEO. He’s a visionary without peer, he’s a ruthless businessman, a shrewd leader, and a great showman. So who can fill that void?
Well, as it happens, Apple has some pretty impressive leadership in its other corner offices as well. I think the situation at Apple, and whether or not to be worried about Jobs leaving, is best expressed in pseudocode:
if (Cook + Schiller + Ive < Jobs) { panic; } else { do_not_panic; }
There are three people at Apple who really stand out from the crowd, besides Jobs himself. They are Tim Cook, the Chief Operating Officer, who was largely responsible for the outstanding success of the iTunes Store; Phil Schiller, the showman who more than adequately filled Jobs’ shoes at this year’s Macworld Expo keynote; and Jonathan Ive, the visionary designer who has been at the heart of just about every new product offering Apple has introduced since Jobs’ return and the world-changing original “gumdrop” iMac design.
In short… these are some brilliant, talented guys. What’s more, together the three of them are at least as responsible for the current state of Apple as is Jobs.
Apple is in good hands.