I stumbled across James Mellers’ responsive wireframes a while back, and have returned to it now that I’m working on a meaty responsive design project of my own.
I’ve bastardised his slick coding work to create the static diagram above, which I’ve printed out so the team (design, dev, and UX) can talk about the approach and if we think it’ll work for what we’re doing. Our project is a content-heavy site, so templating as much as possible will be key, and the simple alphabetical approach to conveying prioritisation will be great to both get the client on board and to allow our awesome developer to use his ridiculously good design instinct to use my wires as a starting point, but then fill in the blanks as long as priority is clear.




