By Tim Caynes on Feb 13, 2008
We just recently resolved an implementation issue that had been going back and forth between Greg, Andrew and me for a good few weeks. It wasn't a big thing, but sometimes the simplest things push the boundaries when I try to do it myself.
For a long time, we've had invitations to talk directly with sales advisors on sun.com, whether you want to chat, call, email or even have sun call you back directly. These invitations have been reasonably prominent in the right-hand navigation of specific pages. More recently, we've been able to embed these invitations by deploying inline rollovers, at the point where customers commit to a call-to-action, making the invitation much more relevant and immediate. You can see the current deployment on some of our promotions, like the Uniboard Upgrade Promotion (until April 1st, which happens to be my birthday, by the way). As you rollover the 'Start Saving Now' call-to-action, our rollover appears, with all the options you might need.
Nice as this is, its actually a pretty cumbersome implementation. When I say cumbersome, I mean, its elegant code (as all our web components are), but the way in which we had to deploy it in the short term left a bit to be desired. Our ever-patient publishing team reluctantly agreed to hard-code the components into specific pages, knowing that that was a huge backwards step, and a potential maintenance disaster - they know we'll change our mind about what's in the component and expect them to find and update it in all the places we asked them to deploy it but never actually kept a record of ourselves. What we all really wanted was a separate source file for the component itself, which could be referenced by a standard piece of code that would be provided to content owners to use as they require.
This, unfortunately, is where I, as usual, said "I can do that, don't worry".
Needless to say, despite my best efforts, I simply could not arrange 10 lines of code and a couple of hash references in the correct order, and ultimately I prostrate myself at the altar of the web design church for forgiveness. Happily, for me, they couldn't either (for about 10 seconds), but eventually resolved the issue with a flourish of staged content, and I took their code and stuck it into my development site. Of course, it didn't work when I tried it, but another couple of hours (and a few gin and tonics by now) later, everything was as we wanted it to be.
The trouble is, it took me so long that Neal probably doesn't even want the rollover any more, but, you know, its useful to 'keep your hand in' with this stuff (not for the developers and publishers who have to clean your mess up, naturally, before they point that out).
Listening Post: Outlaw: Nothing Else To Say