Better contribution documentation about less-docs HOT 7 CLOSED

To expand on this, a lot of web frameworks have models, views and controllers, and within the views they have template tags and filters. They document how to create each of these and how they relate to one another. To create a filter you don't need to understand the entire framework, just that it takes a certain type of input and returns a certain type of output.

I see a great benefit for explaining entry points such as creating colour functions in this manner.

from less-docs.

+1

from less-docs.

I don't mind sketching out some architecture diagrams

from less-docs.

like this one ?

http://www.gliffy.com/go/publish/4784259

from less-docs.

whoa that's awesome @lukeapage, thanks!

from less-docs.

Funny, I was just thinking about that this morning. That's a great start, Luke. I'd also say it would be awesome to have a 1/2/3 breakdown of taking on a bug / issue to what to do next to fork, edit, test, and make a pull request for your code.

I've had a lot of people express interest in contributing to LESS, and what stops them, like @Soviut is not lack of ability or passion, but lack of understanding of process (and underlying architecture), which is a really unfortunate barrier.

from less-docs.

I am closing this since lesscss.org now has developers section which contains most of these suggestions.

from less-docs.