The Quick & Dirty:

  • 9+ years in the biz, 10 messing around
  • All the latest in HTML, CSS, JS & PHP (Sorry, no .net or Ruby skills yet)
  • Cross-browser compatible code from Photoshop or Illustrator files.. or napkins!
  • Custom Specialities in Wordpress theming & plugins, Twitter & jQuery
  • Subversion, server-log analysis, and blocking hack-attempts (of late).
  • Data/Project Geek. I ♥ timelines.

I’ve compiled some handy PHP functions I’ve had to whip up. More extensive code-samples are also available.


Wordpress-from-static HTML


Back in the biz, oh yeah, nothing changed..

There’s always been a line-of-division between those who make pretty pictures, and those who have to make those pictures do something. Interaction designers have come to fill the void, but if there are none, there remains a 1999-level of disconnect. You remember last century, right? The one that gave us OfficeSpace, Matrix & Fight Club? Yeah, I feel like I re-live all those movies when I’m doing my job. It’s painful at times.

But instead of rant about the failures, let’s go over a few suggestions to make this designer/developer thing go smoother.

Take slideshows; the demon. There are a million slideshow-packages out there, and none of them do it all. Designers, in their everyday-use of the internet saw something once, and happened to remember “oh that was cool” and then implement it in visual form. Do they hunt down the package that they were thinking? No. This is not a failure to communicate only, this is a failure of research. R&D days don’t happen as often as they should; clearing-house reviews of packages don’t happen either. There are an insufficient number of feature tables-with-checkboxes; there are an abundance of “feature lists” and “10 best” lists. “10 bests” don’t run a compare/contrast; they fail to help me choose which package or platform to implement.

So off I go, rummaging through all these 10-best lists, trying to find the one that has the effect, the data-model, the visual-model that I need; nevermind IE6 compatibility.

Moving right along, this failure to research is also found in blog-design. WordPress has a specific 2-page format: one “landing page” of the top 5 or 10 posts, and one “sign-post” view, where you can comment. To deviate from this is to waste time. And add frustration. There is never a good reason to accidentally depart from core-services/functionality. We can do it, we can do anything, but if it’s not in the time-or-money-budget, then it should not be done.

I’ve just mentioned briefly 2 areas of recent failure, and the solution is the same: research. That said, I should like to create a set of “blueprints” to help print-designers move into web-fluency. There are plenty of websites out there that try, few who provide anything beyond “Works for Me.” Sadly, I am afraid this might mean that I have to dumb-down/re-write package documentation.

Until then, here’s a “what I use” short-list. This will be expanded upon..

Blog Samples:


Comments & Trackbacks separated:

Paging+Drop-down Menu:


IE6 & Cufon-compatible Fader:

IE6& Cufon-compatible Sliders:



Let me know if you find a good one! cForms is too fussy, Contact Forms 7 is too feature-less..


DropShadow in IE6,7,8 & FF2:

CSS3 Gradients:


Share and Enjoy

  • Facebook
  • Twitter
  • Delicious
  • LinkedIn
  • StumbleUpon
  • Add to favorites
  • Email
  • RSS
Posted in coding, design, development, Information Design, interaction design, life-of-a-geek, Project Management Tagged , Comments Off

Comments are closed.