Sources in web development. Leave or not?

A

Alexander Varakosov2015-09-25 08:25:25

Sass

Alexander Varakosov, 2015-09-25 08:25:25

Sources for building CSS styles. Do you deploy them to the production server, along with the layout, or not? Does this affect anything other than code maintainability?

Reply

Answer the question

In order to leave comments, you need to log in

4 answer(s)

S

Sergey delphinpro, 2015-09-25
@thelongrunsmoke

Yes, in general, they have nothing to do on the server. It is enough that they are in the repository.
The truth is that the situation when you take on revision, open the styles, and see that they are laid out using the preprocessor, infuriates. You ask the customer for the source code, and he says that when they did it, only css was transferred to him, or he doesn’t know at all. Moral: the customer needs to give all the sources, and explain that they will be needed by the future developer for improvements.

A

Alexey, 2015-09-25
@alexeyfedotof

Give only to a bona fide customer

O

OnYourLips, 2015-09-25
@OnYourLips

The source code belongs to the customer, so I give it away.
It is strange that someone can do otherwise.

V

Vladimir Io, 2015-09-25
@vawsan

Give without options. And it's better how to always give 2 versions - before processing in gulp and after. The first for improvements, the second for the release.