I'm a front-end developer with an interest in client-side development through the use of HTML, CSS & JavaScript. I'm an evangelist of HTML5, CSS3, jQuery, standardization & open-source. I don't design the sites you use, I make them work.
Well, I've finally finished my redesign. It took about a month and half of "here and there" work, but I think it paid off. I've tested it across Firefox and IE quite extensively so everything should pretty much be in order. I hope to review it in Safari over the next couple days.
Features
One of the features I've added is an AJAX search. I wanted to eliminate page reloads when a visitor wants to find something and also allow for an alternative way to navigate. For instance if you're searching for a blog post and don't find what you want through the results, all you have to do is type "blog" and voila! The blog page loads on the fly. This particular functionality works for all 4 primary pages (blog, lifestream, portfolio, contact) and I'll likely add to this feature overtime.
As you probably notice, there's currently a few discrepancies with my live site. This has been done on purpose. Why? Well, because as much as I love playing around with websites, Drupal, jQuery, etc., I tend to get a little lazy when it comes to my own site.
To keep myself on track, I decided to create a new theme on and put it on top of my live site instead of in a sandbox. For the most part, this is transparent since I haven't enabled the new theme. However, when it comes to changing the design of my fragmented content (known as "blocks" in Drupal), the content and code changes but doesn't have access to the new theme's CSS.
Well, I have finally come to realize that I need to setup a personal wiki. As I mentioned in some earlier blog posts, I wanted this site to be more than just information about me. I want it to be information FOR me; and for anyone else who may need some answers to various/numerous web questions.
As some of you have noticed, I recently posted a few code snippets to help with some common tasks. However, Drupal doesn't seem to want cooperate with displaying the snippets properly. Also, doing it this way makes it a bit to cumbersome to keep track of these snippets. Instead I've turned to the
It has begun. From the depths of the underground, it has seeped into my computer as I now wear the mark of the Linux Kool-Aid mustache. Flavor: Ubuntu. I must say, it's quite tasty.
Now if you are one that knows me personally, I over glorify every new piece of technology and only a few end up sticking around. From new browsers, to text editors, integrated development environments and even development platforms, I'm all over the board. But this time is different or at least it feels like it.
Well, the migration to Drupal 6 (D6) is complete. I've decided to leave corydorning.net v1.5 behind and start from scratch. As some of you may have noticed, the "New site coming in January 2008" announcement date passed without a new site being deployed. I developed a new site design and was ready to start slicing and dicing it, when I decided I wanted to give Drupal 6 a look.
Well, I've finally finished my redesign. It took about a month and half of "here and there" work, but I think it paid off. I've tested it across Firefox and IE quite extensively so everything should pretty much be in order. I hope to review it in Safari over the next couple days.
