1839523 - Standardize and define dimension (space and size) design tokens

Status: NEW

(Toolkit :: Themes, task)

Description

[Jules Simplicio [:jules]]

We want to start applying some reusable space decisions to existing widget work. Here's an example.

We started capturing some reusable sizing decisions in our first release. See tokens under "size".

Let's standardize how we treat dimensions (space and size) in our codebase and capture our reusable dimension units in tokens. Before we can do that, we need to discuss:

• Should we use relative units or pixels?
  • Look at existing use cases using rems and pxs, and determine why they use what they do and from there try to determine what's the best course. Ideally we pick a lane (either rem or px), but if it turns out we need access to both, we can determine how to handle that via token naming and documentation.
• Should we treat size (width and height) separately than space (margin and padding)?
  • If we treat them differently, should they share any aspect such as being aliases of some overarching 'dimension' token category?