These days it seems as if all the awesome people in the industry design in the browser. But you know what? It's hard to get in the flow when you are coding. Designs turn out blocky and bland.
It feels like the only way to master HTML and CSS is to spend years bashing your head into your keyboard while wrestling with floats and clearing divs in obscure browsers.
It's hard to be creative in the browser because there is a huge wall of technical nonsense between the design in your head and the browser.
So you run right back into the open and waiting arms of your old friend, Photoshop.
Chris Coyier — Chris runs CSS-Tricks.com and founded Codepen.io. Learn how he got started with web development and what tools he uses.
Sacha Greif — As Sacha started developing his own products he taught himself web development. Knowing code is more efficient and gives him more control over the final outcome.
Nathan Barry — Knowing the limitations of the browser is crucial at the beginning of any web design project. The best tool for web design is a pen and paper.
Aaron Gustafson — A close look at the workflow of a his well-known web design consultancy. How do developers and designers work together?
Jen Myers — It's important to start with the basics. Frameworks are amazing productivity boosters but only to the extent you understand how they work.
Jarrod Drysdale — Learn why and how you should tightly integrate Photoshop into your coding workflow.
Nick Disabato — Find out why knowing how to code gives you a huge advantage when working with a frontend developer.
Trent Walton — Start coding as soon as possible. Keep your toolchain simple. And yes, responsive designs should make you cry a little.
The Complete Package is packed with everything you need to go from the very beginning to designing in the browser like a pro. You get every interview with the experts and every topic in the book is covered with a screencast. You even get a second book, Brian Franco's beautiful, Illustrated Guide to Front-End Development.
“Thank you for writing this book. You have no clue how much time you've saved me trying to figure this stuff out.” — Antonio Moton
Keep scrolling for more options. (Team license at the bottom)
Chris Coyier — Chris runs CSS-Tricks.com and founded Codepen.io. Learn how he got started with web development and what tools he uses.
Sacha Greif — As Sacha started developing his own products he taught himself web development. Knowing code is more efficient and gives him more control over the final outcome.
Jarrod Drysdale — Learn why and how you should tightly integrate Photoshop into your coding workflow.
Trent Walton — Start coding as soon as possible. Keep your toolchain simple. And yes, responsive designs should make you cry a little.
The screencasts in this package cover core concepts like Git, Flexbox, Chrome's developer tools and how to build your own grid system. The four expert interviews were selected to cover a wide variety of topics and areas of expertise.
“I can’t thank you enough, your book finally got me using git through the command line! How did I work without this before? no clue.” — Ivan Bruyako
Keep scrolling for more options
“You explain a lot of things that are for some reason, overlooked and assumed. That is what I love about the book. The topics are not over-explained, they are not complicated.” — Laurel Natale
Includes everything in the complete package and a license for up to 10 people. Drop it on a shared drive/dropbox/whatever and let your team at it.
More than 10 people? Email me: [email protected]
Photoshop is powerful tool, but it's just not built for web design. On the other hand CSS3 is awesome, but you still need a tool for creating images. So even if you're designing in the browser, Photoshop will still be part of your workflow.
This book is for web designers, not front-end developers. So you don't need to be an expert or even close. But I will assume you have a working knowledge of CSS and HTML. If you have no experience with CSS and HTML then this book is not for you.
Is a PSD cross-browser compatible? Of course not, but it doesn't matter because it's not the final product. In this book you'll be working on a design deliverable, not the final product. You'll create code that will work in a modern browser, and that's good enough. But yes, it's true, this won't work if your client can't download Chrome.
Howdy, I'm Sean Fioritto. I'm a front-end developer based in Chicago.
You can find me, @sfioritto, on Twitter and my blog is Planning for Aliens.
I've also written for Smashing Magazine and created a few, cool open source projects.
— Erik Hope, Engineer at Dropbox, Cofounder of Riot9
— Bill Maclean, Vice President of Architecture at Simplement