And We’re In Business!

By  on  

The blog has been successfully moved to the new domain and theme. Took longer than I wanted, but doesn't everything?

A few of the roadblocks I ran into include:

  • MooTools & Syntax Highlighter didn't cooperate as I hoped. The issue was with Syntax Highlighter, but I've iron out this issue.
  • Problems upgrading WordPress from 2.2 to 2.3. I've stayed with 2.2 for now.
  • WordPress' list-driven navigation. A lot of WordPress revolves around lists, which in most cases is good, but why use UL/OL/LI if you can simply use "display:block;" CSS?

In any event, the new blog is up and I'd love to hear your thoughts on the design and how I can improve the website!

Recent Features

  • By
    Responsive Images: The Ultimate Guide

    Chances are that any Web designers using our Ghostlab browser testing app, which allows seamless testing across all devices simultaneously, will have worked with responsive design in some shape or form. And as today's websites and devices become ever more varied, a plethora of responsive images...

  • By
    CSS vs. JS Animation: Which is Faster?

    How is it possible that JavaScript-based animation has secretly always been as fast — or faster — than CSS transitions? And, how is it possible that Adobe and Google consistently release media-rich mobile sites that rival the performance of native apps? This article serves as a point-by-point...

Incredible Demos

  • By
    Using jQuery and MooTools Together

    There's yet another reason to master more than one JavaScript library: you can use some of them together! Since MooTools is prototype-based and jQuery is not, jQuery and MooTools may be used together on the same page. The XHTML and JavaScript jQuery is namespaced so the...

  • By
    Image Data URIs with PHP

    If you troll page markup like me, you've no doubt seen the use of data URI's within image src attributes. Instead of providing a traditional address to the image, the image file data is base64-encoded and stuffed within the src attribute. Doing so saves...

Discussion

    Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!