Google has recently released Noto, a font that was develop to cater for all languages. It comes in a serif and sans-serif variant and is split up by characters used in different regions, most likely to reduce file size of the individual fonts. It is also up on Google Fonts to use in your mockups1.

The screenshot below((From the very nice Fonts app for Mac.)) shows how the font compares with others with the glyphs relevant to me2 and readability for people with cognitive disabilities3:

Screenshot of some fontsIt is immediately clear that the glyphs in the “qbd” and “69” parts are very similar apart from the rotating or mirroring, which is unfortunate. I like the upper “I” as it is very distinct from the lower “l”. It is certainly an alternative to the free open fonts we love like Source Sans/Serif, Open Sans, Fira Sans.


  1. I recommend self-hosting your fonts on live sites. 

  2. Punctuation all the way… 

  3. The source for the string „agjJlLiIqbd69“ is actually took from this post about easy-to-read fonts for children, but I think it makes sense to have those glyphs as diverse as possible for other use cases like cognitive disabilities or signage as well. 

Everything’s shiny and new around here! And it’s not just a visual refresh, the technology here is all new. I’ve switched from my beloved Textpattern CMS to WordPress. I didn’t expect that to happen, but it allows me to create content for this English and the German website at yatil.de from the same backend. Also the Website is indiewebified thanks to the tremendous work of Matthias Pfefferle. He created the Sempress theme and various nifty WordPress plugins. With Textpattern I would have developed most functionality myself and I don’t think that I would have found the time to do it.

The transition was painlessful. For example I had to go through each and every post and remove excerpts that were created automatically. Also there were no featured images carried over from Textpattern, so I had to assign them manually as well. That has been quite a bit of work for articles reaching back to 2004. I tried to catch everything, but there may be some rough edges around here.

Main objective of the transition was to post stuff more efficiently, the wide-spread integration and tools available for WordPress really help there. Please keep the webmentions coming, so I can be sure everything works.

I’m going to continue to publish here on my own website, journal, blog, or whatever you want to call it. It’s still possible that I might lose everything but I’d rather take the responsibility for that, rather than placing my trust in ”the cloud” someone else’s server. I’m owning my own words.

Really good article on why we should host our content ourselves and why it is so hard to understand for younger people. This is a must-read!

In this fantastic video from the Webstock ’13 conference, Mike Monteiro shows that designers need to take responsibility for their actions. There are many things I touched on with my article Be Proud to be a Web Developer from almost a year ago, and it’s worth watching. From the description:

You are directly responsible for what you put into the world. Yet every day designers all over the world work on projects without giving any thought or consideration to the impact that work has on the world around them. This needs to change.