Ivor saidNot sure why that’s required. Wouldn’t LESS /SASS/SCSS-savvy developers appreciate having this? As long as the compiled CSS is included it shouldn’t make any difference.
Just make sure you remove all the .less files before uploading.
I was planning on doing that for my next release actually – so will a submission be rejected for including sass/less files?
jakubt saidI didn’t know about lessphp. I’ll be looking into this combination. LESS may have fewer capabilities than SASS , Compass, etc. but I think simplicity is good in this situation.
I use LESS . It is easy to compile it server side using lessphp, or on desktop with less app (Mac only).
Lessphp looks great – I’ll have to look into that over using node.js. A co-worker of mine is fairly vocal in his opinion that SASS is better than LESS . He feels the syntax of LESS is too similar to css and can be a pain to differentiate between them, while SASS has just enough of a difference to keep it clear what is and isn’t preprocessor stuff.
I’m currently working out the details of a partnership with a co-worker to start releasing themes again and curious to hear how others have structured this. How have you handled the revenue sharing (at least in terms of percentages, and any other details), do you have a tool that extracts out the revenue for themes you’ve done together vs your own and calculates earnings, etc…
Was it successful overall for you and would you recommend doing it this way?
I like the idea of divide and concur and feel it will help me avoid the burnout I felt after each theme, but curious on others thoughts about this…
Has anyone started using either…http://twitter.github.com/bootstrap/
Or on that note, had any experience with the popular css preprocessors (ie SASS or LESS )? I’m curious if these are really beneficial or if the overhead is a burden. (ie server side compiling setup for LESS vs SASS ’s ruby requirements). I’ve stuck to a manual workflow thus far, but thinking of harnessing some of these – especially something like http://semantic.gs/.
Google made a browser and now today, every other browser is trying to imitate everything chrome does/has. The only time I use Firefox is when I want to test for compatibility!
Agreed – I finally made the switch to Chrome for my daily browser as well as completely ported my development workflow and haven’t looked back. The native (vs ff’s non-native extension) front-end development tools are so much better in my opinion. It took a couple days to acclimate, but I doubt I’ll ever go back to ff.
I don’t have the link handy but one of the developers from Envato recently did a presentation about running high traffic on WordPress. They seem to be pretty successful at it.