DEV Community

Cover image for 5 reasons why I built a CSS framework (and what I've learned)

5 reasons why I built a CSS framework (and what I've learned)

Pasquale Vitiello on February 19, 2020

Bootstrap, Foundation, Bulma, Tailwind, PureCSS, Materialize, and so forth: the idea of building your own CSS framework might sound like pure madne...
Collapse
 
noahraskin profile image
Noah Raskin

I would love to learn (in a much more simplified version without sacrificing the structure) of how you built this with SCSS. I love what you did with Cruip and I can't ever find great tutorials of the architecture like you have with Cruip! Awesome man! Ever consider doing that?

Collapse
 
pacovitiello profile image
Pasquale Vitiello

Hey Noah, thank you for your feedback! That is something that I would definitely consider for a next article :)

Collapse
 
noahraskin profile image
Noah Raskin

That's awesome to hear! I know it's a lot of work, but if that were a course I would buy it without question πŸ˜‰

Collapse
 
bernardbaker profile image
Bernard Baker

Hi,

What benefits are there with a px unit system?

I took a look at cruip.com I like your template, real time saver. And I have a project which needs a marketing front end solution.

On that topic, I've been using CRA. What's the build system for the React templates?

Are they upgraded to React Router V6?

Are they functional components, which use hooks?

Collapse
 
pacovitiello profile image
Pasquale Vitiello

Hey Bernard,

There are no specific benefits, it's a choice we made during the prototyping stage.

We used create-react-app for our React templates. They include mostly class components. Switching to functional components is something that I was considering but, TBH, I don’t think to get into a so big refactoring process soon (we have been distributing 14 templates!).

No React Router v6 yet!

Cheers, P.

Collapse
 
bernardbaker profile image
Bernard Baker

Ok