You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 24, 2024. It is now read-only.
Terra uses a crazy (to me) number of plugins for CSS. For javascript, it's basically just babel and react, but for CSS we have all of these:
This is incredibly overwhelming, and a big hurdle to newcomers. There was a teams conversation (this one) where someone asked for help understanding our CSS at Cerner, and I realized it wasn't well documented anywhere that I had seen. Turns out it is well documented, but it's in contributing instead of getting started.
Issue Type
New Feature
Enhancement
Bug
Other
Expected Behavior
There should be a link or we should move our CSS style guide to getting started
Current Behavior
CSS style guide is in contributing, meaning most people will never see it.
Issue Description
Terra uses a crazy (to me) number of plugins for CSS. For javascript, it's basically just babel and react, but for CSS we have all of these:
This is incredibly overwhelming, and a big hurdle to newcomers. There was a teams conversation (this one) where someone asked for help understanding our CSS at Cerner, and I realized it wasn't well documented anywhere that I had seen. Turns out it is well documented, but it's in contributing instead of getting started.
Issue Type
Expected Behavior
There should be a link or we should move our CSS style guide to getting started
Current Behavior
CSS style guide is in contributing, meaning most people will never see it.
Steps to Reproduce
Go to the docs page here: https://engineering.cerner.com/terra-ui/getting-started/terra-ui/webpack and see that there's no indication of how to use all these CSS plugins
Environment
The text was updated successfully, but these errors were encountered: