A blog by the folks at Erskine Design
At Erskine it’s more than just accepted, but it’s encouraged to question the way things are done. If something isn’t working, figure out another way and test it out with the team. We’re always experimenting and our processes are constantly questioned. The way we’re working now is ten times better than it was six months ago, and the same thing will happen in another six months. It’s inevitable.
Here at Erskine we use all the usual suspects to keep the day in order: The 37signals Suite (mostly Basecamp and Campfire), Beanstalk, Harvest, Redmine, the list goes on. All of these are great for a team or client overviews, but in my opinion are not enough to personally stay truly organized.
Up until I read Ethan’s new book, Responsive Web Design, I wasn’t very excited about the concept at all. I liked the idea behind it, but the way people were talking about RWD made it seem like child’s play.
“While y’all are off resizing your browsers and tweeting about your oohs and aahs, I’ll be making real websites”, I’d chuckle to myself from the toilet seat. Laptop in hand.
Yesterday though, my mind was changed completely and this is something I’m genuinely excited about. It’s the first thing web-related thats really got me going since I “made” my first site in Dreamweaver. It’s why I slept 4 hours last night. I’ve completely jumped on board and I’m having a boat party, y’all.
This doesn’t mean all the projects we build should be responsive, but the foundation can be laid by developing our websites more logically, with flexible fonts and layout baked in.
I believe there’s still quite a way to go on the best way to implement RWD, and there’s hundreds of use-cases we probably haven’t even uncovered yet— but that’s what I’m most excited about.