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
    5 Ways that CSS and JavaScript Interact That You May Not Know About

    CSS and JavaScript:  the lines seemingly get blurred by each browser release.  They have always done a very different job but in the end they are both front-end technologies so they need do need to work closely.  We have our .js files and our .css, but...

  • By
    Conquering Impostor Syndrome

    Two years ago I documented my struggles with Imposter Syndrome and the response was immense.  I received messages of support and commiseration from new web developers, veteran engineers, and even persons of all experience levels in other professions.  I've even caught myself reading the post...

Incredible Demos

  • By
    Image Manipulation with PHP and the GD Library

    Yeah, I'm a Photoshop wizard. I rock the selection tool. I crop like a farmer. I dominate the bucket tool. Hell, I even went as far as wielding the wizard wand selection tool once. ...OK I'm rubbish when it comes to Photoshop.

  • By
    Flexbox Equal Height Columns

    Flexbox was supposed to be the pot of gold at the long, long rainbow of insufficient CSS layout techniques.  And the only disappointment I've experienced with flexbox is that browser vendors took so long to implement it.  I can't also claim to have pushed flexbox's limits, but...

Discussion

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