diff --git a/.gitignore b/.gitignore new file mode 100644 index 000000000..a609a6416 --- /dev/null +++ b/.gitignore @@ -0,0 +1,4 @@ +* +!.gitignore +!_normalize.scss +!*.md \ No newline at end of file diff --git a/CHANGELOG.md b/CHANGELOG.md deleted file mode 100644 index d0e9f937c..000000000 --- a/CHANGELOG.md +++ /dev/null @@ -1,45 +0,0 @@ -== HEAD - -== 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) - -(Only the notable changes since public release) - -* Add MIT License. -* Hide `audio` elements without controls in iOS 5 (#69). -* Normalize heading margins and font size. -* Move font-family normalization from `body` to `html` (#62). -* Remove scrollbar normalization (#64 #65). -* Remove excess padding from checkbox and radio inputs in IE 7 (#42). -* Add IE9 correction for SVG overflow (#16). -* Add fix for legend not inheriting color in IE 6/7/8/9. diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md deleted file mode 100644 index 82bab9a2b..000000000 --- a/CONTRIBUTING.md +++ /dev/null @@ -1,177 +0,0 @@ -# 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. - - - -## 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. -> -> `` - 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). - - - -## 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. - - - -## 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//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 - ``` - -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 - ``` - -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. - - - -## 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 edited in the README, - `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" v0.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. diff --git a/LICENSE.md b/LICENSE.md deleted file mode 100644 index c6bcc9bf2..000000000 --- a/LICENSE.md +++ /dev/null @@ -1,19 +0,0 @@ -Copyright (c) Nicolas Gallagher and Jonathan Neal - -Permission is hereby granted, free of charge, to any person obtaining a copy of -this software and associated documentation files (the "Software"), to deal in -the Software without restriction, including without limitation the rights to -use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies -of the Software, and to permit persons to whom the Software is furnished to do -so, subject to the following conditions: - -The above copyright notice and this permission notice shall be included in all -copies or substantial portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE. diff --git a/README.md b/README.md index 62ac43cf8..3543c707c 100644 --- a/README.md +++ b/README.md @@ -1,49 +1,21 @@ -# normalize.css v2.1.1 +normalize.Scss +============= +An up-to-date SCSS version of normalize.css -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. +This way you can include it in your COMPASS projects as a submodule, getting updates to normalize.css with a simple: +$ git submodule foreach git pull +and minify it for your production environment. -[Check out the demo](http://necolas.github.io/normalize.css/2.1.0/test.html) +How to submodule: +http://git-scm.com/book/en/Git-Tools-Submodules +How to render on your development environments: +compass -e development +How to render for your production environment: +compass -e production -[Legacy browser support is available in v1](https://github.com/necolas/normalize.css/tree/v1) +============= -## Install +From the real normalize.css project: -Download from the [project page](http://necolas.github.io/normalize.css/). +A modern, HTML5-ready alternative to CSS resets (as used by Twitter Bootstrap, HTML5 Boilerplate, TweetDeck, Soundcloud, and many others). -Install with [Bower](http://bower.io/): `bower install --save normalize-css` - -## What does it do? - -* Preserves useful defaults, unlike many CSS resets. -* Normalizes styles for a wide range of elements. -* Corrects bugs and common browser inconsistencies. -* Improves usability with subtle improvements. -* Explains what code does using detailed comments. - -## How to use it - -Normalize.css is intended to be used as an alternative to CSS resets. - -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. - -## Browser support - -* Google Chrome -* Mozilla Firefox 4+ -* Apple Safari 5+ -* Opera 12+ -* Internet Explorer 8+ - -## Contribute - -Please read the CONTRIBUTING.md - -## Acknowledgements - -Normalize.css is a project by [Nicolas Gallagher](https://github.com/necolas), -co-created with [Jonathan Neal](https://github.com/jonathantneal). diff --git a/normalize.css b/_normalize.scss similarity index 100% rename from normalize.css rename to _normalize.scss diff --git a/component.json b/component.json deleted file mode 100644 index 624623916..000000000 --- a/component.json +++ /dev/null @@ -1,8 +0,0 @@ -{ - "name": "normalize-css", - "version": "2.1.1", - "author": "Nicolas Gallagher", - "homepage": "http://necolas.github.com/normalize.css/", - "main": "normalize.css", - "styles": ["normalize.css"] -} diff --git a/test.html b/test.html deleted file mode 100644 index d7103c49b..000000000 --- a/test.html +++ /dev/null @@ -1,354 +0,0 @@ - - - - - - Normalize CSS - - - - - -

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5

Heading 6

- -

Heading 1 (in section)

Heading 2 (in section)

Heading 3 (in section)

Heading 4 (in section)

Heading 5 (in section)

Heading 6 (in section)

- -

Heading 1 (in article)

Heading 2 (in article)

Heading 3 (in article)

Heading 4 (in article)

Heading 5 (in article)

Heading 6 (in article)

- -

Heading 1 (in hgroup)

Heading 2 (in hgroup)

- - -

- -

Text-level semantics

- - - -

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et m. Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et m. Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et m.

- -

Address: somewhere, world

- -

- The a element example
- The abbr element and abbr element with title examples
- The b element example
- The cite element example
- The code element example
- The ~~del element~~ example
- The dfn element and dfn element with title examples
- The em element example
- The i element example
- The img element example
- The ins element example
- The kbd element example
- The mark element example
- The q element inside a q element example
- The ~~s element~~ example
- The samp element example
- The small element example
- The span element example
- The strong element example
- The _{sub element} example
- The ^{sup element} example
- The u element example
- The var element example -

- -

Embedded content

- -

audio

- -

img

- -

svg

- - - -

video

- -

Interactive content

- -

details / summary

More info

Additional information

Point 1
Point 2

- -

Grouping content

- -

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et m.

- -

pre

- -

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et me.

- -

<html>
-    <head>
-    </head>
-    <body>
-        <div class="main"> <div>
-    </body>
-</html>

- -

blockquote

- -

-
Some sort of famous witty quote marked up with a <blockquote> and a child <p> element.
-

- -

Even better philosophical quote marked up with just a <blockquote> element.

- -

ordered list

- -

list item 1
list item 1 -
1. list item 2
2. list item 2 -
  1. list item 3
  2. list item 3
  -
3. list item 2
4. list item 2
-
list item 1
list item 1

- -

unordered list

- -

list item 1
list item 1 -
- list item 2
- list item 2 -
  - list item 3
  - list item 3
  -
- list item 2
- list item 2
-
list item 1
list item 1

- -

description list

- -

Description name: Description value
Description name: Description value; Description value
Description name
Description name: Description value

- -

figure

- -

- -

Tabular data

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Jimi Hendrix - albums
Album	Year	Price
Album	Year	Price
Are You Experienced	1967	$10.00
Axis: Bold as Love	1967	$12.00
Electric Ladyland	1968	$10.00
Band of Gypsys	1970	$12.00

- -

Forms

- -

- Inputs as descendents of labels (form legend). This doubles up as a long legend that can test word wrapping. -

Text input

Email input

Search input

Tel input

URL input

Password input

File input

- -

Radio input

Checkbox input

Radio input

Checkbox input

- -

Select field

Textarea Textarea text

- -

- Inputs as siblings of labels -

Color input

Number input

Range input

Date input

Month input

Week input

Datetime input

Datetime-local input

- -

Radio input

Checkbox input

Radio input

Checkbox input

- -

Select field

Textarea Textarea text

- -

- Clickable inputs and buttons -

- - -

- -

- box-sizing tests -

- -

- - -