compass-aurora-os 0.1.0

data/templates/shared/README-Partials.md

@@ -0,0 +1,82 @@
+# Theme partials
+
+
+## Intro to Sass partials
+
+This directory contains includes known as [Sass partials](http://sass-lang.com/docs/yardoc/file.SASS_REFERENCE.html#partials). Like PHP, Sass can
+"include" files and incorporate them into a larger master file. You can easily
+identify a Sass partial because it begins with an underscore, indicating to Sass
+that it should not generate a standalone .css file from the original .scss
+
+Beyond that there are no enforced rules. It's up to each team to decide how
+they're used.
+
+
+## How does this theme use partials?
+
+We incorporated the use of Sass partials and the [nesting](http://sass-lang.com/docs/yardoc/file.SASS_REFERENCE.html#nested_rules) architecture that Sass
+provides to provide a more human-understandable organization to the CSS files.
+
+We've also leveraged the respond-to Sass extension, which allows us to embed
+rules involving media queries directly into each component rather than relying
+on the extremely encumbering method of grouping styles per media query.
+
+We have set up the CSS so that each file represents a component of the website.
+If you are making changes to the Funding section, the styles belong in the
+funding partial. If a style should be applied sitewide then place it in one of
+the global partials.
+
+**Example**
+
+*Writing this Sass...*
+
+    #block-views-myview {
+      padding: 1em;
+    
+      h2 {
+        font-size: 2em;
+        color: #fff;
+      }
+    
+      p {
+        line-height: 2em;
+      }
+    }
+
+*Produces this CSS...*
+
+    #block-views-myview {
+      padding: 1em;
+    }
+    
+    #block-views-myview h2 {
+      font-size: 2em;
+      color: #ffffff;
+    }
+    
+    #block-views-myview p {
+      line-height: 2em;
+    }
+
+
+## Benefits
+
+The files are organized into a pattern that humans understand, rather than having
+to be trained to separate styles into layout/typography/brand, or having to jump
+between three media queries in order to consistently apply a change to an element
+that changes appearance between mobile/tablet/desktop.
+
+You can choose to stop using Sass at any time since it generates pure CSS files
+each time you save a .scss file. See drawbacks before proceeding.
+
+Finally, a nice side effect is that code split amongst many files makes merging,
+collaborating and dealing with version control less painful.
+
+
+## Drawbacks
+
+If a team is unable or unwilling to use Sass and Compass, the .css files are
+editable, but you cannot switch back to Sass once you switch to CSS. Technically
+it is possible, but it will be a *HUGE* pain to get SCSS back in sync with CSS.
+
+Besides, once you try Sass you will not want to go back :)

data/templates/shared/README-Sass.md

