Reuniting these two worlds can be conflicting: how do you name design tokens semantically if they have to make sense everywhere but also respond to the inner logic of individual components which are independently developed? In this article, we'll explore the problem and how BEM-a well-known naming design pattern-can come to the rescue. They too can be used across different sections of an app, but their implementation is oriented locally: the styles and logic are written as if the component is an independent element. Components include branded date-pickers, buttons, modals, and other functional elements of an interface. The team employs them to reuse elements and functionality across the app. On the other hand, design systems emerged to facilitate easier development with premade components while ensuring that style remains consistent. Designers want every part of the app interface and all the elements to have the same look and feel, and design tokens were created to help them achieve that outcome. There are design tokens for fonts, colors, sizes, spaces, and even indivisible pieces of an interface. On one hand there are design tokens, which have been used successfully by countless teams over the years to ensure that elements across their UIs are consistent. In this article I want to talk about a common problem: context and naming around shared variables. However, they often encounter conflicts when mapping established style architecture patterns onto the new abstractions inherent in a design system. Design systems are growing in popularity as organizations realize how greatly they empower their various teams to create accessible on-brand web and mobile apps while avoiding duplicated work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |