+ 2

Do i need to export Sass when i am deploying a new web

25th Aug 2018, 6:29 PM
ezall
ezall - avatar
5 Respuestas
+ 1
Just make sure you do what is required by your contract (should be under licensing or IP). If the customer is entitled to the source files, give them the SASS file. It doesn't hurt to include the compile CSS file, just to be safe. If the customer isn't entitled to the source files (didn't pay for them), there's no reason to throw in extras. Before the contract in signed, I usually make a determination about what the customer might appreciate and charge accordingly. (Source code for developers, otherwise I retain the IP and grant the client a license to use the final product -- they don't get the files.)
25th Aug 2018, 8:11 PM
Janning⭐
Janning⭐ - avatar
+ 3
If I'm understanding your question correctly, best practice is to compile your SASS file to CSS (and minify it) so it can be read client-side unless there is some compelling reason to go through the trouble of rigging up something to build it on the fly and serve it dynamically from the back end (in which case, you might as well just use JavaScript or some templating language).
25th Aug 2018, 6:36 PM
Janning⭐
Janning⭐ - avatar
0
i did compile the sass file into a compressed css file . now i can export css html and js files to the server but do i need to export the sass file as well so next time another programmer would update it (if there s an update)or that s gonna just add numbers to the size of the file (if you are the programmer who s gonna update the site what would you prefer)
25th Aug 2018, 7:07 PM
ezall
ezall - avatar
0
thank you very much janning i still didn t do any job so i don t know how this exactly works 😊😊
25th Aug 2018, 8:24 PM
ezall
ezall - avatar
0
No problem. :)
25th Aug 2018, 11:45 PM
Janning⭐
Janning⭐ - avatar