And We’re In Business!
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!
![39 Shirts – Leaving Mozilla]()
In 2001 I had just graduated from a small town high school and headed off to a small town college. I found myself in the quaint computer lab where the substandard computers featured two browsers: Internet Explorer and Mozilla. It was this lab where I fell...
![CSS @supports]()
Feature detection via JavaScript is a client side best practice and for all the right reasons, but unfortunately that same functionality hasn't been available within CSS. What we end up doing is repeating the same properties multiple times with each browser prefix. Yuck. Another thing we...
![GitHub-Style Sliding Links]()
GitHub seems to change a lot but not really change at all, if that makes any sense; the updates come often but are always fairly small. I spotted one of the most recent updates on the pull request page. Links to long branch...
![MooTools 1.3 Browser Object]()
MooTools 1.3 was just released and one of the big additions is the Browser object. The Browser object is very helpful in that not only do you get information about browser type and browser versions, you can gain information about the user's OS, browser plugins, and...
