convention for storing less source files in an mvc solution?

The is just more of a concept开发者_Go百科ual question, but I wanted to ask here to see what others are doing and perhaps agree upon a convention. I maintain a nuget package that installs several css and javascript files. And because the css is compiled from less source files, I've recently been asked to include the less files in the package for those that wish to customize and compile it themselves. Right now i'm thinking Content/less. Any other suggestions?

Chris

---

Haha, that's funny I was just debating over this the other day.

I ended up settling on pretty much the same thing you suggested Content/Less. But if I have a lot of stuff in the content folder I tend to do Content/Styles/ in which case I would probably put the Less folder in there.

I like the idea of including the Less files in the package though, I could see that being useful.

Upvote for less.js though! So handy!