3.0.3

• Addressing Issue #24

3.0.2

• Updating README
• Adding different name in package.json due to name conflict
• Major update to wiki
• and more!

3.0.1

• Updating normalize.scss dependency to latest in bower.json and any version >=5.0.4 in package.json
• Updated sache tags

3.0.0

Version 3.0.0 is finally stable!

3.0.0-dev4

• Removed normalize import in fresh/vars
  • Can't determine location of import during compile time due to Sass limitations
  • Import the mixin in your created loader partial
• Added the correct normalize dep in bower.json

3.0.0-dev2

3.0.0-dev2

• Adding package.json for npm support
• Converting all core files to partials for better support for installing via bower and npm
• Decoupled Skeleton Sass
  • All themes files that @import "vars"; no longer do so
  • Importing of theme components has to be done manually by consumers.
• Added .editorconfig
• Added package.json for installing via npm

Removals

• bin/
• skeleton_template.scss
• _MYConfig.scss
• themes/demo
• var partial imports in shipped theme files

Additions

• Introduction of $new-grid-width in the global config
  • Alters the width set in .container as defined in @media (min-width: 550px)
  • Allows users to change this bizarre default 80% value set in Skeleton CSS 2

2.5.4-dev2

• Added check to ensue normalize.scss dependency is met
• Node script will run automatically as part of the bower install process

Why this check?

Sass provides no means of verifying an imports existence. To make this as portable as possible, it was decided to cover two common consumption cases:

1. User installs via:

    bower install --save skeleton-sass #installs normalize dep, no action required

2. User does something akin to this:

    git clone https://github.com/atomicpages/skeleton-sass.git
    cd path/to/skeleton-sass && git checkout development
    bower install # additional work is needed, but can be automated by the install check script

Certainly developers and consumers can fix this themselves, but we're exploring some options for upcoming releases. The main goal of this check is to simply automate a manual process in a particular use case.

2.5.4-dev1

• Added normalize.scss as a dependency
• Merged master into development

2.5.3

• Comment cleanup
• Rearranging of dependencies
• Update to year in license and other copyright headers
• Change Dir.exists? to Dir.exist? to squash ruby 2.3.x deprecation notice
• Manual bump to normalize.css 4.2.0

2.5.3-dev1

• Testing bower import and fallback functionality