normalize-scss 3.0.3 → 4.0.0.beta.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 23e5e20b69544d934a3f78431dc898a6de304bc1
-  data.tar.gz: 8d0a04cfa5e9eb0b685151fff80eaa2a60dd2491
+  metadata.gz: 79731e8ac41e22a946593374222916a9a7a61ffb
+  data.tar.gz: beb79b209bb640362f9f82989739f74af4a822bd
 SHA512:
-  metadata.gz: 64b29d5f1095f8f02e11303d1a718f3dd1810b28599ef47057853392a8ef26f8de6342489c4cd30d246b063fcd07e21bdd5fc583a698451a7914ef291cd7886b
-  data.tar.gz: 6ef04b429c535544472d5ca7faf1b42d57c7a2721fbd582bddba16eab1e36951f739dc605d58cad8be0776c63d25934b13063274c07a43eae02a73d82fbc775e
+  metadata.gz: d4bb13e9e36e0baeb5235f05cbf10e3ce39d576dce8e1c8184244788e5f431821911d6a94147b26a1b1a43c20b8e1aed5543a8cba05124077ac300170ac667fd
+  data.tar.gz: a2190802eb25feb0ba77ebccce78332552ba05e381d8e4055e82ff9d0310993e26a1fa9db550ae437aad8a48683cf2ab35262966beb63cc09c1d182d34a2a779

data/CHANGELOG.md

@@ -1,4 +1,4 @@
-=== normalize-scss 3.0.3+normalize.3.0.3 (October 17, 2015)
+=== normalize-scss 3.0.3 (October 17, 2015)
 
 * Upgrade to Normalize.css 3.0.3.
 

data/CONTRIBUTING.md

@@ -1,177 +1,5 @@
-# Contributing to normalize.css
+# Contributing to normalize-scss
 
-Please take a moment to review this document in order to make the contribution
-process easy and effective for everyone involved.
+Updates to most CSS rules should be reported to Necolas' upstream [Normalize.css project](http://necolas.github.com/normalize.css/).
 
