Strictly speaking, this is not really an "issue", but it's going to be a big task and we can use your help.
We will be making a couple of announcements! Hang tight, more to come...
I should mention that I have a lot of content to add already, so I will be making updates frequently.
The function reference looks good, but it's very long. The command summary after the TOC seems unnecessary - perhaps break that out into a 'cheat sheet' page?
Ha! @Synchro lol it's funny you say that, here is what I created exactly for that purpose. I wasn't going to advertise the fact that it was there yet, because I'm not finished with the structural code and the "theme" isn't what I want yet, but let me know what you think: http://upstage.github.com/cheatsheet/
btw, top navbar links are fake, so they don't work, here is the source: https://github.com/upstage/cheatsheet
My thinking is that we can cross-reference both the wiki page and the cheatsheet. But some people (like me actually) would also much prefer to have a single-page version. What I'm trying to do with at least some of the easier language features is make them available in valid yaml format, so that it's readable as-is but it can also be reused across many formats: cheatsheets, examples, even tests. I'll post something back up here when I have something to show
@jonschlinkert, thanks for the Wiki. Can we mention Visual Studio's Web Essentials extension under GUI compilers that use LESS.js?
@am11, @jaakkytt we're working on new docs here: https://github.com/less/less-docs.
It would be great if you could create issues on that repo for these requests. Thanks!
out of date