Building responsive websites with great typography is no simple feat. There’s so much going on. It’s easy to get confused and overwhelmed, and maybe even give up on it all!
These, in a nutshell, is what you need to know.
First, you need to know what typography practices apply to the web. The web is chocked full of opinions that every typography practice is important, but many people fail to explain why.
How can you be sure what’s really important? What typography principles can you ignore? How do you discern opinion from facts?
My friend, you need to know the why behind each typography practice. You need to know if they’re applicable (or if they’re viable to implement) on the web.
Second, if you implement everything, you’re sure to run into cases where practices conflict with each other (modular scale and vertical rhythm, I’m looking at you 😡).
How do you resolve these contradictions? Can you back up your claims if anyone challenges your theory?
Third, how do you translate these practices into sane, reusable code? Responsive design is pretty hard. Yeah?
So, unless you have serious design + frontend skills, you’ll probably find yourself confused, overwhelmed and helpless in the face of typography.
It’s hard. 😢
I was helpless and confused too…
Until I decided to drill into design to discover why typography practices work.
In my search, I found universal principles that apply not only to typography, but also to general design. After discovering these principles, I was able to apply them in both my design and code. As a result, both my design processes and code improved dramatically.
On the design side, I became more creative and confident. I knew my designs would be good enough since I have a firm grasp of the fundamentals. I can even walk into a meeting with designers and hold my ground when we talk about typography, something I didn’t think was possible before.
On the code side, my code became simpler and neater. I was able to cut through the bullshit and contradictory opinions since I found out how to translate essential principles from typography straight into code.
What if you’re equipped with the same principles I know now? How different would your approach to work be?
- What if you could be more creative, speed up your design process and know how to tell if your design is good enough?
- What if you can walk into a meeting room knowing you’ll be able to handle pixel pushing designers, and walk out without a ton of small adjustments?
- What if you could finally teach your developers to care about typography?
- What if you have a robust and flexible typography system that you can reuse over and over again for any project?
If any of these sound interesting, I’d like to introduce you to…
