![]() ![]() John Gruber INTRODUCTION STEP INTO THE TELEVISION SECTION of any electronics store, and you’ll see how widely colors can vary from screen to screen. Thanks to Craig, it’s now a little easier to achieve. The goal has always been the same: to make what appears on screen look as good as it possibly can. Our computers are almost unimaginably more powerful than those from years past, but designers and programmers have never stopped pushing the limits of our hardware. Craig effortlessly guides us through the principles and practice of color management as I read, I kept thinking, Well, that’s actually pretty simple-a big realization given I’d treated the subject as a dark art for fifteen years. He tells us not just what to do, but why. Better yet, he shares that complex knowledge in a clear, immediate way. In this book, he takes a step back to truly understand how color management actually works. (There is always a next time.) Craig did something different. When I encounter a color mismatch, I deal with it like so (a tactic I suspect many of you take too): fiddle with various color settings in image editing software and source code until it works out, and hope to remember the magic recipe the next time the problem happens. It’s enough to drive one back to vintage Macs that only display black and white. Or they don’t match on any devices, and good luck identifying the cause. Or they do match on some devices, but not on others. Getting colors right? Here are a few scenarios: a graphic image and CSS background color should match exactly, but they don’t. Thousands of different displays are in use, and our work might appear on any or all of them. Now with digital designs, we have no control over the output platform. I’d go to the print shop, examine the first copies off the press, and if they looked good, I’d feel confident that the whole print run would look the same. Getting color right wasn’t easy, but it was completely under my control as a designer, because I could target the output. Copyright © 2016 Craig Hockenberry All rights reserved Publisher: Jeffrey Zeldman Designer: Jason Santa Maria Executive Director: Katel LeDû Managing Editor: Tina Lee Editor: Tina Lee Technical Editors: Marc Edwards, Gus Mueller Copyeditor: Caren Litherland Proofreader: Katel LeDû Compositor: Rob Weychert Ebook Producer: Ron Bilodeau ISBN: 978-1-93 A Book Apart New York, New York 10 9 8 7 6 5 4 3 2 1 TABLE OF CONTENTS 1 | Introduction 2 | Coping with Colors 15 | Photoshop 41 | Web Browsers 57 | Mobile Apps 74 | Desktop Apps Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 80 | Conclusion 81 | Acknowledgments 82 | Resources 85 | References 88 | Index FOREWORD EARLY IN MY CAREER, I worked as a graphic designer dealing mostly with print. Desktop Apps Conclusion Acknowledgments Resources References Index About A Book Apart About the Author Citation previewĤ MAKING SENSE OF COLOR MANAGEMENT CRAIG HOCKENBERRY FOREWORD BY JOHN GRUBER MORE FROM A BOOK APART BRIEFS Working the Command Line Remy Sharp Pricing Design Dan Mall Get Ready for CSS Grid Layout Rachel Andrew Visit for our full list of titles. By performing these optimizations, the total payload size went from 50.6 kB (not including CDN minified assets) to 30 kB for an overall reduction of 40 %.Table of contents : Cover Foreword Introduction Chapter 1. ![]() Additionally, I found a way to reduce image file size without quality loss by removing image metadata via ImageOptim. With a handful of lines, you can decrease the size of static assets. It blows my mind how much the tool reduces image size. This is safe, because ImageOptim preserves image quality. ![]() ImageOptim overwrites the files with their optimized versions. ![]() ImageOptim reduces file size by removing image metadata.īy default ImageOptim removes invisible metadata from images, such as EXIF camera information and color profile. A colleague suggested the tool ImageOptim. That makes sense because image compression degrades quality. Doesn’t appear that WhiteNoise compresses images. For example, main.css went from 5.4 kB to 2.1 kB. Before Optimization After making changes with WhiteNoise + GzipMiddleware With this PR, all CSS/JS is now compressed and minified via WhiteNoise, HTML minified via GzipMiddleware, and images via ImageOptim. Adding minification and compression dramatically boosts page speed. Caching static assets is only half the game. ![]()
0 Comments
Leave a Reply. |