That's where I feel like it's actually pretty nice to not have CI tied to your source code. It's probably more expensive to use Travis/Circle but at least you don't have a single point of failure for deploys.
579 karma · joined July 12, 2009
Granted, it’s harder to do that on the Playstation but the alternative is just … not sharing it at all which probably is the case for most gamers.
It was just an effective way to get through substack/medium in my experience.
Adam Morse's updated color palette: https://clrs.cc/
This really cool color scale generator: https://hihayk.github.io/scale/#4/6/50/80/-51/67/20/14/1D9A6...
Twitter has a large user base who just use it because it has 500M daily active users.
To use your "rounded" thing as an example:
Design systems should have their own definitions of what a "rounded" thing is. The designs also probably have different types of border-radius based on if it's a container element, or a button, or a pill button, etc. So you define those as different types of "rounded". Small, medium, large. Round, rounder, roundest. They could be whatever you want. This way, your team doesn't have to remember that 10px = round, designers or PMs just say "round" and you use the "round" utility class.
Or if they don't like styling they can say "hmm what about 'rounder'?" and you use the rounder class.
That's what Tailwind aims to solve is to 1) define a common language across the team and 2) make that easily available for the FE dev to implement versus trying to cross-reference what "round" is.