npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

jigsass-tools-typography

v1.4.0

Published

Typographic sass tools

Downloads

25

Readme

JigSass Tools typography

NPM version Build Status Dependency Status

A REM-based typographic system with support for responsive vertical rhythms, named-sizes and flexible modular scales.
Inspired by accoutrement-scale

Installation

Using npm:

npm i -S jigsass-tools-typography

Usage

@import 'path/to/jigsass-tools-typography/scss/index';

jigsass-tools-typography is based on a typographic system that sets the font-size of the html element to a fourth of the desired line-height, which will then serve as the base-unit for establishing and maintaining a vertical rhythm. It then sets the font-size of the body element to the base font size, and its line-height to 4rem.

By default, the base font size is set at 16px, while the vertical rhythm is at 6px, giving us a default line-height 1.5 times the default font-size (24px).

All sizes can be defined on a per-breakpoint level. jigsass-tools-typography depends on jigsass-tools-mq to manage media-queries and breakpoints definitions.

A good place to start at, is by defining these two sizes and other the other jigsass-tools-typography configuration variables so that they match your project's settings and design:

// Default output unit, where applicable
$jigsass-defaule-unit: rem;

// Should a pixel fallback be included for rem values
$jigsass-rem-px-fallback: false;

// User-defined ratios for building modular scales.
// Extends the default map
$jigsass-ratios: (
  some-ratio: 1.273;
);

$jigsass-default-ratio: major-second;


// Extends the default map of named-sizes.
$jigsass-sizes: (
  // ** Override defaults ** //
  // Will be set as the font-size of the `html` element
  // and used as the basic unit of vertical rhythm.
  rhythm-unit: (
    default: 6px,   // In `default` breakpoint.
    medium: 7px     // In `medium` breakpoint.
  ),      

  // Will be used to set the `font-size` of the `body` element.
  body: (
    default: 16px,  // In `default` breakpoint.
    medium: 18px,   // In `medium`breakpoint.
  ),            

  // The minimum amount of pixels above and below text lines
  min-line-padding: (default: 2px), 

  // ** Named sizes ** //
  headline: (
   default: body 3 golden,  // format: base (named-size or number) [exponent [ratio]]
  ),
)

The sizes are then easily available, converted into the unit of your choice:

@include jigsass-set-baseline;

.headline {
  @include jigsass-font-size(headline, $bps: all, $unit: rem);
  padding-right: jigsass-get-size(rhythm-unit, $unit: rem);
}

In depth documentation of jigsass-tools-typography features can be found in the sassdoc directory, or online at https://TxHawks.github.io/jigsass-tools-typography.

Documention

Documentation of JigSass Tools typography's Sass features is generated by SassDoc.

Run gulp serve:sassdoc to fire up a live server serving the documentation.

To generate documentation from annotation in the source code, run gulp sass:doc.

To disable the generation of sass documentation, create an empty noSassDoc file at the root jigsass-tools-typography directory.

Development

It is a best practice for JigSass modules to not automatically generate css on @import, but rather have to user explicitly enable the generation of specific styles from the module.

Contributions in the form of pull-requests, issues, bug reports, etc. are welcome. Please feel free to fork, hack or modify JigSass Tools typography in any way you see fit.

Writing documentation

Good documentation is crucial for scalability and maintainability. When writing your module, please do make sure that both its Sass functionality (functions, mixins, variables and placeholder selectors), as well as the CSS it generates (selectors, concepts, usage exmples, etc.) are well documented.

As mentioned above, the Sass is documented using SassDoc (Documention).

Running tests

gulp lint will, well, lint the contents scss files in the scss directory.

gulp test with run module's test using Mocha and Sassaby.

gulp tdd will watch both the Sass files and the test specs for changes, and will run tests automatically upon them.

Writing tests

JigSass Tools typography tests are written using Sassaby and Mocha. Spec files are located in the test directory.

Mocha allows us to place a call to before() in the root of any test file and it will be run once, before all the other tests in every test_*.js file. We can also require() files and assign them to the global object to make them available to all test_*.js files.

jigsass-tools-typography uses a file called helper.js can be used to set up mocha globals requires and before().

In addition to Sassaby's testing functions, jigsass-tools-typography makes a few Sass functions available to the test suite, for use inside Sassaby tests:

File structure

┬ ./
│
├─┬ scss/ 
│ └─ index.scss # The module's importable file.
│
├── sassdoc/    # Generated documentation 
│               # of the module's sass features
│
└─┬─ test/
  │
  ├─┬ helpers/
  │ │
  │ ├── importer.scss       # Used for easilty importing tested scss files
  │ │
  │ └── _test_helpers.scss  # JigSass's assertion helpers,
  │                         # for use inside Sassaby tests.
  │                         
  ├── helper.js              # Used for defining global `before()`
  │                          # functions and requiring modules.
  │                         
  └── test_jigsass-tools-typography # Specs. Mocha will automatically 
                                    # run all javascript files located
                                    # in the `test` directory.

License: MIT