Skip to content
Origami Design System

Origami Newsletter, November 2020

Posted on by Lee Moody.
Tagged with Newsletter

TL;DR:This issue features Engine Room, Origami v2, and on-site messaging bugs.

Top Things

Some of the bigger Origami news from the last month:

Engine Room

This month Origami team member Lee (oh hey, that’s me!) gave a talk “Origami: Past, Present, & Future” at Engine Room, the FT’s engineering-focused, internal conference.

The talk covers a little history including why Origami exists, how Origami has adapted to new needs over the last 7 years, and gives a little peek at what’s to come. There are plenty of new opportunities for us to share and build on each others good work. The talk touches on a few technical subjects but is suitable for anyone within product and technology. If you missed it a recording is available here.

More Engine Room recordings are available in Google drive. There are many excellent talks to explore for those who couldn’t make it.

Origami V2

Work continues on our proposal to drop Bower support in favour of NPM. By switching we will align with the broader tech ecosystem and help speed up development at the FT.

This month we’ve tested out the proposed approach and… it works 🎉 We have also created a draft Origami v2 specification with the changes required to drop Bower support.

This proposal affects all projects which depend on Origami components. If you have any questions, thoughts, or feedback we’d love to hear in the #origami-chat Slack channel or as a comment on the proposal.

We know this is one many of our engineers are excited about. Thanks to everyone who has given us feedback so far, it’s much appreciated. 👏

On-Site Messaging

Working with the design team we released a minor update to o-message this month, which fixes some visual bugs including improvements to spacing around message content. We’re careful not to release breaking changes within minor releases but unfortunately messaging on some projects broke as they were heavily customising o-message in an unsupported way, with CSS overrides.

In response we offered to help update how projects use o-message to fix the problem. In addition, Xuan and the #design-ops team are auditing our on-site messaging currently so we can update o-message and other Origami components to meet our current needs consistently, without the use of overrides.

Overriding component styles with CSS can be problematic for a few reasons. It introduces design inconsistency, code complexity, and fragility (overrides are liable to break without warning when components are updated, as happened in this case). Instead it’s better to:

  • Work with the design team to decide whether a component really needs a unique modification (see the #design-ops Slack channel).
  • Update the component to include the new style.
  • Add new Sass options so the component can be customised.
  • Or, if you’re after quite different features or a whole new look, build from scratch.

The Origami team are here to help you decide which option is right for your project and make component updates if needed. We’re also happy to help you review a projects use of components, to remove duplication and overrides — let us know how we can help in #origami-support 😊

Special Thanks

This month we’ve made more direct contributions to Customer Products projects than usual. Our special thanks goes to those who helped review and release our work quickly so we could move on to other tasks. That includes Nick Colley and Simon Plenderleith, thanks both! 🙏

Broader Update

A digest of other things that have happened this month:

  • Origami Proposals: This month there is a new proposal to rename the Origami team. There is also an update on the variable font proposal — since we can only commission a resized MetricWeb variable font the work required for the proposal is greater, but as a bonus we may be able to reduce the complexity and increase the reliability of our font loading strategy. Let us know what you think!
  • Origami Specification: we’ve updated the Origami specification to relax some rules. Components without Sass may support brands without including o-brand as a dependency; Sass lint rules may be customised with a Style Lint configuration .stylelintrc.js; we’ve also been working on the v2 draft specification as discussed previously.
  • MINOR: o-buttons adds refresh and cross icon buttons to the default set for Build Service Users; improves spacing between icon and button text; updates pagination buttons with an improved look and new recommendations for the number of pages to show (thanks to Marina Ilieva for the design work here!) If your project uses pagination we recommend reviewing it and adding to your backlog if there’s an opportunity to use the latest o-buttons version to make improvements.
  • MINOR: o-comments logs a warning if required constructor options are not given; improves the styles for the reported state (credit to Glynn Phillips).
  • MINOR: o-header makes the height of the sticky nav public with a Sass variable; improves the search close button’s readability (thanks Nick Colley!)
  • MINOR: o-icons adds a new scroll-to icon.
  • MINOR: o-labels updates live indicator label animation.
  • MINOR: o-layout adds a listing element for use with the landing layout, this is useful to list posts on a blog for example.
  • MINOR: o-message: as discussed above, corrects the padding/margin of messages; adds a feedback state for the notice o-message.
  • MINOR: o-share adds support for the internal brand.
  • MINOR: o-spacing adds $o-spacing-names variable.
  • MINOR: polyfill-library adds new features and improvements thanks to open source contributions. Adds a Intl.Locale polyfill (thanks longlho); adds TextEncoder and TextDecoder polyfills (thanks lpd-au); adds a DOMTokenList.prototype.forEach polyfill (thanks romainmenke); rewrites the Symbol.prototype.description polyfill to make it work with different Symbol implementations (thanks mhassan1); improves the error message for feature detection tests (thanks romainmenke).
  • PATCH: create-origami-component update getDataAttributes to only return namespaced data attributes.
  • PATCH: fticons remove the 0x0x1024x1024 viewport requirement from contributing guide, this is no longer required to support raster graphic scaling via the Image Service.
  • PATCH: o-cookie-message attempts to improve accessibility by implementing the dialogue role; deprecates the standard theme option (these styles are output by default).
  • PATCH: o-gallery updates the support status of o-gallery to “dead”, due to its age and low (or no) use. Please let us know if your project relies on o-gallery still. Note there is a proposal for a similar carousel component.
  • PATCH: o-grid updates the bookmarklet (used to overlay the grid on a website for testing) to use the latest version of o-grid.
  • PATCH: o-normalise fixes :focus-visible focus styles (previously broken in Chrome/Edge 68).
  • PATCH: o-teaser registers brand support, to remove the brand support message in the Origami Registry; removes the opinion background from featured “hero image” teasers for desktop-sized viewports.
  • PATCH: o-toggle specifies brand support to remove branding warning from the Origami Registry.
  • PATCH: o-visual-effects corrects custom mixin documentation (another thanks for the contribution, Nick Colley!)
  • PATCH: origami-build-tools pa11y runs automated accessibility checks against all brands; fixed an issue that prevented demo JS from initialising reliably.
  • PATCH: stylelint-config-origami-component, adds tests to confirm our linting expectations.