Arfive
This utility droid provides a set of single-purpose mixins for writing (S)CSS within the Galaxy.
Installation
$ npm install --save-dev @theholocron/arfive
Table of Contents
Usage
// include all animations with 'arfive' as the namespace
// calls all mixins and will include in CSS output
@use "@theholocron/arfive/src" as arfive;
// use all animations with a different base class
// calls all mixins and will include in CSS output
@use "@theholocron/arfive/src" as arfive with (
$base-class: '.my-animation-class'
);
// include only a specific group of mixins
@use "@theholocron/arfive/src/bounce as *";
// call the mixins from this group
@include bounce-back-forth();
@include bounce-out-down();
// use only a specific mixin
@use "@theholocron/arfive/src/bounce/back-forth";
// call the mixin you want to use
@include bounce-back-forth();
// call the mixin you want, but override this animations base class
@include bounce-back-forth('.another-class');
Then copy the code below, swapping out the <animation-name>
for one of the ones listed below. Add .infinite
to keep the animation going on forever.
<div class="animate <animation-name>">Text</div>
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. More documentation and a possible site to explore are set to come.
- bounce - these animations come from the opposite direction listed in the class (named after the direction it travels) and go slightly past the target and then oscillating a bit giving it the appearance of momentum and bounce.
- fade - these animations are a bit more subtle. They still come from the opposite direction listed in the class (named after the direction it travels) but they transition the opacity of the element instead.
- slide - these animations come from the opposite direction listed in the class (named after the direction it travels) with a smooth transition.
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:
How do I… (click to expand)
Where to Find Support
Looking to talk to someone or need some help? Please read our support guidelines.
License
©2020 GNU General Public License v3. See LICENSE for specifics.