--
You received this message because you are subscribed to the Google Groups "Compass" group.
To view this discussion on the web visit https://groups.google.com/d/msg/compass-users/-/e61IwAvg-2MJ.
To post to this group, send email to compas...@googlegroups.com.
To unsubscribe from this group, send email to compass-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/compass-users?hl=en.
If it works then your import worked.
http://compass-style.org/reference/compass/css3/
- brajeshwar
I end up putting the site specific stuff in default.sass.
Just wondering if that's a good idea or should I build up a 'common'
default.sass (.css) and then create the site specific parts in a
separate site.sass file.
Presumably I can set up site.sass so that it has access to the things in
default.sass.
Is this the way most people manage multiple sites with a common 'base'?
Much thanks! That worked.
Dave.
I think this is more of a discipline which one develops that best
suits oneself. There are numerous articles online that gives you a
guiding framework, guideline on how to organize your files (CSS).
These can be suited to SCSS/SASS files organization.
What's good thing about Sass is that, you can do whatever you want and
still get just one single CSS generated which you might not even look
at while working. I've one Sass file that imports all others (which
are organized into folders according to their functions or modules).
Looking back at each project, I find that no two are same and I tend
to keep modifying stuffs, organization, et al.
I, however, have a template where I know I'll just pluck when I start
a new Project and then build ahead from there. I usually tend not to
touch them so I can do a diff and see what I should add in to the
template files if I come across something that is useful or better
code.
- brajeshwar
> --
> You received this message because you are subscribed to the Google Groups "Compass" group.