(S)CSS Functions

This utility droid provides a set of single-purpose, functions for writing (S)CSS within the Galaxy.",

Installation

$ npm install --save-dev @theholocron/scss-functions

Table of Contents

• Usage
• Documentation
• Change Log
• Versioning
• Contribution
• Support
• Credits
• License

Usage

@use "./node_modules/@theholocron/scss-functions/src" as *;

.example {
    border: .0625rem solid shade(#8ce2d4, 25%);
    background-color: best-contrast(#8ce2d4, #fff, #000, 4.5, 4.5);
}

The previous examples are only a sample of what utilities are available.

Documentation

The best way to find out what's available is to check out the source code or tests but you can also take a look at the-holocron.github.io/astromech/functions or the README which have been generated by SassDoc and sassdoc-to-markdown.

• Accessibility - check contrast to ensure its compliant, fix contrast, choose the best color to match a level of contrast, and more.
• Color - a set of functions that work with, on and/or manipulate colors.
• List - a set of functions that deal with lists.
• Math - a translation of mathematical functions into (S)CSS.
• Miscellaneous - various functions that deal with breakpoints and deeply nested maps and lists.
• Number - functions that manipulate numbers; check if a value is a number, within a bounds, etc.
• String - any function that manipulates strings; input a direction and output the opposite, strip the unit suffix, replace parts of a string, and so on.

How We Track Changes

This project uses a CHANGELOG and GitHub releases which contains a curated, chronologically ordered list of notable changes for each version of a project. Read more about changelogs.

How We Version

We use SemVer for its versioning providing us an opt-in approach to releases. This means we add a version number according to the spec, as you see below. So rather than force developers to consume the latest and greatest, they can choose which version to consume and test any newer ones before upgrading. Please the read the spec as it goes into further detail.

Given a version number MAJOR.MINOR.PATCH, increment the:

• MAJOR version when you make incompatible API changes.
• MINOR version when you add functionality in a backward-compatible manner.
• PATCH version when you make backward-compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

How to Contribute

Have a bug or a feature request? Looking to contribute to advance the project? Read our contribution guide or maintenance guide first in order to understand how we do things around here. Or you could look at some of our other guides below:

• Ask or Say Something?
  • Request Support
  • Report an Error or Bug
  • Request a Feature
• Make Something?
  • Setup the Project
  • Create an Issue
  • Create a Feature Request
  • Contribute Documentation
  • Contribute Code
  • Join the Team
• Manage Something
  • Provide Support on Issues
  • Label Issues
  • Clean Up Issues and PRs
  • Create a Pull Request
  • Review Pull Requests
  • Merge Pull Requests
  • Tag a Release
  • Release a Version

Where to Find Support

Looking to talk to someone or need some help? Please read our support guidelines.

Where We Get Inspiration

• @gianablantin (A11Y color functions)
• @terkel (Math constants/functions and number functions)
• Daniel Perez Alvarez (Rad functions)
• @mdo (breakpoint function)
• @HugoGiraudel (various miscellaneous functions)
• @adamgiese (valid-quantity function)
• @davidkpiano (str-replace-batch function)

License

©2020 GNU General Public License v3. See LICENSE for specifics.