Artoo (R2-D2)

This utility droid provides a set of single-purpose, responsive and functional helpers for writing CSS within the Galaxy.

Installation

$ npm install --save-dev @theholocron/artoo

Table of Contents

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

Usage

There are a few things that are provided with this library. At its core, this is a (S)CSS mixin library using dart-sass modules. By default, mixins are available in a namespace based on the basename of the URL, so check out below for ways to import. Each of these will produce a CSS class that can then be used within your HTML.

// _index.scss

// include all utilities with 'artoo' as the namespace
// calls all mixins and will include in CSS output
@use "./node_modules/@theholocron/artoo/src" as artoo;

// use all utilities with a different set of breakpoints
// calls all mixins and will include in CSS output
@use "./node_modules/@theholocron/artoo/src" as artoo with (
    $breakpoints: (
        "xs": "0",
        "sm": "480px",
        "md": "768px",
        "lg": "1024px",
        "xl": "1280px",
    )
);

// include only a specific group of mixins
@use "@theholocron/artoo/src/text" as *;
// call the mixins from this group
@include text-reset();
@include text-underline();

// use only a specific mixin
@use "@theholocron/artoo/src/positioning/clearfix";
// call the mixin you want to use
@include clearfix();
// call the mixin you want, but override this breakpoints
@include clearfix(
    $breakpoints: (
        "xs": "0",
        "sm": "480px",
        "md": "768px",
        "lg": "1024px",
        "xl": "1280px",
    )
);

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

If you only want the CSS, there are several configurations you can choose. The following uses unpkg as a CDN, so all of the rules apply to retrieving a specific version or file. But also provided in the dist directory are a set of compiled CSS files in both compressed and non-compressed forms. The entire library is provided as well as each directories as described below.

• The [@<semver>] is an optional field that allows you to pick a specific version, or if you omit it will grab the latest tagged version.
• The [min] is optional as well, but highly recommended if you're going to call the CSS file directly in your HTML, as its minified.
• The <type> is a required field that allows one to pick a specific group to include or include the entire set. The following are allowed types:
  • artoo - the entire collection
  • a11y - only include accessible
  • box-model - only include box model
  • images - only include images
  • positioning - only include positioning
  • text - only include text

<link rel="stylesheet" href="https://unpkg.com/@theholocron/artoo[@<semver>]/dist/<type>.[min].css" />

Once you've determined how you're going to include the files, then copy the code below, swapping out the <property-name> for one of the ones in a collection listed above (check each README for a list of the actual properties). By default the <property-name> is not responsive, but if you add any one of the keywords (xs, sm, md, lg, xl) preceded with a dash - and combine it with -up for sizes at that break point and up, or -down for sizes at that breakpoint and down, or -only for the range between that particularly break point, you can make it responsive.

<div class="<property-name>[-<breakpoint keyword>]">Text</div>

Where to Find Documentation

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

• A11Y - A11Y is a module of CSS that lets deal with accessibility concerns.
• Box Model - Box model is a module of CSS that defines the rectangular boxes—including their padding and margin—that are generated for elements and arranged according to the visual formatting model.
• Images - Images is a module of CSS that defines what types of images can be used (the <image> type, containing URLs, gradients and other types of images), how to resize them and how they, and other replaced content, interact with the different layout models.
• Positioning - Positioning is a module of CSS that defines how to position elements on the page.
• Text - Text is a module of CSS that defines how to perform text manipulation, like line breaking, justification and alignment, white-space handling, and text transformation.

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.

Tools We Use

• Browserslist - Used to share to our code which browsers we support
• CommitLint - Used to ensure our commits follow our standards
• Dart Sass - Used to compile (S)CSS
• Conventional Changelog - Used to generate our CHANGELOG
• Husky - Used for auto-fixing linting errors on each commit
• MarkdownLint - Used to lint our Markdown docs
• PostCSS - Used to compile (S)CSS
• Semantic Release - Used for automating and releasing our library
• StyleLint - Used to lint our (S)CSS
• True - Used to test our (S)CSS mixins and functions
• @godban's Browser Support Badges - The tool used to generate the "Which Browsers [sic] We Support" section

References

• Conventional Commits - For how we format commit messages
• Contributor Convenant
• Keep a Changelog - For building out a quality CHANGELOG
• Make a README - For building out this README
• SemVer - For versioning this library

License

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