Posted on
by Origami team.
Tagged with Newsletter
TL;DR: Origami via Bower is deprecated, please migrate to the npm versions. A new autocomplete component has been built and is ready for use.
Some of the bigger Origami news from the last month:
Our main objective this quarter was to have everything in Origami moved off of Bower and onto the NPM registry (see January’s announcement).
Moving Origami from Bower to NPM provides many benefits, such as:
We have completed this piece of work and now are ready for teams to migrate their products to the new implementation of Origami. Components on Bower are now deprecated and we recommend all products migrate to the new implementation to keep up-to-date with future releases to Origami.
The FT Bower Registry has now also been placed into a maintenance only mode for 12 months, until 1st July 2022, when we will look to decommission the service completely.
We have created a set of guides to cover the different ways products may choose to migrate.
Another one of our objectives this quarter was to build an autocomplete/type-ahead component within Origami. This was a component which has been requested by several different FT products. The Product Design team have done a great job on creating an autocomplete design which fits with the rest of the components within our products. We have completed development of the component, which we named o-autocomplete. It is the first component which exists on NPM and not on Bower and it has benefited greatly from this by being able to use the accessible-autocomplete package which already exist on NPM and was made by Gov UK. This greatly reduced the amount of code we would have had to write ourselves.
If your product is already using an autocomplete component or wanting to use one, we recommend looking at o-autocomplete and seeing if you can start using it instead as it is actively being worked on by the Origami and Product Design.
This version of the build service uses the now deprecated FT Bower Registry. We have built a new version, version 3, which does not use the FT Bower Registry. To help projects migrate to version 3, we have built a tool which will list out the specific steps for a project to do in order to successfully migrate over to the new version.
We are tracking the projects which will need to be migrated to the new version in the same spreadshet we are tracking the Bower migration.
This issues special thanks goes to Xuan Zhang! Xuan worked on the design and interactions for the new o-autocomplete component and was very helpful in explaining the designs and how they should look on different devices.
source_id property