To build the .min.css files, I think the main (phase 1) Makefile would be the ideal place.
There might be better ways to distingiush between development and production environment, for example by adding a xslt parameter which is automatically set in the build script. I first need to understand which actually should be development environment, and which should be production environment. For example, will the automatic build of test.fsfe.org be production or development?
@reinhard I took another round with Max to integrate the valentine mode as well. We updated the name of the control file to config. The variable is now css-mode. Max suggested to simply sed the css-mode in the make file. Could you prepare that.
Max suggested to simply sed the css-mode in the make file
Sorry, I didn't see Reinhard's suggestion before, a parameter would be even cooler, but to be honest I don't have a strong preference here.
For example, will the automatic build of test.fsfe.org be production or development?
IMHO production or compiled as it is called now. The server can take care of the CSS generation, so I see no reason for increasing the loading time.
Yes, it's only for local development.
Great feature, thank you! Just a reminder that once this gets merged we should update this documentation.
changed title from WIP: Less live build to Less live build3 years ago
@reinhard if you're happy with it could you prepare the make file? lessc then has also to be available on the build system.
For all people who already use local build, it's important to run fsfe-preview --copy look/ build/ scripts/ to have everything prepared. From then on, all pages have to be rebuild at least once to render them correctly since fsfe.min.css is no longer available. But probably a full rebuild would make sense anyway.
I wrote a ticket for updating the wiki and send a mail to the list: #967