Darren Cadwallader

In `scss/bitstyles/atoms/content/_settings.scss`, the value of the large padding is given as `l1`: ```scss 'l': var(design-token.get('content', 'padding', 'l1')), ``` But this value doesn’t exist — the correct value is just `l`...

Fixes #762 ## Changes - Structuring the button custom properties to make variants work better, and to be more usable in situations like joined-ui - turning off prettier in more...

Right now we apply the min-width & min-height only to the `button--square` variant, but we could just apply that to each button size variant (we never want button to be...

- When the new icon set is finalised, we should update the Icon component used here in our docs. The new icons should either be provided here, or imported from...

We have a few layout primitives that could be used together — let’s add some docs: - list which atoms are good for layout, and link to the docs for...

Right now themes provide a `text` and `background` color, and other components “attach” their colors to each theme as they need. This system doesn’t scale well now that we have...

The CSS Nano `mergeRules` option only merges adjacent CSS rules, so can be safely re-enabled in our config as it doesn’t break any source order (see https://cssnano.co/docs/optimisations/mergerules/)

Add some layout primitives

1

Utility classes can be used to create some complex layouts, but it’d be great to have some commonly-used layouts encapsulated in CSS classes. That would avoid having to recreate them...

Inputs

1

Update design for inputs. Zeplin: https://zpl.io/p1YYqjM Also: we have the organisms/joined-ui component, currently used only for buttons. Adapt inputs to use the same approach for their rounded corners. Zeplin: zpl://components?stid=63079b90d0bf4a646c46c227&coids=63628af4d50639b5e763fbf8

When using bitstyles in a project, it is common to update some colors or the sizing scale. If this is only changing the values of colors and sizes, but keeping...