Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Okey! i recently came up with learning sass/less and it was quit interesting and i totally love to implement them. Now real question is how can i implement in preexisting project that is done in css. I know css is pretty backward compatible. but i don’t want to force all the project-member to use less.
If anyone update the css file, will it be ported to less file automatically i don’t know for sure!!
will there be any issue or problem to implement less on existing project??
To get the full benefits of Sass/less you’d want to refactor the existing style sheet(s) to take advantage of @mixin and @include (and @extend in Sass) and unless everyone on the team was onboard, or you’re committed to integrating their commits, I wouldn’t bother. Writing styles in meta-languages like Sass/Less changes the way you think about styling — it really is a different mindset. That said, I really don’t think it’s too much to ask that other team members adopt a more modern approach and I’ve had good luck with that on projects. The key I think is doing the infrastructure work and initial hand-holding to make it easy for them. Write some useful mixins that save them time. Try to anticipate their needs. I find I have to still do some refactoring, but as time goes by it becomes less (no pun intended) of a chore.