Cirrus VS uikit

💎 Cirrus 📝 Documentation

Do you like launching stuff? I like launching stuff! A few months ago, I released one of the largest updates to my CSS framework, Cirrus. Cirrus is a CSS framework designed for rapid prototyping and production use with a wide variety of ready-to-use components to plug into your app and utility classes to customize them. This makes building anything new with Cirrus a breeze with dead simple configuration and little overhead.

For this tutorial, let’s create a simple viewport mixin similar to the screen-above() mixin defined in Cirrus. The mixin below will apply any styles passed into it if it is larger than the specified breakpoints. Copy the contents below into a new file within /src/mixins.scss.

I previously thought Sass unit testing would never be a thing and why would it be a thing that developers would try to figure out. Today, I cannot think of developing Cirrus or any large projects with hundreds of styles without unit testing.

Update headline font sizes to have less of a gap from h1. 7d63a17

4. Cirrus.css

💎 Cirrus 📝 Documentation

Using it is incredibly simple. Go to a repository you are browsing, let's say https://github.com/Spiderpig86/Cirrus. Then, go to your address bar and change github.com to github1s.com and press enter. You should now see the repository loaded up in a VSCode-like window.

If you're interested, feel free to check out Cirrus! Documentation

UIKit (WIP): https://github.com/kyoto-framework/uikit

UIKit (in active development): https://github.com/yuriizinets/kyoto-uikit

Started development of UI Kit. High-level components library that tries to bring fully featured components, like navbar, sidebar, statistics, headings, forms and so on. We are trying to avoid low-level components like buttons/inputs/selects as far as we think that low-level things can be made without components at all. Library now in active development and not recommended for using. We are trying to find out main problems while implementing components as a separate package.