Giter Club home page Giter Club logo

typographyhandbook's Introduction

Typography Handbook

A concise, referential guide on best web typographic practices.

View the web book here!

This repository contains the source code for Typography Handbook. It was built using a custom Gulp and Nunjucks powered static-site generator. This project was largely inspired by the works of Adam Schwartz, Zell Liew, and Tim Brown.

typographyhandbook's People

Contributors

acusti avatar aeewhite avatar corysimmons avatar henggana avatar ierhyna avatar kennethwangdotdev avatar lupinskij avatar ms-studio avatar pjbeardsley avatar tbredin avatar tenzer avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

typographyhandbook's Issues

Repetition in the "Font Loading" part

In the part "Font Loading" there is a repetition :

Flash of Unstyled Text (FOUT). A FOUT is an instance where where a web page uses default and fallback fonts before switching to the proper web font.

Colors in "table of contents" and "further readings" sections violate law of similarity

The Typography Handbook says the following:

The Gestalt Law of Similarity states that entities that look similar tend to be grouped together. For example, if all clickable texts are sky-blue, the audience will assume that all textual content that is sky-blue is clickable.
In typography, the law of similarity just means to keep your styles consistent on elements that serve the same function. Group of elements should also look similar to other groups that serve the same function, for example: the visual styles of one blog post should look similar to another blog post. On the other hand, elements with a different functions should not look similar to one another.

However, it violates this very law in each "further readings" section, which has an opposite color scheme to the rest of the page:

image

Same applies to the table of contents, which uses black and gray colors for anchor links (or, more accurately, #333 and #333 with 0.75 opacity):

image

Polling github API too often

I had this page open but minimised in my browser for several days while i waited for a good time to read it. During that time it was repeatedly using the github API and draining my rate-limit, which was badly affecting my use of other pages that populate the page with content using the github API. Finally, the helpful folks at github helped me identify this page as the culprit.

I suggest you only use an API call once when the page is opened.

Add white background to body

There are browser themes that don’t have a default white background for websites. For example Firefox on Ubuntu prefers showing a light grey for website bodies when the web designer didn’t define the background. This results in seeing white shadows behind all links in the Typography Handbook.

typo-handbook

To prevent this, explicitly define body {background-color: white;}.

Usage of `rem` for vertical rhythm

I've noticed the suggestion of the use of rem in the code for vertical rhythm, with SASS calculations based on font-size. I'm wondering whether usage of em for heading margins wouldn't be more useful and simple - effectively the same calculation would happen automatically. In this case the dynamic nature of em size is actually a feature - larger heading will get more space, etc.
So I suggest to revise the rem suggestion, or at least to provide some useful information about the em alternative in this context.
Obviously you know a lot about the subject, so I also wonder maybe there's a thing for me to learn here.
This article (which is linked in your page) provides examples for this use case:
https://zellwk.com/blog/rem-vs-em/

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.