Do your font-sizes look gigantic on the mobile? You’re not alone. It’s a common problem many people have when using Modular Scale for responsive websites.
In this article, I want to share with you how this problem arises and how to fix it so you no longer have font-size woes.
Ready? Let’s go.
Just a few days ago, I received a design critique from Aurobind (a font, newspaper and magazine designer) regarding my website. He specifically pointed out that the spaces between my paragraphs could be reduced to achieve a better effect.
I was dumbfounded. I didn’t believe him at first since I was already using Vertical Rhythm. If I were to reduce the amount of space between paragraphs, wouldn’t I be breaking the Vertical Rhythm?
Even though I don’t believe it, I decided to try it out since I respect his expertise and the feedback he’s willing to give. And boy, I’m utterly convinced.
You might have noticed that I redesigned my blog recently if you followed me for a while. In this redesign, I switched from Wordpress to a static generator that I’ve created.
I love static site generators. They make it easy for me to create websites without having to go through a CMS like Wordpress. Since my blog is on a static site generator, I managed to simplify my blogging workflow because I don’t need access to the Wordpress backend anymore.
The only major problem I had with static site is that that I’m unable to schedule my articles and publish them on a different date. I tried several methods, burned myself, and finally found a solution that I’m happy to share with you.
Last week, I wrote a tutorial to show you how to use the mixins and functions of Typi, a library I’ve created for responsive typography. There’s a lot more to Typi that I can cover in one article. So, this week, I’m going to show you some advanced tips that I use with Typi so you can use them as well.
Typi is a library I’ve created to help make responsive Typography easy. I first talked about Typi when I released the article on responsive typography in January 2016. Since then, I’ve added new functionalities to Typi to make it even better.
In this article, I’m going to tell you what Typi can do and how to use it.
Are you sick of procrastinating?
I am. I have procrastinated a lot in my life, and I don’t want to procrastinate a moment further. But, somehow, procrastination always seem to creep up on me when I least expect it.
Recently, I got stuck with a serious bout of procrastination that paralyzed me for two full days. I couldn’t get any work done. I felt incredibly stressed. This incident reminded me about how awful it was to feel useless and powerless.
Having gotten past this serious bout of procrastination, I want to take this opportunity to tell you what goes through my mind when I procrastinate. I want this to serve as a reminder to myself, and also to hopefully jolt you into action.
I think it was a few months ago where someone asked me if I had any pointers to help them transit from Bootstrap’s dom-littering
.col classes to either Susy or Neat. It struck me that I haven’t talked about this even though I’ve been using Susy grids for so long!
Anyway, this transition is a fairly big undertaking if you’re doing it for the first time. Allow me to walk you through a four-step process that I use in this article.
I recently came across an article titled “Web typography is broken. Here’s how we can fix it”. A mix of emotions rushed through me while I read through it. I realized that the biggest argument Tom was making in the article was that web typography is broken because type doesn’t sit perfectly on a baseline grid.
On one hand, I was happy to see people coming up with ideas to push code to their limits.
On the other hand, I’m unsettled. I asked myself: “Is there a need to make every line of text sit on the baseline”? I knew the importance of Vertical Rhythm and the baseline grid. I also knew that details matter when it comes to design. But is this one detail enough to break web typography?
As I browsed through the internet looking for answers, I found out that even great designers like Mark Boulton remarked that it would be cool if CSS gave us a pain free baseline grid.
This increased my urge to find out if web typography was completely broken. After all, if a great designer said the same thing, then sticking perfectly to the baseline grid should be important. Right?
Have you wondered if you should use
rem for media queries? I had the same question too, and I never figured it out, not till now.
When I first created the mappy-breakpoint library over a year ago, I used
rem units. Then after a conversation with Sam Richard, I quickly switched to
em instead because I found out there isn’t a difference between the two.
In addition to
rem, a popular unit of choice for media queries is the good old pixel. I wondered if it’s possible to use pixel queries nowadays since px-zooming problem that used to exist was now resolved by all browsers.
This week, I finally decided to get to the bottom of this matter.
I talked about using rem and em for responsive typography and for building modular components in two blog posts previously. In both posts, comments about viewport based units inevitably comes into the picture.
I resisted working with viewport units for a while, believing that using them would be a pain in the ass because of the calculations involved.
Last week, I finally overcame the resistance and took a stab at exploring viewport units and how to use them in responsive typography.