Origami Frontend Components & Services

Origami Newsletter, October 2021

Posted on by lee & chee.
Tagged with Newsletter.

TL;DR: Origami image sets have moved and improved; the “master” brand is now the “core” brand; we’re creating Storybook demos for Origami components.

Top things

Some of the bigger Origami news from the last month:

Image sets have moved home

Origami image sets have moved. You used to be able to find image sets maintained by the Origami team under the Origami registry. Now image sets are listed directly within Origami Image Service documentation. No more jumping between the Origami registry and the Origami Image Service URL Builder!

Behind the scenes we’ve moved the images from multiple separate git repositories and S3 buckets into the Origami Image Service repository itself, using Git Large File Storage (LFS). This is a more simple architecture that allows us to publish new images and logos more quickly. Finally, author headshots were moved from being owned by Origami to being Editorial owned a couple years ago. However, many projects were still using the Origami Image Service to request (stale) author headshots. So we have now updated the Origami Image Service to no longer return an old headshot but to instead fetch an up-to-date image from our Content API.

What’s the Origami Image Service? It’s a service used to optimise, resize, and transform images. It works with FT images from an Origami image set, our Content APIs, or any image url. The quickest way to get started is to experiment with the URL builder.

The “master” brand is now the “core” brand

Origami components currently support 3 brands:

To address offensive and objectionable technology terms we opened a proposal to rename the master brand, our brand team agreed we should rename the brand and decided with other stakeholders to rename the “master” brand to the “core” brand.

We’re in the process of rolling out the rename. The “master” brand will become the “core” brand. This change will be reflected across Origami components, services, and documentation.

How Does The Brand Rename Affect Your Project?

It doesn’t! For now Origami components and services will continue to recognise the “master” brand.

However, if your project is using the latest version of Origami components we suggest setting the “core” brand in your Sass.

-$o-brand: 'master';
+$o-brand: 'core';

And if your project uses v3 of the Origami Build Service, we recommend setting “core” instead of “master” as your brand query parameter.

-https://www.ft.com/__origami/service/build/v3/bundles/css?components=o-layout@^5.0.6&brand=master
+https://www.ft.com/__origami/service/build/v3/bundles/css?components=o-layout@^5.0.6&brand=core

We’re rolling out documentation changes this week. Keep a look out for that!

Storybook

We’re working on an Origami Storybook. We see it as an eventual replacement to our very custom Origami component registry. Why? Because we can maintain less code and take advantage of the substantial Storybook ecosystem. Let me tell you some of the reasons why that’s super exciting.

Our current component demos are static. Take o-buttons demos as an example. What you see is what you get. You can’t experiment by changing the type of button, the icon, or button text. However in the o-buttons story you can try updating a demo with your own content right in the browser under the “controls” tab.

We’ve made use of the Storybook plugin system to add a custom HTML tab, similar to the existing registry, where Origami users can copy HTML from when building web products. Unlike our existing component registry this HTML changes when you toggle demo controls. This should make it much easier to experiment with a component, find the feature/variants you’re looking for, then copy the HTML to implement it in your project.

Storybook could also help us implement new components and keep in sync with the design team. We added a “design” tab to see a component’s Figma design right alongside its actual working implementation.

In addition we’ve been hard at work bringing over our existing documentation alongside demos, such as component readme, migration guides, and changelog.

We’re also excited to make use of the existing plugin ecosystem. Check out the accessibility tab which will look for issues such as colour contrast.

Our next steps are to add more components and missing features such as Codedocs. We’ll also be looking for user feedback. We’d love to know what you think. 🙂

Special thanks

Special thanks this week goes to Mo Shawwa! Mo contributed to Origami to fix a low level accessibility issue in o-normalise that could prevent readers with Voice activation software from filling out forms. Thanks for that! 💛

Broader update

A digest of other things that have happened this month: