![]() ![]() You'd probably want those styles in two different libraries, so people working on a responsive web project can just turn on that specific library. It's worth breaking them up if the designers are using different styles for different projects, that way they don't have to scan through styles they won't need.įor example, let's say you have a separate set of type styles for mobile native from text styles targeting responsive web. To make it easier to parse, you may want to consider sharing your text styles from separate libraries instead of one centralized library. The more text styles you add, the longer the style picker list will be. To make your styles easier to browse, you can prefix your style names with a forward slash (prefix/style-name) which will group your styles under subheads in the style picker. That said, you'll likely wind up creating more styles with this approach (since some styles may share the exact same properties) hidden behind a more descriptive name to help communicate their intended use. The descriptive naming approach can help you communicate where these styles get used.
0 Comments
Leave a Reply. |