suit VS Bulma

As style sheets became the responsibility of larger and larger teams, CSS’ global scope and specificity were often at odds with team dynamics. Style collisions became increasingly common, where changes introduced by one developer would inadvertently affect styles elsewhere on the website. As the old joke goes: two CSS properties walk into a bar; a bar stool in a completely different bar falls over. As these issues and the number of people experiencing them multiplied, so too did new CSS methodologies, particularly those focused on style sheet architectures. Before long, we had SMACSS, SUIT CSS, BEM, ITCSS, and more. Third party supersets of CSS also appeared during this time, such as Sass and LESS, which gave style sheet authors access to scripting features like variables and loops.

CSS (Cascading Style Sheets) are rules to describe how your HTML elements look. Writing good CSS is hard. It usually takes many years of experience and frustration of shooting yourself in the foot before one is able to write maintainable and scalable CSS. CSS, having a global namespace, is fundamentally designed for web documents, and not really for web apps that favor a components architecture. Hence, experienced front end developers have designed methodologies to guide people on how to write organized CSS for complex projects, such as using SMACSS, BEM, SUIT CSS, etc.

This is actually super bad practice. I really dislike scoped css.

When I see devs using scoped css the class names always end up like `.box` or `.name`.

Having to think about classnames and writing Sass makes me much more aware of the structure of the components I'm styling. Frankly I think only JS oriented devs like scoped CSS and frontend who love html/css and the challenges of architecturing good CSS don't egt any benefit out of styled components (since you're using atomic css like Tailwind and/or BEM-style which always "scopes" classnames with the component name.

In general any solid guidelines makes CSS instantly 10x better and that's all most projects needs, and it's often what most projects lack.

SuitCSS works great with Vue in my experience, and can even be linted with postcss-bem-linter :

https://github.com/suitcss/suit/blob/master/doc/naming-conve...

SUITCSS

Tachyons developer, Adam Morse in this talk at DevShop London 2016, talks about motivation behind Tachyons. He discusses the problem of continuous over-riding your own written CSS code, writing tons of CSS code, struggle to keep all this info in your head and the need to refactor 200Kb CSS file. His answer to the problem is Tachyons. SUIT CSS (Style Tools for UI Components). was the initial inspiration that lead to creation of Tachyons. Unlike Bootstrap where you redefine a component multiple times, SUIT had a class which would not redefine itself or mutate later.

This component syntax is mainly taken from Suit CSS with minor modifications.

suitcss/suit - Style tools for UI components

Tailwind is great, but creating everything from scratch is annoying. A nice base of components which can be extended with tailwind would be great. There are a few tailwind frameworks like Flowbite, Daisy Ui, but I like Bulma, PicoCSS and Bootstrap.

I would talk about building the frontend, but it is just a single page React app I built quickly. It does use a CSS library called Bulma, which is similar to tailwind and worth checking out. I did spend a day implementing a login/signup page, but this was just for the learning experience, and not what I wanted in the final product.

After finding a few spare hours I decided to address the alerts and update some my dependencies. I spent several hours debugging my Gatsby site after doing some recommended npm package updates. My UI class library Bulma was not being loaded by my sass-loader module. (I later learned that they migrated to dart-sass so I guess the fix should have been a pretty easy). Nonetheless, this prompted me to rethink my entire static site generator stack and got me curious about some other options. Why have these unnecessarily complex dependency chains? At that point I was almost too hesitant to even touch my package.json file. That's just silly.

Oh wow, quite happy about this, for a while it seemed the project was abandoned, really glad Jeremy keeps working on this :) The new website (https://bulma.io/) also looks very slick. I could totally see that he'd be able to monetize this like Tailwind, it's a really well thought-out framework with a good compromise between responsiveness, utility classes and components.

So, our post.component.html component is the generic page where all posts will have their content loaded. Here, the classes are from the Bulma CSS framework, and the template looks like this:

This is a pretty basic HTML that contains a form with a couple of form fields and a submit button. To make styling a little easier, I opted to use Bulma. But that’s entirely optional, and does nothing to impact our app.

Since v1.9.0 release, the Gowebly CLI includes support for Bootstrap and Bulma CSS frameworks.

Bulma is a lightweight and modern CSS framework that simplifies the styling of your web projects. It offers a clean and intuitive set of classes to structure and design your HTML elements, providing a quick and easy way to create visually appealing layouts. Bulma is responsive and mobile-friendly, making it an excellent choice for developers who want a straightforward and flexible solution for their projects. Whether you're a beginner or an experienced coder, Bulma's simplicity and versatility make it a popular option for building stylish and responsive web interfaces without the need for extensive customization.