In my previous post, I reviewed some of the characteristics of responsively-challenged sites. I ended with this mantra: To move forward, we have to discard the idea of web pages and instead create design systems. Tomorrow’s web will be designed and built from collections of content modules, each optimized to provide the best experience for each type of viewing device. Today I’ll outline a new responsive process that we’re using at Hanson to create a better end product with fewer wasted steps.
This year, the world wide web turns 25. It’s been a long, sometimes awkward journey to adulthood (a journey I recently summarized elsewhere). From simple beginnings (check out the first website ever published), the web has grown up to change the world. Recently we’ve seen the web transcend the computer and become ubiquitous. That ubiquity presents a problem for people who write, design, and build content.
I’m sometimes asked, “Dave, why do web developers hate Internet Explorer?” It’s true that IE is sometimes the bane of our existence, and always the butt of our jokes. But the history of Microsoft’s browser is a Darth Vader-esque tale of hope, betrayal, and redemption.