A blog for announcements relating to the Origami team, components, and services. Subscribe to our feed for updates.
Hello new Origami; Goodbye Registry; Goodbye Sass.
Sass build times got you down? Enable Sass monitoring in your project and let us know.
Origami releases experimental O3 Button, updates on improvements to documentation and bootcamps.
Origami For Everyone will support the FT to create differentiated products, targeting different audiences, by scaling Origami to support more brands and platforms.
Racing bar charts that tell a story of Origami component development over time
Origami For Everyone means major technical changes for Origami. Does this mean we should move away from Sass?
Origami is preparing two talks for June. We released FT Professional themes for a bunch of components. We started working on Origami For Everyone(O3) and we started talking to other organisations to share knowledge about design systems.
Featuring FT Professional updates; front-end technology tooling maps; TSX templates and Storybook demos; and the bit where we failed to deliver around 9k image requests each day due to a confusing and unprompted error, affecting pretty much every FT Group product.
Origami updates on its new components and work exploring options for a Multi-brand design system
Origami has more team members; Storybook templates; More accessibility improvements; New CLI tool to create new components.
We've released new focus styles to improve the accessibility of FT Group products which use Origami.
A new Origami component ft-concept-button (:blobaww:); more accessibility fixes (:blob-hype:); an update on the Bower and Origami Build Service v2 migration (:blobhelp:).
A belated happy new year to you! The Origami team are off to a flying start. This feature includes many accessibility improvements; app team collaboration; Storybook Stories and JSX templates for components; and ongoing bower to npm migration support.
Origami image sets have moved and improved; the "master" brand is now the "core" brand; we're creating Storybook demos for Origami components.
We made a monorepo, and gained a delivery manager
New introduction to Origami sessions and special thanks.
We have released new versions of Origami components which bring full NPM support and drops support for Bower. This post explains the changes and how to migrate products to the new version.
Origami via Bower is deprecated, please migrate to the npm versions. A new autocomplete component has been built and is ready for use.
The Origami specification is no more
Updated Origami workshops. Work has begun to migrate Origami to npm. Reminder, we deprecate FT's Bower Registry in July. 2021 and plan to decomission in July 2022.
This issue is a big one. It covers our progress toward the recently announced npm migration; a new Origami Image Service placeholder image feature; a new Origami Build Service feature to help teams keep components up to date; and a whole bunch more.
We are migrating Origami Components from Bower onto the npmjs registry, this will be done by the end of Q2. Once the Origami Components are on npm, the versions on Bower will go into a deprecated state where they have no new features added. Products/Projects which want to get new Origami designs and features will need to migrate to npm.
Origami's new mission
This issue features Engine Room, Origami v2, and on-site messaging bugs.
This issue features new introduction to Origami sessions, an o-tracking major, and a proposal to drop Bower support.
This issue features image service cost saving and promoted content teasers.
This issue takes a closer look at some of our regular polyfill and documentation work.
This issue features a tutorial to create a new Origami component, automated "readme" documentation review, and new "indicator" labels.
This issue features accessibility fixes for users and improvements for developers.
This issue features a big Fastly cost saving, new font formats, and a major release of Origami Build Tools.
This issue features the Origami Component Survey, Automating Visual Testing of Origami Components and moving from CircleCI to GitHub Actions
Some charts outlining the results of our recent survey titled "Origami Survey: Building Components"
This issue features remote first working, deep spring cleaning, and an improved release workflow.
A new component, a project board and a post-mortem.
Users of Google Chrome may recently have seen a broken layout for many of our internal tools and products which use the o-layout component. Users of Firefox, Safari, and other browsers were not affected. In this post we'll discuss what changed in Chrome 80.
This issue features some changes to our Slack channels, a replacement for the Origami Open Meeting, an update on the Major Cascade, and a number of polyfill.io improvements including a new nodeJS library.
We are working on a major release of low level components like o-typography. In this post we'll discuss what improvements are being made and how they further our aims to help bring design consistency and reduce the time teams spend repeating work.
This issue covers an upcoming major new release of our components including o-typography, o-colors, and o-buttons; plus we discuss our new Continuous Integration tools.
This issue talks about the summit, bundle sizes and how we saved $2000
This issue announces a new team member, covers improvements to our operational documentation, and some projects that we built in our 10% time.
This issue features a new and improved version of o-forms, a new component o-spacing, and fancy new features to our colour contrast checker.
This issue features improvements to the image service, a new table filtering feature, and two new browser polyfills.
This issue features the new Origami website, a quantitative change in the Polyfill Service's capacity and a clarification on a problem we introduced—and promptly recitified—regarding our components
We re-launched the Origami website and Origami component registry.
This issue features Origami on npm, a new major release of o-layout, and a new major release of o-header-services.
This issue features a new component named o-stepped-progress, a new beta for o-header-services, and the release of the Polyfill Service v3.