tree eb80c4b918e1bfa4afb71db4116ff3ebf20896fe
parent 6693617d2022af9b7212ff8ba56a3f201b972900
author Han Seoul-Oh <laughinghan@gmail.com> 1486516563 -0800
committer Han Seoul-Oh <laughinghan@gmail.com> 1486516563 -0800

Rename font/ => fonts/

First suggested by https://mathquill.slack.com/archives/mathquill/p1486494860000902

It's definitely the consensus:
KaTeX
  https://github.com/Khan/KaTeX/tree/f3df1ccbac4c61efd55bec423bc8509f8d173fb2/static/fonts
MathJax
  https://github.com/mathjax/MathJax/tree/6273842a9746731b9ecca0de18ec9fd50a36df99/fonts
FontAwesome
  https://github.com/FortAwesome/Font-Awesome/tree/04dad1e192b129ab09cddcd9b1aefb8b189c8d79/fonts
materialize
  https://github.com/Dogfalo/materialize/tree/189722c9cac812f5e9b3b05299298e8d4e90d7c5/fonts
a blogpost on React-Meteor
  https://medium.com/@abhaytalreja/custom-fonts-in-react-meteor-app-ebe2a7fc7a2b#.43mnzbxaj
clinical-meteor
  https://github.com/clinical-meteor/fonts

It's even the consensus for Rails and Django:
react_on_rails "recommended project structure"
  https://github.com/shakacode/react_on_rails/blob/9483bf8aaa2610a0ba5c5f04a551001f99589b0d/docs/additional-reading/recommended-project-structure.md#directory-structure
"Custom Web Fonts and the Rails Asset Pipeline": "The recommended way"
  https://gist.github.com/anotheruiguy/7379570#the-recommended-way
"Ultimate Django"
  https://ultimatedjango.com/learn-django/lessons/serving-static-files/
someone on stackoverflow "Best practice for Django project working
directory structure"
  http://stackoverflow.com/a/35244323/362030