Improvement > lite is better :)

CHANGELOG.md

@@ -1,8 +1,78 @@
-== 1.0.1 (August 19, 2012)
+=== HEAD
+
+=== 3.0.3 (March 30, 2015)
+
+* Remove unnecessary vendor prefixes.
+* Add `main` property.
+
+=== 3.0.2 (October 4, 2014)
+
+* Only alter `background-color` of links in IE 10.
+* Add `menu` element to HTML5 display definitions.
+
+=== 3.0.1 (March 27, 2014)
+
+* Add package.json for npm support.
+
+=== 3.0.0 (January 28, 2014)
+
+=== 3.0.0-rc.1 (January 26, 2014)
+
+* Explicit tests for each normalization.
+* Fix i18n for `q` element.
+* Fix `pre` text formatting and overflow.
+* Fix vertical alignment of `progress`.
+* Address `button` overflow in IE 8/9/10.
+* Revert `textarea` alignment modification.
+* Fix number input button cursor in Chrome on OS X.
+* Remove `a:focus` outline normalization.
+* Fix `figure` margin normalization.
+* Normalize `optgroup`.
+* Remove default table cell padding.
+* Set correct display for `progress` in IE 8/9.
+* Fix `font` and `color` inheritance for forms.
+
+=== 2.1.3 (August 26, 2013)
+
+* Fix component.json.
+* Remove the gray background color from active links in IE 10.
+
+=== 2.1.2 (May 11, 2013)
+
+* Revert root `color` and `background` normalizations.
+
+=== 2.1.1 (April 8, 2013)
+
+* Normalize root `color` and `background` to counter the effects of system
+  color schemes.
+
+=== 2.1.0 (January 21, 2013)
+
+* Normalize `text-transform` for `button` and `select`.
+* Normalize `h1` margin when within HTML5 sectioning elements.
+* Normalize `hr` element.
+* Remove unnecessary `pre` styles.
+* Add `main` element to HTML5 display definitions.
+* Fix cursor style for disabled button `input`.
+
+=== 2.0.1 (August 20, 2012)
+
+* Remove stray IE 6/7 `inline-block` hack from HTML5 display settings.
+
+=== 2.0.0 (August 19, 2012)
+
+* Remove legacy browser form normalizations.
+* Remove all list normalizations.
+* Add `quotes` normalizations.
+* Remove all heading normalizations except `h1` font size.
+* Form elements automatically inherit `font-family` from ancestor.
+* Drop support for IE 6/7, Firefox < 4, and Safari < 5.
+
+=== 1.0.1 (August 19, 2012)
 
 * Adjust `small` font size normalization.
 
-== 1.0.0 (August 14, 2012)
+=== 1.0.0 (August 14, 2012)
 
 (Only the notable changes since public release)
 

CONTRIBUTING.md

@@ -0,0 +1,177 @@
+# Contributing to normalize.css
+
+Please take a moment to review this document in order to make the contribution
+process easy and effective for everyone involved.
+
+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.

README.md

@@ -1,11 +1,26 @@
-# normalize.css v1.0.1
+# normalize.css v3
 
 Normalize.css is a customisable CSS file that makes browsers render all
-elements more consistently and in line with modern standards. We researched the
-differences between default browser styles in order to precisely target only
-the styles that need normalizing.
+elements more consistently and in line with modern standards.
 
-[Check out the demo](http://necolas.github.com/normalize.css/1.0.1/test.html)
+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)
+
+## Install
+
+* [npm](http://npmjs.org/): `npm install --save normalize.css`
+* [Component(1)](https://github.com/component/component/): `component install necolas/normalize.css`
+* [Bower](http://bower.io/): `bower install --save normalize.css`
+* [cdnjs](https://cdnjs.com/libraries/normalize)
+* [Download](http://necolas.github.io/normalize.css/latest/normalize.css).
+
+No other styles should come before Normalize.css.
+
+It is recommended that you include the `normalize.css` file as untouched
+library code.
 
 ## What does it do?
 
@@ -15,28 +30,61 @@ the styles that need normalizing.
 * Improves usability with subtle improvements.
 * Explains what code does using detailed comments.
 
-## How to use it
+## Browser support
 
-Normalize.css is intended to be used as an alternative to CSS resets.
+* Google Chrome (latest)
+* Mozilla Firefox (latest)
+* Mozilla Firefox ESR
+* Opera (latest)
+* Apple Safari 6+
+* Internet Explorer 8+
 
-It's suggested that you read the `normalize.css` file and consider customising
-it to meet your needs. Alternatively, include the file in your project and
-override the defaults later in your CSS.
+[Normalize.css v1 provides legacy browser
+support](https://github.com/necolas/normalize.css/tree/v1) (IE 6+, Safari 4+),
+but is no longer actively developed.
 
-## Browser support
+## Extended details
+
+Additional detail and explanation of the esoteric parts of normalize.css.
+
+#### `pre, code, kbd, samp`
+
+The `font-family: monospace, monospace` hack fixes the inheritance and scaling
+of font-size for preformated text. The duplication of `monospace` is
+intentional.  [Source](http://en.wikipedia.org/wiki/User:Davidgothberg/Test59).
+
+#### `sub, sup`
+
+Normally, using `sub` or `sup` affects the line-box height of text in all
+browsers. [Source](http://gist.github.com/413930).
+
+#### `svg:not(:root)`
+
+Adding `overflow: hidden` fixes IE9's SVG rendering. Earlier versions of IE
+don't support SVG, so we can safely use the `:not()` and `:root` selectors that
+modern browsers use in the default UA stylesheets to apply this style. [SVG
+Mailing List discussion](http://lists.w3.org/Archives/Public/public-svg-wg/2008JulSep/0339.html)
+
+#### `input[type="search"]`
+
+The search input is not fully stylable by default. In Chrome and Safari on
+OSX/iOS you can't control `font`, `padding`, `border`, or `background`. In
+Chrome and Safari on Windows you can't control `border` properly. It will apply
+`border-width` but will only show a border color (which cannot be controlled)
+for the outer 1px of that border. Applying `-webkit-appearance: textfield`
+addresses these issues without removing the benefits of search inputs (e.g.
+showing past searches).
+
+#### `legend`
 
-* Google Chrome
-* Mozilla Firefox 3+
-* Apple Safari 4+
-* Opera 10+
-* Internet Explorer 6+
+Adding `border: 0` corrects an IE 8–11 bug where `color` (yes, `color`) is not
+inherited by `legend`.
 
-## Contribute
+## Contributing
 
-Please read my [issue
-guidelines](https://github.com/necolas/issue-guidelines).
+Please read the CONTRIBUTING.md
 
 ## Acknowledgements
 
-Normalize.css is a project by [Nicolas Gallagher](http://github.com/necolas)
-and [Jonathan Neal](http://github.com/jonathantneal).
+Normalize.css is a project by [Nicolas Gallagher](https://github.com/necolas),
+co-created with [Jonathan Neal](https://github.com/jonathantneal).

bower.json

@@ -0,0 +1,13 @@
+{
+  "name": "normalize-css",
+  "version": "3.0.3",
+  "main": "normalize.css",
+  "author": "Nicolas Gallagher",
+  "ignore": [
+    "CHANGELOG.md",
+    "CONTRIBUTING.md",
+    "component.json",
+    "package.json",
+    "test.html"
+  ]
+}