I am knee-deep in my first home renovation. My latest project was to replace all of the trim—around the doors, floors, and windows—which, while labor intensive, sounded to me like a simple enough project. After ripping out the old stuff, I found that my seemingly well-installed floors were anything but. The floor was inches away from the wall, and none of our doorjambs were actually connected to anything. I thought I had one big job ahead of me, but it turned out I had three. Whoever did the work the first time took the easy route, leaving me with extra work.
This is for everyone who wants to achieve greatness, tries too hard, and ends up driving their efforts right into the ground.
In my life, I’ve had a few notable personal achievements which I believe merited a celebration—champagne, a ticker tape parade, wild applause—but went relatively (okay, completely) unnoticed. Two come to mind:
Never look back, Steve Jobs said, or maybe it was Bernie Madoff. But at this time of year, it is customary to look at where we’ve been, and take educated guesses about where we’re going.
As web designers, we are in a time of new patterns. But we are making sense of these patterns and naming them. I traveled the world this year. Everywhere I went I heard the same four or five ideas.
From Cardiff to Costa Mesa, in every business meeting and at every conference I attended, we all spoke of responsive websites, finding new design and approval processes, and the challenge of delivering great design and appropriate content to a continually expanding universe of devices.
There’s something that’s hard for some of us web designers to just flat out admit: we stubbornly hate to code. I’m a designer, dammit. I live and breathe Creative Suite. Give me Photoshop or give me death. My former coding knowledge included two things: what a div is, and how to stylize my MySpace page (circa 2004).
And without even realizing it, my attitude has changed, seemingly overnight.
Within the past month, I have learned to build responsive, HTML wireframes using Foundation and Compass. The initial setup was enough to make me want to run away and join the circus. With the added confusion at first, it seemed like everything broke if I merely looked at my code the wrong way. But, with patience, coaching, and helpful documentation, it soon clicked—and with only a few tears shed along the way.
Some agencies adhere to the mantra “you get the clients you deserve.” If that’s the case, clients also get the results they deserve—especially when they hire based on spec. This past year, I watched two projects implode after they landed with other agencies who provided spec work in the sales process. I’m not typically a sore loser, but if you hire a partner based off of spec work, you’re digging your own grave.
Deploying a website to a web server is hard. Not “It’ll take some extra time” hard or “We’ll need some help” hard. It’s “Get a whiteboard and plan out the thing A Beautiful Mind-style” hard. It’s easy to look at your code, look at your server, and just drag/drop files to production. It’s a lot more difficult to set up an automated system that will do that for you.
At Happy Cog, we work in a variety of technical situations, and our deployment strategies must be extensible enough to suit each and every need. We deploy to Windows servers and to *nix servers. In some situations, we deploy code as well as content. We deploy PHP websites on some servers and Ruby web workers on others.
Successful design systems stand on the shoulders of sound grids. Grids form the groundwork for a uniform yet flexible suite of templates. Their layouts hold containers that fit together like pieces of a puzzle. Last week, Happy Cog, in partnership with Mijingo, released the 7th video in The Happy Cog Way series: “The Basics of Grids.” In it, MJ discusses using a nice little web app called Modular Grid Pattern, a grid generator that can export into a variety of design programs.
As the web evolves, there will always be two ever-growing lists: one of all the pieces of content that will need to appear on any given site over time and another with all the ways we can access that content. Creating flexible, modular design systems makes both of these lists a little less daunting and a lot more manageable.
At Happy Cog, we pride ourselves on empowering clients to take ownership of their content, and we provide a framework and all the building blocks to help them do so. These building blocks range depending on a project’s needs. One could be a video carousel; another a contact form. But, the most fundamental building block that’s on every site and we have to get right every time is typography.
When we think of responsive design, we typically focus on newfangled mobile devices like smartphones and tablets. But, as front-end developers, we still need to account for older browsers that can’t handle the newest CSS3 techniques when rendering our sites. In the case of responsive design, that means our old friend Internet Explorer 8 (and below) needs some extra handholding when we build our sites with media queries. These browsers don’t support media queries, and since they are still in widespread enough use that we can’t ignore them (~10% of users are still using IE8), we have to come up with new techniques for gracefully degrading our sites.
When Dan Cederholm introduced us that spring afternoon at An Event Apart in 2010, I took one look at you and thought, “What a dreamboat.” I knew you were going to change my life. We took things pretty slow at first—I experimented with button and gradient generators while marveling at your features. “You mean, no more cutting gradient background images? And wait, I can just round those corners however I want?!” At the time, my exploration focused on replicating classic Photoshop effects. I had no idea that that was just a small part of what you could do. Since then, you’ve brought so much adventure into my life, creating effects that I could never dream up in Photoshop.