Me: *Building my own CSS and JS framework for static websites and testing it as i go while building my work site*

Inner me: Stop remaking the wheel, use MDL!

Me: *Starts sweating furiously*

Why must JS and CSS be so bloody horrible to build with from scratch, should I just use MDL and extend it with some custom classes or keep powering forward?

Out of curiosity, how are you pre-processing?

Sometimes I feel that it's horrible as well, and I know a lot of people here on devRant will laugh at it, but the way I see CSS is like any other language. It's all about how you think about it.

Sometimes when it's driving me mad, I try to find a way to flip the "pain and agony" and make the problems / small tasks into something more interesting. I'm not too sure if that makes any sense lol.

@Rundle What do you mean by pre-processing?

@lxmcf Are you writing pure CSS or using SASS / LESS?

@Rundle Ah, just pure CSS and JS, like keeping things as vanilla as I can

@lxmcf Ahh okay. You could always pre-process it while creating the framework, then just include the vanilla CSS in your end product. Alot of projects do this, they just don't include the source SASS/LESS files in the end product.

I mean in the end, it's all CSS, doesn't really matter how you get to that point. I always find that using the mixins and variables to generate it makes it a little more interesting (in my opinion). Really cuts down on the dev time as well! Just keep it in mind as an option :D

It’s simple if you like it plain, these fancy stuff are the one that’s hard to work on

Accesibility over fancy website for me