w3.css: Compact but complete CSS framework


Almost all the latest generation front-end developers know the Bootstrap CSS framework, and many of them use it as a valid support […]

Almost all the latest generation front-end developers know the Bootstrap CSS framework , and many of these use it as a valid support in the realization of their projects. But a new CSS framework is ready to be squeezed into the codes of our applications.

This is w3.css , produced by the w3schools body . This CSS framework is gaining more and more respect among developers, because it has the main features that are in line with the most obvious desires of those who write front-end code.

The first quality of w3.css concerns its total independence . For example, unlike Bootstrap, which for many of its features requires the presence of external components, such as jQuery and Popper.js, and comes with a package including multiple files, including the precompiled CSS, w3.css is represented from a single file to include in our beloved HTML pages via download or CDN service offered by the same w3schools . You write the link tag, set the href attribute to the appropriate value, and the game is done.

<link  rel="stylesheet"  href="https://www.w3schools.com/w3css/4/w3.css">

The second quality concerns the ease of learning and use . Bootstrap (which in this article represents the most correct comparison point to which we refer) necessarily requires a learning process, which can be more or less long depending on the skills and personal talent of the developer, before being used correctly. The same thing also happens with other common CSS frameworks available on the square. w3.css instead, has a very low learning curve, so as to be usable effectively right from the start. Both the core and the advanced features follow a logic that is very fluid during production, and therefore particularly pleasant to use and reuse.

The third quality concerns the product between completeness , compactness and compatibility . w3.css is complete with every feature that an HTML / CSS developer may need, from the simplest and most obvious controls, to the most advanced features, such as dropdowns, tooltips, modal windows, accordion, shading and slideshow.

Despite being a complete product, it is at the same time very compact and above all very fast, essential characteristics in a virtual world that is becoming increasingly heavy and full of contents of all kinds. Finally, the essential feature for a quality CSS framework, which is not intrinsically guaranteed by all the products we find on the web, is the wide cross-browser and cross-device compatibility, deriving from standard CSS code.

No further control weighs on the shoulders of the user of w3.css: the code that is produced is serene compatible with all major browsers (Chrome, Firefox, Opera, Safari, Edge and the friendly Internet Explorer) and with all major devices (desktop, laptop, tablet, mobile).

Since all HTML and CSS development revolves around the layout structure, it follows that producing a layout using CSS framework must be smooth and pleasant. w3.css offers different solutions to fulfill this task, including the excellent 12-column grid system , which, thanks to the device size control classes, becomes very easy to use and produces results consistent with expectations. Producing a layout that complies with any development standard, even a rather complex one, that proves to be responsive and with a mobile-first oriented structure , is a rather simple task if we use w3.css.

With this review I do not intend to discredit the excellent Bootstrap in favor of w3.css. Both are excellent choices in the wide range of open-source CSS frameworks that the network offers us at present, a bit like what happens in the Javascript panorama (with jQuery, MooTools, Prototype, and so on) and PHP (with Zend Framework, Code Igniter , Symfony and so on), where everything is in the style of the developer choose the option with which he is more at ease

In my life as a developer I tried them both and I currently use them both. However, I personally find that the development with w3.css appears to be fluid and immediate, and being a total lover of minimalism and predisposition to ” write less, do more ” (on which jQuery has made history), I tend to prefer it compared to Bootstrap for developing layouts and HTML pages.

I did a little personal test: I realized the same project using the same logic of front-end and back-end development, but with different CSS frameworks. w3.css turned out to be the tool that allowed me to spend less time getting to the final result.

Good writing of standard CSS code to everyone!


Please enter your comment!
Please enter your name here