A customer requested a custom content scroller that would showcase a grid of products on a single page. Unlike a typical scroller, they wanted horizontal only scrolling and the addition of "prev" and "next" links to advance the scroller one product column at a time. The challenge came from a user interface constraint that I imposed myself: I wanted to add "snap points" to the scroller.

While importing some past projects to the new website, I ran across an excellent tool that I haven't used in a while, but that I still think can be quite useful when used properly. I'm talking about an interactive color picker that is loaded with some javascript to allow the user to manually control certain color areas on the page.

Sometimes I come across a bug (usually in internet explorer) that just makes me gasp at how horribly something can go wrong simply because the browser was poorly implemented. This week that honor once again goes to IE. Below, you will see a couple screen captures of the exact same browser content as rendered in Chrome (on the left) vs. IE (on the right).

This week I have been stressing about embedding videos in HTML 5 using a cross-browser compatible solution that conforms to the latest mark-up guidelines. After looking around at multiple resources, it became apparent that the current browser usage patterns require at least one fallback option in order to include all the different mobile devices, and older browsers still in use by a large segment of the population.

No matter how tech savvy you may be, there is often a language barrier when discussing internet technology. Sometimes it stems from a brand new technology that no one has really heard of. Other times it can be a simple issue of "How do you pronounce that word anyways?". Lets take "Wysiwyg" for example. I find myself using that word pretty often when trying to explain to a potential customer how they will be able to change/add content on their own without coding knowledge.