bitstyles
bitstyles copied to clipboard
bitcrowd
A complete design system, with base styles and components, built in Sass using CSS variables
`tools/shadow.generate()`, `tools/shadow.to-box-shadow()`, and `tools/shadow.to-drop-shadow()` could make use of design tokens passed in, and use them instead of hard-coding sizes and colors. For examples the default configuration produces shadow design tokens...
Once #693 is done, we could use those exported design tokens to make the docs better, something like we do for the color palette already. e.g. render blocks for each...
Joined buttons currently require utility classes to achieve the correct rounded corners and borders. Can we achieve that in a better way? Options could be a new button type, or...
Our directional utility classnames have have the order: `---` e.g. `.u-margin-m-left` This feels a little unintuitive, maybe as it doesn’t match the way CSS itself is written e.g., `margin-left: 1rem`,...
See https://webkit.org/blog/7929/designing-websites-for-iphone-x/ `atoms/content/` doesn’t currently account for any `safe-area-inset-*` values. So when fullscreen layouts are required to work on landscape, there are currently either borders at the sides, or the...
We have a lot of utility classes, perhaps they could be grouped into logical sub-sections? See comment here: https://github.com/bitcrowd/bitstyles/pull/647#discussion_r860860962 e.g. the `inset` and `position` classes could be grouped under `positioning`...
Using icons in a flex layout has superseded the `inline-block` alignment (that always had issues with vertical alignment anyway). Try out display block or display flex — any advantages or...