beCSS is a lightweight (27kb minified, 6kb compressed), hackable, responsive, flat-style-ready, and Flexbox-based style sheet, created directly with CSS without any preprocessors. Since beCSS is a single file, it does not include javascript.
Use the terminal to do the installation via NPM. Copy the file to your project, and then you simply have to load the style sheet from your html.
Features
beCSS provides a set of components and a Flat UI Color Scheme as starting point, and it is structure taking efficiency and simplicity as a reference.
Installation
Recomended
npm install becss
Copy the file to your project, and then you simply have to load the style sheet from your html.
<link rel="stylesheet" href="/your-path/becss.css">
Load from CDN UNPKG
You can call beCSS directly from UNPKG using the code below.
<link rel="stylesheet" href="https://unpkg.com/becss@0.1.2/dist/becss.css">
If you want to always call the latest version you can use the following code:
<link rel="stylesheet" href="https://unpkg.com/becss@latest/dist/becss.css">
Load from CDN JSDELIVR
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/becss@0.1.1/dist/becss.css">
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/becss@latest/dist/becss.css">
There are more than 300 classes in beCSS. By general normal the classes follow a semantic sense and are divided into three parts: id, type, fuction. The id + Function make a family.
id : = All classes start with the prefix "be".
type : = It is the family identifier. A family is a group of classes that share one or more types of functions. Every family have: id + type.function : = Indicates the specific task performed by this class.
Why vanilla CSS instead of a preprocessor?
However, it's also important to consider that CSS preprocessors can offer advantages in terms of code maintainability and scalability. They allow the use of features like variables, mixins, and rule nesting, which facilitate code organization and reusability.
Ultimately, the choice between vanilla CSS and CSS preprocessors depends on personal preferences, the nature of the project, and specific requirements. Both approaches are valid and widely used in web development.