This issue features remote first working, deep spring cleaning, and an improved release workflow.
These are some of the bigger things we’ve done over the last month.
It’s hard to believe we were largely working from an office at the beginning of this month. A reminder that we’re here to help. Our level of support is the same, and we’re happy to help via a hangout or Slack. 😊
We’re also running our workshops as usual. This month we ran out first ever fully remote “An Introduction to Origami” workshop for our fellow colleagues in Sofia. Thanks to everyone who attended!
In response to these times, we’ve been doing more spring cleaning of the Origami estate than usual.
We’ve created an origami-labels Github action to synchronise issue labels across all our projects, which we can use to organise our project board.
Every project also now has our issue templates to help users request new features or report bugs.
All Origami projects now have Github Code Owners, so new issues are assigned and added to our project board.
Each Origami component has our eslint configuration directly in the repository, which improves code editor integration and allows us to fix code linting issues automatically.
We recently renamed our support slack channel and have found out remaining outdated references so you always know how to find us.
We updated the support status for a host of older components, with recommendations for modern alternatives.
Many stale issues which were never prioritised have been actioned. Such as using dummy data in o-header demos, and pointing users to the Navigation Service instead; tweaking the Origami Registry UI, for example to make sure the “copy to html” button does not obscure demo HTML and works consistently; and we fixed a few origami-build-tools issues which highlighted a performance bug (o-buttons, which has a lot of demos, builds around 7-8 times faster! 🎉) — watch this space, we have more origami-build-tools improvements to come.
New Component Release Workflow
We’ve introduced an optional new workflow for releasing Origami projects. If your team maintains an Origami component, we hope you love it as much as we do!
It’s now possible to add a release label to an open pull request which will automatically create a semver release when merged. The version number released is added as a comment on the merged pull request. Labels include release:minor, release:patch, and release:major.
The benefits of this approach are:
It makes new releases of previous major versions “just work”. Our former approach was time consuming and easy to make a mistake. Now we’re able to support users who haven’t been able to upgrade to the latest version of Origami components easier.
Releasing happens faster (we had some projects which had many minor changes which had not been released yet).
In the future we can add extra features/protections to versioning, such as enforcing a migration guide exists for a major release.
This months special thanks goes to you all! You’re all doing a great job. Treat yourselves kindly. We miss your faces. ❤️
A digest list of other things that have happened since our last update:
MAJOR: origami-build-tools, only build assets once when shared by multiple demos, swaps lib sass for dart sass, fix demo sass source maps, drop node v8 support.
MAJOR: o-teaser introduces a new typography style (great work Olga Averjanova and Mark Limb!)
MINOR: o-banner now allows for banner button customisation (thanks Ben Fletcher!).
MINOR: o-message adds support for custom message states, which was used to build our Corona virus newsletter signup messaging.
MINOR: o-colors our mandarin colour is now available to internal brand users.
MINOR: o-fonts, adds a new Financier font weight for redesigned teasers (thanks Olga Averjanova!) And introduces recommended fonts to make it easier to include fonts commonly used across ft.com products.
MINOR: o-typography, adds an option to error if a font variant (family/weight/style)
is used when a font face for that variant has not been included in
MINOR: o-comment-api, updated support status to “dead”. This project is no longer maintained and has been replaced by the new version of o-comments.
MINOR: o-linked-list, updated support status to “dead”. This component is no longer maintained, please speak to the team if you would like to use a component like o-link-list.
origami-registry-ui, we removed a US Heroku backend to save a little extra money. As a Fastly backed bronze service we realised a US backend was surplus. We also improved a number of UI elements as described previously, including ensuring the “copy to html” button does not obscure demo HTML and works consistently.