• Utilities feature goal
• Personas
• Themes and patterns
• Utilities help people build websites more easily
• Legible classes are easier to understand
• Users want the actual values (colors and sizes) mapped to their corresponding token/class
• Users want to know the limitations of the system
• Most users didn’t understand the meaning of the u- prefix and its meaningful difference between the usa prefix
• Users want straightforward, practical, concise docs, and get overwhelmed by long documentation and content
• It was unclear what spacing units (padding, margin) were mapped to, most thinking ems or rems
• Users expected padding to go up to 10 and were confused why it only went up to 9
• Most users didn’t understand what 1p5 meant
• Users expect a default set of colors included in the system
• Users tried values in between color numbers, like black-23
• Two users tried to use pink and expected it to be included as a default color
• Users were confused about the border color, thinking the 20 in border-right-black-20 was a size value
• Users found the title of the Scoping section title unclear
• Users like the constraints of the system
• Users expect all the utilities bundled together and included by default, less choice
• Several users mentioned wanting to know performance implications of the utilities
• Users could mostly use font utilities with combined font family and font size
• Several users mentioned preferring to work at the component level
• What things should default to
• The balance of additional behavior built in for common use cases vs. single-purpose control
• Next steps