Discussion Forum

asiral

Member

Registered: May 18, 2013

Posts: 43

LESS Import Directory

Just a suggestion here: Some open source projects have separation between less files and css files (/js, /css, /less).  I prefer this organization, too.  In order to implement this right now, I need to edit a hard-coded path in the router: SITE_ROOT . "css/".  It would be easy to turn this into a variable, which as a filesystem path seems appropriate, and also allows for this organizational scheme.

timbuckingham

Administrator

From: Baltimore, MD

Registered: April 2, 2012

Posts: 978

Re: LESS Import Directory

It makes sense that we should let users choose the path. What do you think about:

- If the user places a "/" in the path to the CSS or LESS file, assume we're including relative to /site/ (so you could do "less/file.less" and it would include "/site/less/file.less")
- If the user doesn't have a "/" in the path, include relative to /site/css/ for backwards compatibility (so "file.less" would still include "/site/css/file.less")