@@ -0,0 +1,77 @@
+ABOUT SASS AND COMPASS
+----------------------
+
+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.
+
+[Learn more about Sass](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.
+
+[Learn more about Compass](http://compass-style.org)
+
+HANDLING DEPENDENCIES
+---------------------
+
+Dependencies in Ruby are best handled by [Bundler](http://gembundler.com/). Bundler works by having you define a `Gemfile` of dependent gems and their version numbers, allowing you to ensure that the correct version of all of your gems are used. New Aurora subthemes come with a `Gemfile`, but if you do not have one already, you can create one yourself. Here is the contents of the `Gemfile` supplied by the current version of Aurora.
+
+`# Pull gems from RubyGems
+source 'https://rubygems.org'
+# ~> Refers to all versions of the given gem on the current full version number, so it will be able to use any version of Compass Aurora until Compass Aurora 4.x.x. For a specific version of a gem, remove the ~>
+gem 'compass-aurora', '~>3.0.0'
+gem 'toolkit', '~>1.0.0'
+gem 'singularitygs', '~>1.0.7'
+gem 'breakpoint', '~>2.0.2'
+gem 'sassy-buttons', '~>0.1.4'
+gem 'compass-normalize', '~>1.4.3'`
+
+These are the version numbers of these gems needed for Aurora 3.x. If you are using older versions of these gems, or require older versions of these gems, please change them to the versions you need. To see what versions of the gems you have installed, enter either `gem list` in the command line to see a list of all gems and their versions, or `gem list {name}` to see the list of versions for the named gem.
+
+Once you have your `Gemfile` written, you need to install the gems so you can use them. To do so, in the command line, type the following: 
+
+`bundle install`
+
+This will create a `Gemfile.lock` file with all relevant dependencies which should be committed into your version control.
+
+
+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:
+
+  `bundle exec 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:  `bundle exec compass watch`
+
+While using generated CSS with your browser's inspectors, 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. By default, Compass will output a comment with what line and what partial the CSS is comming from above the selector. This is useful if you're looking at your CSS file itself, but not as useful if you're trying to debug straight from your inspector. If you'd like to debug straight from your inspector, there are two options, one for Google Chrome and one for Firefox.
+
+If you are using Firefox, you can install the [FireSass](https://addons.mozilla.org/en-US/firefox/addon/firesass-for-firebug/) plug-in into Firefox. Then, edit your sub-theme's config.rb file so Firesass is true (`firesass = true`) and make sure that `sass_options = :debug_info => true` is enabled (in the example config.rb file, there's a check for whether you're on the development environment). If you are using Google Chrome, make sure the Debug Info is enabled as well, go to `about://flags`, Enable Developer Tools experiments, restart Chrome, open your inspector, click settings (the gear on the bottom right), open experiments, and check Support for Sass.
+
+
+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 beginnning:
+    `#environment = :production`
+- Regenerate all the CSS files by running: `compass compile`
+
+And don't forget to turn on Drupal's CSS aggregation. :-)

data/templates/shared/README-templates.md

@@ -0,0 +1,3 @@
+# Drupal Custom Template Folder
+
+Put any templates to override Aurora templates, Drupal Core templates, Drupal Contrib templates, or any custom templates in this folder.

data/templates/shared/_extendables.scss

@@ -0,0 +1,22 @@
+////////////////////////
+// Extendables Partials
+//
+// All of your extendable classes, ids, and placeholder extendables
+//   should go in this file.
+////////////////////////
+
+.clearfix {
+	@if $legacy-support-for-ie6 or $legacy-support-for-ie7 {
+    *zoom: 1;
+  }
+
+  &:before,
+  &:after {
+    display: table;
+    content: "";
+  }
+
+  &:after {
+    clear: both;
+  }
+}

data/templates/shared/_functions.scss

@@ -0,0 +1,5 @@
+////////////////////////
+// Functions Partials
+//
+// All of your functions should go in this file.
+////////////////////////

data/templates/shared/_mixins.scss

@@ -0,0 +1,5 @@
+////////////////////////
+// Mixins Partials
+//
+// All of your mixins should go in this file.
+////////////////////////

data/templates/shared/_variables.scss

@@ -0,0 +1,5 @@
+////////////////////////
+// Variables Partials
+//
+// All of your variables should go in this file.
+////////////////////////

data/templates/shared/aurora.info.erb

@@ -0,0 +1,69 @@
+<% project_name = File.basename(Compass.configuration.project_path) %><% project_js = Compass.configuration.javascripts_dir %><% project_css = Compass.configuration.css_dir %>name =  <%= project_name %>
+description =  <%= project_name %> theme based on the Aurora base theme.
+core = 7.x
+base theme = aurora
+
+; ========================================
+; Regions
+; ========================================
+
+regions[header]       = 'Header'
+regions[main_prefix]  = 'Main Region Prefix'
+regions[content]      = 'Main Region'
+regions[main_suffix]  = 'Main Region Suffix'
+regions[footer]       = 'Footer'
+
+; ========================================
+; Stylesheets
+; ========================================
+
+stylesheets[all][] = '<%= project_css %>/style.css'
+stylesheets[print][] = '<%= project_css %>/print.css'
+
+; If installed through Bower
+; stylesheets[all][] = 'components/formalize/assets/css/formalize.css'
+
+; ========================================
+; Scripts
+; ========================================
+
+; If installed through Bower
+; scripts[] = 'components/formalize/assets/js/jquery.formalize.min.js'
+
+; ========================================
+; Modernizr
+; ========================================
+
+modernizr[tests][] = css_boxsizing
+
+; ========================================
+; Settings
+; ========================================
+
+settings[toggle_node_user_picture] = '1'
+settings[toggle_comment_user_picture] = '1'
+settings[toggle_comment_user_verification] = '1'
+settings[default_logo] = '1'
+settings[logo_path] = ''
+settings[logo_upload] = ''
+settings[default_favicon] = '1'
+settings[favicon_path] = ''
+settings[favicon_upload] = ''
+settings[hide_recomended_modules] = '0'
+settings[aurora_enable_chrome_frame] = '1'
+settings[aurora_min_ie_support] = '10'
+settings[aurora_html_tags] = '1'
+settings[aurora_typekit_id] = '0'
+settings[aurora_livereload] = '0'
+settings[magic_embedded_mqs] = '0'
+settings[magic_css_excludes] = ''
+settings[magic_footer_js] = '0'
+settings[magic_library_head] = '0'
+settings[magic_experimental_js] = '0'
+settings[magic_js_excludes] = ''
+settings[magic_rebuild_registry] = '0'
+settings[magic_viewport_indicator] = '0'
+settings[magic_modernizr_debug] = '0'
+settings[magic_performance__active_tab] = 'edit-dev'
+settings[magic_css_excludes_regex] = ''
+settings[magic_js_excludes_regex] = ''

data/templates/shared/bowerrc.txt

@@ -0,0 +1,3 @@
+{
+  "directory" : "components"
+}

data/templates/shared/component.json.erb

@@ -0,0 +1,8 @@
+<% project_name = File.basename(Compass.configuration.project_path) %><% project_js = Compass.configuration.javascripts_dir %><% project_css = Compass.configuration.css_dir %>{
+  "name": "<%= project_name%>",
+  "version": "1.0.0",
+  "dependencies": {
+    "formalize": "git://github.com/nathansmith/formalize"
+  },
+  "devDependencies": {}
+}

data/templates/shared/config.rb.erb

@@ -0,0 +1,40 @@
+<% project_name = File.basename(Compass.configuration.project_path) %><% project_js = Compass.configuration.javascripts_dir %><% project_css = Compass.configuration.css_dir %><% project_sass = Compass.configuration.sass_dir %><% project_img = Compass.configuration.images_dir %><% project_fonts = Compass.configuration.fonts_dir %># Require any additional compass plugins here.
+require 'aurora-os'
+
+# Set this to the root of your project when deployed:
+http_path = "/sites/all/themes/<%= project_name %>"
+css_dir = "<%= project_css %>"
+sass_dir = "<%= project_sass %>"
+images_dir = "<%= project_img %>"
+javascripts_dir = "<%= project_js %>"
+fonts_dir = "<%= project_fonts %>"
+
+# Change this to :production when ready to deploy the CSS to the live server.
+# Note: If you are using grunt.js, these variables will be overriden.
+environment = :development
+#environment = :production
+
+# To enable relative paths to assets via compass helper functions. Since Drupal themes can be installed in multiple locations, we shouldn't need to worry about the absolute path to the theme from the server root.
+relative_assets = true
+
+# To enable debugging comments that display the original location of your selectors. Comment:
+line_comments = false
+
+# In development, we can turn on the debug_info to use with FireSass or Chrome Web Inspector. Uncomment:
+# debug = true
+
+
+##############################
+## You probably don't need to edit anything below this.
+##############################
+
+# Disable cache busting on image assets
+asset_cache_buster :none
+
+# You can select your preferred output style here (can be overridden via the command line):
+# output_style = :expanded or :nested or :compact or :compressed
+output_style = (environment == :development) ? :expanded : :compressed
+
+# Pass options to sass. For development, we turn on the FireSass-compatible
+# debug_info if the debug config variable above is true.
+sass_options = (environment == :development && debug == true) ? {:debug_info => true} : {}

data/templates/shared/editorconfig.txt

@@ -0,0 +1,21 @@
+# EditorConfig helps developers define and maintain consistent
+# coding styles between different editors and IDEs
+# editorconfig.org
+
+root = true
+
+
+[*]
+
+# Change these settings to your own preference
+indent_style = space
+indent_size = 2
+
+# We recommend you to keep these unchanged
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.md]
+trim_trailing_whitespace = false

data/templates/shared/gitignore.txt

@@ -0,0 +1,2 @@
+node_modules/
+.sass-cache/

data/templates/shared/jshintrc.txt

@@ -0,0 +1,24 @@
+{
+    "browser": true,
+    "bitwise": true,
+    "devel": true,
+    "curly": true,
+    "eqeqeq": true,
+    "forin": true,
+    "immed": true,
+    "indent": 2,
+    "jquery": true,
+    "latedef": true,
+    "newcap": true,
+    "noarg": true,
+    "quotmark": true,
+    "regexp": true,
+    "undef": true,
+    "unused": true,
+    "trailing": true,
+    "smarttabs": true,
+    "predef": [
+        "Drupal",
+        "Modernizr"
+    ]
+}

data/templates/shared/package.json.erb

@@ -0,0 +1,19 @@
+<% project_name = File.basename(Compass.configuration.project_path) %><% project_js = Compass.configuration.javascripts_dir %><% project_css = Compass.configuration.css_dir %>{
+  "name": "<%= project_name%>",
+  "version": "1.0.0",
+  "dependencies": {},
+  "devDependencies": {
+    "grunt": "~0.4.0",
+    "grunt-contrib-watch": "~0.4.3",
+    "grunt-contrib-compass": "~0.2.0",
+    "grunt-contrib-jshint": "~0.1.1",
+    "grunt-contrib-uglify": "~0.2.0",
+    "grunt-contrib-imagemin": "~0.1.4",
+    "grunt-parallel": "~0.1.0",
+    "grunt-svgmin": "~0.1.0",
+    "grunt-contrib-copy": "~0.4.1"
+  },
+  "engines": {
+    "node": ">=0.8.0"
+  }
+}

data/templates/shared/template.php.erb

@@ -0,0 +1,180 @@
+<% project_name = File.basename(Compass.configuration.project_path) %><% project_js = Compass.configuration.javascripts_dir %><% project_css = Compass.configuration.css_dir %><?php
+
+/**
+ * Override or insert variables into the maintenance page template.
+ *
+ * @param $vars
+ *   An array of variables to pass to the theme template.
+ * @param $hook
+ *   The name of the template being rendered ("maintenance_page" in this case.)
+ */
+function <%= project_name %>_preprocess_maintenance_page(&$vars, $hook) {
+  // When a variable is manipulated or added in preprocess_html or
+  // preprocess_page, that same work is probably needed for the maintenance page
+  // as well, so we can just re-use those functions to do that work here.
+  // <%= project_name %>_preprocess_html($variables, $hook);
+  // <%= project_name %>_preprocess_page($variables, $hook);
+
+  // This preprocessor will also be used if the db is inactive. To ensure your
+  // theme is used, add the following line to your settings.php file:
+  // $conf['maintenance_theme'] = '<%= project_name %>';
+  // Also, check $vars['db_is_active'] before doing any db queries.
+}
+
+/**
+ * Implements hook_modernizr_load_alter().
+ *
+ * @return
+ *   An array to be output as yepnope testObjects.
+ */
+/* -- Delete this line if you want to use this function
+function <%= project_name %>_modernizr_load_alter(&$load) {
+
+}
+
+/**
+ * Implements hook_preprocess_html()
+ *
+ * @param $vars
+ *   An array of variables to pass to the theme template.
+ * @param $hook
+ *   The name of the template being rendered ("html" in this case.)
+ */
+/* -- Delete this line if you want to use this function
+function <%= project_name %>_preprocess_html(&$vars) {
+
+}
+
+/**
+ * Override or insert variables into the page template.
+ *
+ * @param $vars
+ *   An array of variables to pass to the theme template.
+ * @param $hook
+ *   The name of the template being rendered ("page" in this case.)
+ */
+/* -- Delete this line if you want to use this function
+function <%= project_name %>_preprocess_page(&$vars) {
+
+}
+
+/**
+ * Override or insert variables into the region templates.
+ *
+ * @param $vars
+ *   An array of variables to pass to the theme template.
+ * @param $hook
+ *   The name of the template being rendered ("region" in this case.)
+ */
+/* -- Delete this line if you want to use this function
+function <%= project_name %>_preprocess_region(&$vars, $hook) {
+
+}
+// */
+
+/**
+ * Override or insert variables into the block templates.
+ *
+ * @param $vars
+ *   An array of variables to pass to the theme template.
+ * @param $hook
+ *   The name of the template being rendered ("block" in this case.)
+ */
+/* -- Delete this line if you want to use this function
+function <%= project_name %>_preprocess_block(&$vars, $hook) {
+
+}
+// */
+
+/**
+ * Override or insert variables into the entity template.
+ *
+ * @param $vars
+ *   An array of variables to pass to the theme template.
+ * @param $hook
+ *   The name of the template being rendered ("entity" in this case.)
+ */
+/* -- Delete this line if you want to use this function
+function <%= project_name %>_preprocess_entity(&$vars, $hook) {
+
+}
+// */
+
+/**
+ * Override or insert variables into the node template.
+ *
+ * @param $vars
+ *   An array of variables to pass to the theme template.
+ * @param $hook
+ *   The name of the template being rendered ("node" in this case.)
+ */
+/* -- Delete this line if you want to use this function
+function <%= project_name %>_preprocess_node(&$vars, $hook) {
+  $node = $vars['node'];
+}
+// */
+
+/**
+ * Override or insert variables into the field template.
+ *
+ * @param $vars
+ *   An array of variables to pass to the theme template.
+ * @param $hook
+ *   The name of the template being rendered ("field" in this case.)
+ */
+/* -- Delete this line if you want to use this function
+function <%= project_name %>_preprocess_field(&$vars, $hook) {
+
+}
+// */
+
+/**
+ * Override or insert variables into the comment template.
+ *
+ * @param $vars
+ *   An array of variables to pass to the theme template.
+ * @param $hook
+ *   The name of the template being rendered ("comment" in this case.)
+ */
+/* -- Delete this line if you want to use this function
+function <%= project_name %>_preprocess_comment(&$vars, $hook) {
+  $comment = $vars['comment'];
+}
+// */
+
+/**
+ * Override or insert variables into the views template.
+ *
+ * @param $vars
+ *   An array of variables to pass to the theme template.
+ */
+/* -- Delete this line if you want to use this function
+function <%= project_name %>_preprocess_views_view(&$vars) {
+  $view = $vars['view'];
+}
+// */
+
+
+/**
+ * Override or insert css on the site.
+ *
+ * @param $css
+ *   An array of all CSS items being requested on the page.
+ */
+/* -- Delete this line if you want to use this function
+function <%= project_name %>_css_alter(&$css) {
+
+}
+// */
+
+/**
+ * Override or insert javascript on the site.
+ *
+ * @param $js
+ *   An array of all JavaScript being presented on the page.
+ */
+/* -- Delete this line if you want to use this function
+function <%= project_name %>_js_alter(&$js) {
+
+}
+// */