I might be wrong about the assumption that C1 is also targeting the hobby and small-time implementer segment like my self and if so, this discussion is irrelevant. But if so, it is NOT obviously for people trying to use C1, that they have to do these more or less manually steps to make the basic CSS work.
@burningIce: I'm not arguing that the server should compile LESS->CSS over and over again, that's your words.
I'm fine with the way it works. if the CSS is never than the LESS no compiling is done, but if I can't make the server do the compiling when needed, that is a problem.
The way you describe the workflow with automated deployment tasks is fine for a professional bureau, but again back to that huge segment of hobby users C1 might be missing out on.
And then back to topic please.
Does anyone know of any shared web-hosting capable of supporting the node.js usage of C1 or is it just manually LESS -> CSS way from now on?
@burningIce: I'm not arguing that the server should compile LESS->CSS over and over again, that's your words.
I'm fine with the way it works. if the CSS is never than the LESS no compiling is done, but if I can't make the server do the compiling when needed, that is a problem.
The way you describe the workflow with automated deployment tasks is fine for a professional bureau, but again back to that huge segment of hobby users C1 might be missing out on.
And then back to topic please.
Does anyone know of any shared web-hosting capable of supporting the node.js usage of C1 or is it just manually LESS -> CSS way from now on?