tachyons-modular-nested 1.0.0

Tachyons module for styling nested elements generated by a cms.

Stats

505 | 17 | 21 ---|---|--- bytes | selectors | declarations

Installation

With npm

npm install --save-dev tachyons-modular-nested

Learn more about using css installed with npm:

• https://webpack.github.io/docs/stylesheets.html
• https://github.com/defunctzombie/npm-css

With Git

http:

git clone https://github.com/particlecss/tachyons-modular.git

ssh:

git clone [email protected]:particlecss/tachyons-modular.git

Usage

Using with Postcss

Import the css module

@import "tachyons-modular-nested";

Then process the css using the tachyons-cli

$ npm i -g tachyons-cli
$ tachyons path/to/css-file.css > dist/t.css

Using the css

CDN

The easiest and most simple way to use the css is to use the cdn hosted version. Include it in the head of your html with:

<link rel="stylesheet" href="http://unpkg.com/[email protected]/build/build.min.css" />

Locally

The built css is located in the build directory. It contains an unminified and minified version. You can either cut and paste that css or link to it directly in your html.

<link rel="stylesheet" href="path/to/module/build/build.min.css">

Development

The source css files can be found in the src directory. Running $ npm start will process the source css and place the built css in the css directory.

The css

/*

    NESTED
    Tachyons module for styling nested elements
    that are generated by a cms.

*/
/**
 * Dependengies (color variables)
 * TODO: define local variables for colors
 * TODO: formart to stylelint standard
 */
/*

   Tachyons
   COLOR VARIABLES

   Grayscale
   - Solids
   - Transparencies
   Colors

*/
.nested-copy-line-height p, .nested-copy-line-height ul,
.nested-copy-line-height ol { line-height: 1.5; }
.nested-headline-line-height h1, .nested-headline-line-height h2,
.nested-headline-line-height h3, .nested-headline-line-height h4,
.nested-headline-line-height h5, .nested-headline-line-height h6 { line-height: 1.25; }
.nested-list-reset ul, .nested-list-reset ol { padding-left: 0; margin-left: 0; list-style-type: none; }
.nested-copy-indent p + p { text-indent: 1em; margin-top: 0; margin-bottom: 0; }
.nested-copy-seperator p + p { margin-top: 1.5em; }
.nested-img img { width: 100%; max-width: 100%; display: block; }
.nested-links a { color: #357edd; -webkit-transition: color .15s ease-in; transition: color .15s ease-in; }
.nested-links a:hover { color: #96ccff; -webkit-transition: color .15s ease-in; transition: color .15s ease-in; }
.nested-links a:focus { color: #96ccff; -webkit-transition: color .15s ease-in; transition: color .15s ease-in; }

Contributing

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request

Authors

• mrmrs
• johno

License

ISC