JigSass Utils Display
A collection of dynamically generated css
display utility classes.
Class names follow the Emmet abbreviation
syntax, with colons (':') replaced by two dashes (
--) to follow BEM naming
conventions (It modifiies the user agent's default display).
display: none utility class name is
npm i -S jigsass-utils-display
Import JigSass Utils Display into your main scss file near its very end, together with all other utilities (utilities should always be the last to be imported).
Like all other JigSass Utils, JigSass Display does not automatically generate any CSS
when imported. You would need to explicitly indicate that each individual display
class should actually be generated in each component or object it is used in
(clarification: This will include style declarations inside
.foo and .
Doing so helps us a great deal with portability, as no matter where we import component or object partials, the correct utility classes will be generated. Think of it as a poor man's dependency management.
Developer communication is also assisted by including "dependencies" wherever they are required, as anyone going through a partial, can easily understand how it should be marked up with just a glance.
As far as bloat goes, just don't worry about it - the actual styles will only be generated once, at the location in the cascade where the Jigsass Clearfix partial was imported into the main file.
Based on the breakpoint arguments passed to
jigsass-util when including a display class, responsive
modifiers are generated according to the following logic:
So, assuming the
landscape breakpoints are defined in
(orientation: landscape) respectively,
will generate the
.u-d--f class, which is not limited to any media-query.
will generate the
.u-d--f--until-medium class, which will be in effect at
(max-width: 37.49em) and will override styles in the default class until that point.
will generate the
.u-d--f--from-large-when-landscape class, which will go into
(min-width: 64em) and (orientation: landscape) and will override styles in the default
class under these conditions.
The full documentation was generated using mdcss, and is available at https://txhawks.github.io/jigsass-utils-display/
It is a best practice for JigSass modules to not automatically generate css on
rather have the 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 Display in any way you see fit.
Good documentation is crucial for usability, scalability and maintainability. When contributing, 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.
Jigsass Display uses Jonathan Neal's mdcss.
When styles and documentation comments are not automatically generated by your module on
please use the
sgSrc/sg.scss file to enable their generation.
In addition, any file in
sgSrc/assets will be available for use in the style guide.
┬ ./│├─┬ scss/│ └─ index.scss # The module's importable file.│├─┬ sgSrc/ # Style guide sources│ ││ ├── sg.scc # It is a best practice for JigSass│ │ # modules to not automatically generate│ │ # css and documentation on `@import.`│ │ # Please use this file to enable css│ │ # and documentation comments) generation.│ ││ └── assets/ # Files in `sgSrc/assets` will be│ # available for use in the style guide│└─┬ docs/ # Documention│└── styleguide/ # Generated documentation# of the module's CSS