-Following these guidelines helps to communicate that you respect the time of
-the developers managing and developing this open source project. In return,
-they should reciprocate that respect in addressing your issue or assessing
-patches and features.
-
-
-## Using the issue tracker
-
-The issue tracker is the preferred channel for [bug reports](#bugs),
-[features requests](#features) and [submitting pull
-requests](#pull-requests), but please respect the following restrictions:
-
-* Please **do not** use the issue tracker for personal support requests.
-
-* Please **do not** derail or troll issues. Keep the discussion on topic and
-  respect the opinions of others.
-
-
-<a name="bugs"></a>
-## Bug reports
-
-A bug is a _demonstrable problem_ that is caused by the code in the repository.
-Good bug reports are extremely helpful - thank you!
-
-Guidelines for bug reports:
-
-1. **Use the GitHub issue search** – check if the issue has already been
-   reported.
-
-2. **Check if the issue has been fixed** – try to reproduce it using the
-   latest `master` branch in the repository.
-
-3. **Isolate the problem** – create a live example (e.g., on
-   [Codepen](http://codepen.io)) of a [reduced test
-   case](http://css-tricks.com/6263-reduced-test-cases/).
-
-A good bug report shouldn't leave others needing to chase you up for more
-information. Please try to be as detailed as possible in your report. What is
-your environment? What steps will reproduce the issue? What browser(s) and OS
-experience the problem? What would you expect to be the outcome? All these
-details will help people to fix any potential bugs.
-
-Example:
-
-> Short and descriptive example bug report title
->
-> A summary of the issue and the browser/OS environment in which it occurs. If
-> suitable, include the steps required to reproduce the bug.
->
-> 1. This is the first step
-> 2. This is the second step
-> 3. Further steps, etc.
->
-> `<url>` - a link to the reduced test case
->
-> Any other information you want to share that is relevant to the issue being
-> reported. This might include the lines of code that you have identified as
-> causing the bug, and potential solutions (and your opinions on their
-> merits).
-
-
-<a name="features"></a>
-## Feature requests
-
-Feature requests are welcome. But take a moment to find out whether your idea
-fits with the scope and aims of the project. It's up to *you* to make a strong
-case to convince the project's developers of the merits of this feature. Please
-provide as much detail and context as possible.
-
-
-<a name="pull-requests"></a>
-## Pull requests
-
-Good pull requests - patches, improvements, new features - are a fantastic
-help. They should remain focused in scope and avoid containing unrelated
-commits.
-
-**Please ask first** before embarking on any significant work, otherwise you
-risk spending a lot of time working on something that the project's developers
-might not want to merge into the project.
-
-Please adhere to the coding conventions used throughout a project (whitespace,
-accurate comments, etc.) and any other requirements (such as test coverage).
-
-Follow this process if you'd like your work considered for inclusion in the
-project:
-
-1. [Fork](http://help.github.com/fork-a-repo/) the project, clone your fork,
-   and configure the remotes:
-
-   ```bash
-   # Clone your fork of the repo into the current directory
-   git clone https://github.com/<your-username>/normalize.css
-   # Navigate to the newly cloned directory
-   cd normalize.css
-   # Assign the original repo to a remote called "upstream"
-   git remote add upstream https://github.com/necolas/normalize.css
-   ```
-
-2. If you cloned a while ago, get the latest changes from upstream:
-
-   ```bash
-   git checkout master
-   git pull upstream master
-   ```
-
-3. Never work directly on `master`. Create a new topic branch (off the latest
-   version of `master`) to contain your feature, change, or fix:
-
-   ```bash
-   git checkout -b <topic-branch-name>
-   ```
-
-4. Commit your changes in logical chunks. Please adhere to these [git commit
-   message conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
-   or your code is unlikely be merged into the main project. Use Git's
-   [interactive rebase](https://help.github.com/articles/interactive-rebase)
-   feature to tidy up your commits before making them public.
-
-   Make sure to add a test to the `test.html` file if appropriate, and test
-   your change in all supported browsers.
-
-5. Locally rebase the upstream development branch into your topic branch:
-
-   ```bash
-   git pull --rebase upstream master
-   ```
-
-6. Push your topic branch up to your fork:
-
-   ```bash
-   git push origin <topic-branch-name>
-   ```
-
-10. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/)
-    with a clear title and description.
-
-    Please submit a separate pull request for any appropriate changes required
-    in the `v1` branch for legacy browsers.
-
-**IMPORTANT**: By submitting a patch, you agree to allow the project owner to
-license your work under the same license as that used by the project.
-
-
-<a name="maintainers"></a>
-## Maintainers
-
-If you have commit access, please follow this process for merging patches and
-cutting new releases.
-
-### Accepting patches
-
-1. Check that a patch is within the scope and philosophy of the project.
-2. Check that a patch has any necessary tests and a proper, descriptive commit
-   message.
-3. Test the patch locally.
-4. Do not use GitHub's merge button. Apply the patch to `master` locally
-   (either via `git am` or by checking the whole branch out). Amend minor
-   problems with the author's original commit if necessary. Then push to GitHub.
-5. If a patch should be included in `v1`, cherry-pick the commits or manually
-   apply if all else fails.
-
-### Releasing a new version
-
-1. Include all new functional changes in the CHANGELOG.
-2. Use a dedicated commit to increment the version. The version needs to be
-   added to the CHANGELOG (inc. date), and the `bower.json`, `component.json`,
-   and `normalize.css` files.
-3. The commit message must be of `v0.0.0` format.
-4. Create an annotated tag for the version: `git tag -m "v0.0.0" 0.0.0`.
-5. Push the changes and tags to GitHub: `git push --tags origin master`
-6. Checkout the `gh-pages` branch and follow the instructions in the README.
+Updates to the Sass should be reported in the [Normalize-scss project](https://github.com/JohnAlbin/normalize-scss/).

data/README.md

@@ -1,45 +1,31 @@
-## Latest downloadable version
+# normalize-scss
 
-The latest release of _normalize.scss for Sass 3.4 or libSass 3.2.0 (and later) is: [4.0.0-alpha.1](https://github.com/JohnAlbin/normalize-scss/releases/tag/4.0.0-alpha.1).
-It combines normalize.css v3.0.3 and normalize v1.1.3.
+## Latest versions
 
-The latest release of _normalize.scss for Sass 3.3/Compass 1.0 (and later) is: [3.0.3+normalize.3.0.3](https://github.com/JohnAlbin/normalize-scss/releases/tag/3.0.3%2Bnormalize.3.0.3).
-It combines normalize.css v3.0.3 and normalize v1.1.3.
+For use with…                | normalize-scss version
+-----------------------------|-----------------------
+Sass 3.4 or libSass          | [4.0.0-beta.1](https://github.com/JohnAlbin/normalize-scss/releases/tag/4.0.0-beta.1)<br> combining normalize.css v3.0.3 with v1.1.3
+Ruby Sass 3.3 + Compass 1.0  | [3.0.3](https://github.com/JohnAlbin/normalize-scss/releases/tag/3.0.3)<br> combining normalize.css v3.0.3 with v1.1.3
+Ruby Sass 3.2 + Compass 0.12 | [2.2.0+normalize.2.1.3](https://github.com/JohnAlbin/normalize-scss/releases/tag/2.2.0%2Bnormalize.2.1.3)<br> combining normalize.css v2.1.3 with v1.1.3
 
-The latest release of _normalize.scss for Sass 3.2/Compass 0.12 is: [2.2.0+normalize.2.1.3](https://github.com/JohnAlbin/normalize-scss/releases/tag/2.2.0%2Bnormalize.2.1.3).
-It combines normalize.css v2.1.3 and normalize v1.1.3.
+## The Sass port of normalize.css
 
-## The Compass port of normalize.css
+__This project is the Sass version of Normalize.css__, a collection of HTML element and attribute rulesets to normalize styles across all browsers. This port aims to use a light dusting of Sass to make Normalize even easier to integrate with your website. To learn about why Normalize.css is so amazing, skip to the "normalize.css" section below.
 
-__This project is the Sass/Compass version of Normalize.css__, a collection of
-HTML element and attribute rulesets to normalize styles across all browsers.
-This port aims to use the best partials from Compass to make Normalize even
-easier to integrate with your website. To learn about why Normalize.css is so
-amazing, skip to the "normalize.css" section below.
+This Sass port currently utilizes:
 
-This Sass/Compass port currently utilizes:
+* Browser support variables: Allowing you to easily add/drop support for any browser by modifying a single Sass variable.
+* Vertical rhythm mixins: Allowing you to alter the font-size, line-height and margins in Normalize’s output without hacking the library.
 
-* Browser Support variables
-* CSS3 Box Sizing mixin
-* Vertical Rhythm mixins
+In addition, Normalize.css has 2 major versions: version 3 (without “legacy browser” support) and version 1 (with support for IE 6/7, etc.) This Sass port combines the two versions into one file so that you can easily toggle between the two versions using its browser support variables.
 
-In addition, Normalize.css has 2 major versions: version 3 (without legacy
-browser support) and version 1 (with support for IE 6/7, etc.) This Compass port
-combines the two versions into one file so that you can easily toggle between
-the two versions using Compass' Browser Support variables.
-
-Did a client wait until the last minute to mention their CEO uses IE 6? Simply
-update your `$browser-minimum-versions` variable and recompile your Sass files.
-Details can be found at https://github.com/JohnAlbin/normalize-scss/wiki
+Did a client wait until the last minute to mention their CEO uses IE 6? Simply update your `$support-for` variable and recompile your Sass files. Details can be found at https://github.com/JohnAlbin/normalize-scss/wiki
 
 # normalize.css v3
 
-Normalize.css is a customisable CSS file that makes browsers render all
-elements more consistently and in line with modern standards.
+Normalize.css is a customisable CSS file that makes browsers render all elements more consistently and in line with modern standards.
 
-The project relies on researching the differences between default browser
-styles in order to precisely target only the styles that need or benefit from
-normalizing.
+The project relies on researching the differences between default browser styles in order to precisely target only the styles that need or benefit from normalizing.
 
 [View the test file](http://necolas.github.io/normalize.css/latest/test.html)
 
@@ -58,29 +44,36 @@ Install using one of the following methods:
 * Download directly from the [project page](https://github.com/JohnAlbin/normalize-scss/releases).
 * Install with [npm](http://npmjs.org/): `npm install --save normalize-scss`
 * Install with [Bower](http://bower.io/): `bower install --save normalize.scss`
-* Install with [Component(1)](http://component.io/): `component install JohnAlbin/normalize-scss`
-* Install with [Ruby Gem](https://rubygems.org/gems/normalize-scss):
-  `gem install normalize-scss` Note: if you want to alter the _normalize.scss
-  file after installation (see "how to use it" below), you can use the
-  `gem list --details normalize-scss` command to show you where the
-  normalize-scss files were installed.
+* Install with [Ruby Gem](https://rubygems.org/gems/normalize-scss): `gem install normalize-scss`<br>
+  and, if using Compass, add `require "normalize-scss"` to your config.rb file. Note: if you want to alter the _normalize.scss file after installation (see "how to use it" below), you can use the `gem list --details normalize-scss` command to show you where the normalize-scss files were installed.
 
 ## How to use it
 
-There is a fantastic introduction to the project and brief instructions how to
-use it in the [About normalize.css article](http://nicolasgallagher.com/about-normalize-css/).
+There is a fantastic introduction to the project and brief instructions how to use it in the [About normalize.css article](http://nicolasgallagher.com/about-normalize-css/).
+
+You can use the Sass port of Normalize in one of several methods, following the "About normalize.css" article's suggestions:
+
+__Approach 1:__ Download and use normalize-scss as a starting point for your own project's base Sass, customising the values to match the design's requirements. (The best approach, _IMO_.)
+  1. Copy the normalize-scss files to your sass directory so that you can alter it
+    as you include it in your project. To aid with this method, normalize-scss
+    includes several ready-made "fork" versions:
+    * [fork-versions/default](fork-versions/default) - Fork for libSass or Ruby Sass
+    * [fork-versions/ruby-sass-compass](fork-versions/ruby-sass-compass) - Fork for Ruby Sass with Compass
+    * [fork-versions/typey](fork-versions/typey) - Fork with Typey
+    * fork-versions/typey-kss - Fork with Typey and KSS comments
+  2. The normalize-scss code uses the `support-for` module, so add it
 
-To use the Compass port of Normalize, simply:
+__Approach 2:__ Install and include normalize-scss untouched and then build upon it, overriding the defaults later in your Sass when necessary. Just import normalize-scss like any normal Sass module by:
+  1. Set variables to override the default normalize-scss variables.
+  2. Import with `@import "normalize";`
+  3. Output the CSS rules with `@include normalize();`
 
-1. copy the _normalize.scss file to your sass directory (or if installed with
-   Ruby Gem, add `require "normalize-scss"` to your config.rb file.)
-2. import the partial into your main Sass file with `@import "normalize";`
-3. and follow the "About normalize.css" article's suggestions:
-  * __Approach 1:__ use `_normalize.scss` as a starting point for your own
-    project's base Sass, customising the values to match the design's
-    requirements. (The best approach, _IMO_.)
-  * __Approach 2:__ include `_normalize.scss` untouched and build upon it,
-    overriding the defaults later in your Sass when necessary.
+Alternatively, you can import normalize-scss immediately into your main Sass file without needing to use the `normalize()` mixin by:
+
+  1. (Optionally) set variables to override the default normalize-scss variables.
+  2. Import with `@import "normalize/import-now";`
+
+Note: if you use [wiredep](https://github.com/taptapship/wiredep), normalize-scss's bower.json points at the normalize/import-now Sass partial. If you don't wish to immediately output the CSS, you will need to override the Sass partial that wiredep grabs from normalize-scss.
 
 ## Browser support
 
@@ -91,8 +84,8 @@ To use the Compass port of Normalize, simply:
 * Apple Safari 6+
 * Internet Explorer 6+
 
-The exact browsers supported in your project is controlled by Compass' Support
-variables. See https://github.com/JohnAlbin/normalize-scss/wiki
+The exact browsers supported in your project is controlled by the browser
+support variables. See https://github.com/JohnAlbin/normalize-scss/wiki
 
 ## Extended details
 
@@ -132,32 +125,25 @@ Adding `border: 0` corrects an IE 8–11 bug where `color` (yes, `color`) is not
 inherited by `legend`.
 
 ## Contributing
-Please read Necolas' [contributing
-guidelines](CONTRIBUTING.md).
+Please read Necolas' [contributing guidelines](https://github.com/necolas/normalize.css/blob/master/CONTRIBUTING.md).
 
-Updates to most CSS rules should be reported to Necolas' upstream [Normalize.css
-project](http://necolas.github.com/normalize.css/). Updates to the Sass should
-be reported in the [Normalize-scss project](https://github.com/JohnAlbin/normalize-scss/).
+Updates to most CSS rules should be reported to Necolas' upstream [Normalize.css project](http://necolas.github.com/normalize.css/). Updates to the Sass should be reported in the [Normalize-scss project](https://github.com/JohnAlbin/normalize-scss/).
 
 ## Acknowledgements
 
 Normalize.css is a project by [Nicolas Gallagher](https://github.com/necolas),
 co-created with [Jonathan Neal](https://github.com/jonathantneal).
 
-This Sass/Compass port is a project by [John Albin Wilkins](http://john.albin.net).
+This Sass port is a project by [John Albin Wilkins](http://john.albin.net).
 
 ## Other ports of Normalize.css
 
-For the record, there are several other Sass or Compass ports as well.
-Including:
+For the record, there are several other Sass ports as well. Including:
 
 * https://github.com/waynegraham/compass-normalize-plugin
 * https://github.com/ksmandersen/compass-normalize
 * https://github.com/hail2u/normalize.scss
 * https://github.com/kristerkari/normalize.scss
-
-Some of the above projects convert normalize into Sass mixins. That makes it
-impossible to add Normalize using __Approach 1__ (by copying the file into your
-website and customizing/overriding for your needs.)
+* https://github.com/krisbulman/normalize-libsass
 
 [![Build Status](https://travis-ci.org/JohnAlbin/normalize-scss.png?branch=master)](https://travis-ci.org/JohnAlbin/normalize-scss)

data/bower.json

@@ -0,0 +1,34 @@
+{
+  "name": "normalize-scss",
+  "description": "This is the Sass version of Normalize.css, a collection of HTML element and attribute rulesets to normalize styles across all browsers. This port aims to use a light dusting of Sass to make Normalize even easier to integrate with your website.",
+  "main": [
+    "sass/normalize/_import-now.scss"
+  ],
+  "authors": [
+    "John Albin Wilkins <virtually.johnalbin@gmail.com> (http://john.albin.net/)"
+  ],
+  "license": "(MIT OR GPL-2.0)",
+  "keywords": [
+    "sass",
+    "normalize",
+    "reset",
+    "typography",
+    "design",
+    "ui"
+  ],
+  "homepage": "https://github.com/JohnAlbin/normalize-scss",
+  "ignore": [
+    "**/.*",
+    "CHANGELOG.md",
+    "CONTRIBUTING.md",
+    "lib",
+    "node_modules",
+    "normalize-scss.gemspec",
+    "sache.json",
+    "test.html",
+    "test"
+  ],
+  "dependencies": {
+    "support-for": "~1.0.2"
+  }
+}

data/lib/normalize-scss.rb

@@ -1,12 +1,17 @@
-require 'compass'
-
 project_path     = File.join(File.dirname(__FILE__), '..')
-stylesheets_path = File.join(project_path)
-templates_path   = File.join(project_path, 'templates')
+stylesheets_path = File.join(project_path, 'sass')
 
-Compass::Frameworks.register(
-  'normalize-scss',
-  :path => project_path,
-  :stylesheets_directory => stylesheets_path,
-  :templates_directory => templates_path
-)
+if (defined? Compass)
+  Compass::Frameworks.register(
+    'normalize-scss',
+    :path => project_path,
+    :stylesheets_directory => stylesheets_path
+  )
+else
+  # Compass not defined, register the Sass path via an environment variable.
+  if ENV.has_key?('SASS_PATH')
+    ENV['SASS_PATH'] = ENV['SASS_PATH'] + File::PATH_SEPARATOR + stylesheets_path
+  else
+    ENV['SASS_PATH'] = stylesheets_path
+  end
+end

data/normalize-scss.gemspec

@@ -1,31 +1,32 @@
 # -*- encoding: utf-8 -*-
 
-Gem::Specification.new do |s|
-  s.name        = 'normalize-scss'
+Gem::Specification.new do |spec|
+  spec.name        = 'normalize-scss'
 
-  s.summary     = %q{The Sass/Compass version of Normalize.css}
-  s.description = %q{This is the Sass/Compass version of Normalize.css, a collection of HTML element and attribute rulesets to normalize styles across all browsers. This port aims to use the best partials from Compass to make Normalize even easier to integrate with your website.}
+  spec.summary     = %q{The Sass version of Normalize.css}
+  spec.description = %q{This is the Sass version of Normalize.css, a collection of HTML element and attribute rulesets to normalize styles across all browsers. This port aims to use a light dusting of Sass to make Normalize even easier to integrate with your website.}
 
-  s.homepage    = 'https://github.com/JohnAlbin/normalize-scss'
-  s.rubyforge_project =
+  spec.homepage    = 'https://github.com/JohnAlbin/normalize-scss'
+  spec.rubyforge_project =
 
-  s.version     = '3.0.3'
-  s.date        = '2015-10-17'
-  s.licenses    = ['GPL-2']
+  spec.version     = '4.0.0.beta.1'
+  spec.date        = '2015-11-18'
+  spec.licenses    = ['GPL-2']
 
-  s.authors     = ['John Albin Wilkins']
-  s.email       = 'virtually.johnalbin@gmail.com'
+  spec.authors     = ['John Albin Wilkins']
+  spec.email       = 'virtually.johnalbin@gmail.com'
 
-  s.add_runtime_dependency('sass',          '~> 3.3', '>= 3.3.0')
-  s.add_runtime_dependency('compass-core',  '~> 1.0', '>= 1.0.0')
+  spec.add_runtime_dependency('sass', '~> 3.3')
+  spec.add_runtime_dependency('support-for', '~> 1.0')
 
-  s.files       = %w[
-    _normalize.scss
+  spec.files       = `git ls-files`.split($/).select {|f| File.exist?(f) && f =~ %r{^(lib|sass)/} }
+  spec.files       += %w(
+    bower.json
     CHANGELOG.md
     CONTRIBUTING.md
-    lib/normalize-scss.rb
     LICENSE.md
     normalize-scss.gemspec
+    package.json
     README.md
-  ]
+  )
 end