Posted on
by chee rabbits, lee moody.
Tagged with Newsletter
TL;DR: The Origami specification is no more
Some of the bigger Origami news from the last month:
The team spent most of the month revisiting the Origami Specification. The specification is a formal document detailing the rules of how an Origami project, such as a component, must be built. We were trying to separate the parts of it that were developer advice from the parts that were relied on by our tools and services. After reducing the specification from 35 pages to 3, we had one last meeting in which we ultimately decided to retire the specification entirely.
When other teams say Origami, they tend to mean either the FT’s design or our team.
When we say Origami we tend to mean our reference implementation of the brand guidelines.
Origami was originally conceived as a series of specifications for components and services. There was an expectation that people all over the company and at external agencies would be building new Origami components and services all the time. In that context, a shared contract made a lot of sense.
But that’s not how it ended up. Origami components are mostly built by our team, and we’re always in the loop when other teams build Origami components.
Teams don’t trust the specification, they trust us.
The specification wasn’t what kept our components working in all the environments they were used in: we did!
We’ve always been vigilant about not breaking things for people, and that will never change. Breaking changes will always happen in major versions.
Retiring the specification gives us the opportunity to create better, faster, more modern components and to make sure that Design are a leading part of the process.
We’ll be going into a lot more detail about our plans in a blog post at the end of Q2.
This issues special thanks goes to Nick Ramsbottom! Nick worked with us on a component update to support New Product Development work, and enthusiastically got involved in the development. Together we were able to avoid project-specific overrides for a more reliable, consistent user interface.
If your team are looking to customise an Origami component for a project, checkout our guide to component customisation or contact the team for support.
A digest of other things that have happened since our last update:
input[type="file"] 🎉, and fixes the low contrast of valid form fields for the whitelabel brand.HTMLInputElement.prototype.valueAsDate, fix a URLSearchParams bug, and more (polyfill-library releases).githubname to the change api payload if the action was triggered by a github user, this fixes the action when trigged at set intervals by a cron for example.o-grid.layoutChange events given custom layouts (breakpoints). Thanks for your help with that, Eray Baskin!updateRows method to account for removed or changed rows. Thanks Emma Lewis for your work investigating that one!percy Github label, which used to trigger tests, has been removed.