It all started when our project manager Tom forwarded me a link to a cool CSS utility he had come across called the Holmes Markup Detective.
It essentially acts a markup linter and uses CSS to highlight places
where your markup is invaild, non-standard or deprecated and also
includes CSS based messages to tell you specifically what the problems
are. Immediately I recognized two things: one, this was a great tool for
validating your markup with visual cues, and two, it could easily be
ported to SASS. The initial port from CSS to SASS syntax (or SCSS more
specifically) didn't take long, but as my understanding and awareness of
Compass extensions grew, I recognized that was the best way to share it
with everyone else. And finally, as of today, it is done.
We are excited to represent Context and Philadelphia at this year's Drupalcon in Denver, CO. While I am still in PA, managing our current projects, I've received quite a few updates from our development team in Denver.
Integration pieces in development can be a mixed bag. On one hand, they can be intellectually challenging to implement, which is a valuable opportunity for any developer looking to push their own envelope.
In my last blog post, I covered my general approach to debugging for IE, which I hope you have to put to use in crushing your website's IE layout bugs. But wait, there's more! Allow me to reveal some of the less widely known IE browser caveats so you can be prepared when you encounter them yourself.
There are three main components to our daily operations that I like focus on, especially during the early planning phase of a new web development project. I affectionately refer to these elements as my Project Management GTL...
We've all been there. You are just humming along, building the perfect website, when you have a sudden realization that seriously ruins your feng shui: you haven't debugged your layout and styles for IE. And as much as you might just want to say, forget it, we all know IE still takes up a significant amount of the browser market and your client probably can't afford to miss out on that many users. But take heart! I am here to provide you some quick tips & tricks acquired over a long history of battle with IE that will help you avoid and conquer the many 'gotchas' of IE rendering.
The scrollExtend plugin is designed to automatically load new content at the bottom of the screen (by appending to a DOM element) when the user scrolls beyond the element, much like Facebook does with their status updates. The existing infinite scroll plugin was primarily designed to integrate with Wordpress, which didn’t really suit my purposes.
