W
W
Web Lizard2016-02-29 19:09:08
Sass
Web Lizard, 2016-02-29 19:09:08

How to deal with bad people who make edits to the compiled css nickname?

Let's say there is a project whose layout is written in sass. And so it turns out that freelancers (or someone else) make changes to the project. But how they do it: they make edits through devtools, they edit the file with minified css lying on the server - and it's like done, the job is done.
And then when changes are made already in sass, then all this "work" of theirs, of course, frays the fuck. And it turns out that they have to do double work - that is, sit and dig like an idiot in a minified css nickname and look for what they did there in order to then transfer it to sass. Awesome job, overall. This is provided that there is still a backup. And if it does not exist, then all the work will have to be done again without options.
Question: how to deal with it?

Answer the question

In order to leave comments, you need to log in

2 answer(s)
O
Oleg, 2016-02-29
@Lizard-108

It is not very clear why different people do the same work, if you have a team, then VCS git or others will help. The most clumsy option is to create user_style.css and make additions there, but leave the main file untouched.

D
DarkMatter, 2016-02-29
@darkmatter

No, this is a professional tool and it is only used by pros.
I'll tell you how we are. Our company has different websites with different designs + landing pages with different designs. Freelance layout designers do the layout and hand it over to us. There are sources there, but in our company, a marketer who owns html, css but not sass is engaged in bringing everything to mind, respectively, after a couple of his edits, all sass sources are thrown out because they have no meaning for us. For approximately the same reason at the corporate level it is forbidden to use sprites for example.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question