Origami Frontend Components & Services

Origami Newsletter, August 2020

Posted on by Lee Moody.
Tagged with Newsletter.

TL;DR: This issue takes a closer look at some of our regular polyfill and documentation work.

Top Things

Welcome to our (slightly delayed) August newsletter, here are some updates from the last month.

Deleting Documentation

Last issue we introduced a new tutorial: Create A New Origami Component. This issue we’re happy to report we deleted some of that work!

We wrote the tutorial to encourage more contributions from outside the core Origami team. However a secondary benefit of thoroughly documenting how to create a new component is that we can identify opportunities to simplify our process, for example by moving to new standards, and delete sections of the tutorial as we go.

This month wasn’t just about deleting documentation though, based on feedback we linked to general component documentation from each component readme. The aim is to help people less familiar with Origami components get started. Thanks to Nick Colley in particular for opening that issue and to everyone who gives the team feedback.


We’ve also supported a number of polyfill updates this month. These allow us to use new technologies to build Financial Times products whilst still supporting our customers who may be using older web browsers or devices. For example the fetch polyfill is now standards compliant and we can now consistently sort arrays of data.

As our polyfills are open source they are used by many companies outside the Financial Times. For example (name drops incoming) skyscanner, sainsburys, aviva, eurostar, weather.com, guardian… there’s a lot. Our service polyfill.io received 818.8 million requests in the last 24 hours. This means part of maintaining our polyfills is responding to bug reports and external code contributions. Credit to the people who contribute to our polyfills by opening issues or with code contributions, inside and outside the Financial Times 😊

Special Thanks

You may know from our last issue that we have taken on stewardship and maintenance of o-tracking this quarter. That work is in progress, but we have another related special thanks.

Special thanks to Rob Squires and the Customer Products Platform team for helping answer our questions about cookie sizes on ft.com — without their help we would not have known about o-tracking’s large cookies for some customers. The new version of o-tracking will mitigate that issue and improve the performance of every ft.com request (images, css, fonts, js, etc) — hopefully more on that next issue!

Thanks again for the help, Rob and the Customer Products Platform team.

Broader Update

A digest of other things that have happened since our last update: