Considering the switch from less to sass – initialisation settings

[cmscss]

Hi There,

We currently use codkit to compile our less and use both a theme.less file and theme.js file to import components and use a directory structure we like (and one that suits our CMS).

But when we initialise a Sass, Compass or Foundation project in Codekit, the directory structure is created for us.

Is it possible to control and initialise a Sass-based project using a custom directory structure?

We’re obviously using the wrong search terms as nothing we understand comes up – any pointers in the right direction would be much appreciated.

Cheers

Ben

[cmscss]

Thanks for the reply, it creates this flat structure (we create the .php template files):

/theme-name
    a-template-name.php
    /css
    /scss
    /bower_componants
    bower.json
    index.html
    /js
    package.json
    README.md
    template-name-two.php

We prefer to have all theme-related files separated from the actual templates in an /assets directory like this:

/theme-name
    /assets
        /css
        /scss
        /bower_componants
        bower.json
        /js
        package.json
        README.md
    a-template-name.php
    template-name-two.php

Or maybe it’s the index.html which is created that is throwing us – do we just initialise the Sass project inside an /assets directory?

In the past (3 years ago) it seemed like Sass was very specific about it’s structure so maybe we misunderstood.

[cmscss]

OK – thanks heaps!

Will search for info on config files.

Cheers

[nixnerd]

It’s probably worth also installing Compass. Tons of x-browser @mixins out of the box and setting up projects is a breeze. It’s even easier with a bash script to set everything up!

[Author]

Posts