groups/themes/openstack/sass
Marton Kiss d97e3ba1c1 Refactor front page layout
Introduce a new layout to front page, include a map, group finder,
and tabbed upcoming events / recent activity.

Change-Id: I1a865e29e3a1174a2f0ca1636f01ee3a2d0df0a0
2014-06-17 13:06:35 +02:00
..
components Openstack theme 2013-10-24 16:34:47 +02:00
layouts Openstack theme 2013-10-24 16:34:47 +02:00
_init.scss Openstack theme 2013-10-24 16:34:47 +02:00
_mixins.scss Openstack theme 2013-10-24 16:34:47 +02:00
_normalize-rtl.scss Openstack theme 2013-10-24 16:34:47 +02:00
_normalize.scss Openstack theme 2013-10-24 16:34:47 +02:00
_print.scss Openstack theme 2013-10-24 16:34:47 +02:00
custom.scss Refactor front page layout 2014-06-17 13:06:35 +02:00
page-layouts.scss Openstack theme 2013-10-24 16:34:47 +02:00
README.txt Openstack theme 2013-10-24 16:34:47 +02:00
styles-rtl.scss Openstack theme 2013-10-24 16:34:47 +02:00
styles.scss Openstack theme 2013-10-24 16:34:47 +02:00

ABOUT SASS AND COMPASS
----------------------

This directory includes Sass versions of Zen's CSS files. (If you are wondering
how these Sass files are organized, read the css/README.txt file.)

Sass is a language that is just normal CSS plus some extra features, like
variables, nested rules, math, mixins, etc. If your stylesheets are written in
Sass, helper applications can convert them to standard CSS so that you can
include the CSS in the normal ways with your theme.

To learn more about Sass, visit: http://sass-lang.com

Compass is a helper library for Sass. It includes libraries of shared mixins, a
package manager to add additional extension libraries, and an executable that
can easily convert Sass files into CSS.

To learn more about Compass, visit: http://compass-style.org


DEVELOPING WITH SASS AND COMPASS
--------------------------------

To automatically generate the CSS versions of the scss while you are doing theme
development, you'll need to tell Compass to "watch" the sass directory so that
any time a .scss file is changed it will automatically place a generated CSS
file into your sub-theme's css directory:

  compass watch <path to your sub-theme's directory>

  If you are already in the root of your sub-theme's directory, you can simply
  type:  compass watch

While using generated CSS with Firebug, the line numbers it reports will be
wrong since it will be showing the generated CSS file's line numbers and not the
line numbers of the source Sass files. To correct this problem, you can install
the FireSass plug-in into Firefox and then edit your sub-theme's config.rb file
to set: firesass = true
  https://addons.mozilla.org/en-US/firefox/addon/firesass-for-firebug/


MOVING YOUR CSS TO PRODUCTION
-----------------------------

Once you have finished your sub-theme development and are ready to move your CSS
files to your production server, you'll need to tell sass to update all your CSS
files and to compress them (to improve performance). Note: the Compass command
will only generate CSS for .scss files that have recently changed; in order to
force it to regenerate all the CSS files, you can use the Compass' clean command
to delete all the generated CSS files.

- Delete all CSS files by running: compass clean
- Edit the config.rb file in your theme's directory and uncomment this line by
  deleting the "#" from the beginning:
    #environment = :production
- Regenerate all the CSS files by running: compass compile

And don't forget to turn on Drupal's CSS aggregation. :-)