Posted on
by Akaki Mikaia.
Tagged with Newsletter
TL;DR: 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.
Some of the bigger Origami news since our last update:
Mark your calendars! We have two engaging talks lined up for the upcoming month.
Introduction to Origami: Lee will be delivering an insightful session that provides a high-level overview of Origami. Whether you work in Product or Technology, this talk is for you! Discover why Origami exists and how it can benefit you in your work.
Origami Foundations: Join Ako as he explores the fundamentals of Origami components. This talk will delve into the usage, advantages, and practical implementation of key components such as o-normalise, o-fonts, o-spacing, o-colors, o-typography, and a glimpse into o-grid.
Note: This talk is engineer oriented but anyone who want to deepen their Origami knowledge is definitely welcome.
Last months Origami has been working with FT Professional to gather requirements and identify which Origami components require a new FT Professional theme, this quarter we managed to release more themes than we promised and we will release a few more before Q2 finishes.
Currently we support o-banner, o-forms, o-tooltip, o-typography and o-buttons component themes and variations.
We’re excited about Origami for Everyone as creating differentiated products targeting different audiences is a central theme of the FT’s product and growth strategy. Origami for Everyone will allow Origami to scale to support more brands, designer-developer collaboration, and multi-platform compatibility.
To achieve these vision, we’ll need to make some fundamental changes in the existing Origami implementation. We’ve already started recruiting a new designer to lead on the design side of Origami, and we’ve been conducting research into design tokens, which will form the backbone of the new implementation of Origami. Ben already did a demo for new design tokens system and we got some initial positive feedback from our potential users. You can read more about this on our blogpost Origami Team Trials Design Tokens and if you want to know more of a technical decisions made along the way check out Conventions for origami Design Tokens.
We encourage everyone to actively participate in this project, offering feedback and sharing proposals for the new Origami architecture. Together, we can shape a future where the Origami design system works seamlessly with every product we deliver.
We’ve been talking with other organisations to share knowledge about design systems. We had a meeting with the design system team from the Lego, Washington Post, and Compare The Market. Next month we have a meeting scheduled with Conde Nast and we are all excited to share our knowledge and learn from each other.
We had a few contributors who helped us to improve Origami components and we want to thank them for their contributions. Thanks to Juan Sanchez Alcala for contributing to o-topper, o-video and o-comments components.
Special thanks to Anna Bebb for deprecating the n-sliding-popup component – that prompted us to write some docs on how to do deprecate Origami components. Now we have a guide on how to deprecate Origami components
We had new contributors who helped us to improve Origami components. Thanks to Marlon Bucley for helping us to improve o-multi-select component and thanks to Ed Gargan for helping us to improve o-forms component.
And a final thankyou to Arjun Gadhia who contributed a new customisation feature to o-autocomplete to support the TagMe rewrite. This was a most excellent pull request which included problem context, screenshots, documentation, and demos – making it very easy for the team to review and approve.
A digest list of some other things that have happened in April and May:
o-multi-select functionality and now it can be initialised with a selected value. We also added a custom event OptionChange to enable users to track interactions to o-multi-select. We also published TSX templates.o-forms had a few minor releases in the last two months. We removed the “green” valid state from o-forms. Deprecated pseudo-radio-links. o-forms now also has TSX templates published and can be used by other TSX projects. We also released FT Professional themes for o-forms elements. Now we apply invalid input styles to inputs with custom validation, as well as those which use default browser validation.ft-concept-button sets aria-label on initialise.professional themes.page-inverse and base-inverse colour usecases.professional themes and now it supports setting themes imperatively.professional themes for body and links.suggestionTemplate override option. This function is used to override the default rendering of suggestion items in autocomplete, with a function that returns a custom HTML string for the given option. It is typically used when wanting to provide additional context or styling for each suggestion item.inverse-professional themes.