Sassquatch is a CSS foundation and framework for Meetup, built with Sass.
Hologram documentation is built to github pages
An overview of basic Sassquatch2 conventions is also available in the wiki
Manage installation via bower:
"dependencies": {
"sassquatch2": "[email protected]:meetup/sassquatch2.git#master",
...
}
Clone this repo and run ./setup.sh
.
Code guidelines and standards are documented on the wiki
We use the Gitflow branching model for development:
develop
- default branch for active development (all PRs diff againstdevelop
)- release branches - cut from
develop
, get merged intomaster
master
- only release branches and hotfixes get committed to master- master branch in theory should always contain the latest stable release
Command | Result |
---|---|
grunt |
By default, grunt recompiles Sass and rebuilds Hologram docs |
grunt sass |
Recompiles Sass |
grunt hologram |
Rebuilds Hologram docs |
grunt clean |
Cleans compiled docs and CSS in docs/build |
grunt ghpages |
Caution: commits compiled docs for your branch to gh-pages |
Until I write the script for creating a release, the process is unfortunately manual.
Because we're using the git-flow branching model, all fix and feature commits flow into
the develop
branch. The master
branch is our "production" branch.
To create a release:
- merge changes from
develop
intomaster
- increment the version number in
bower.json
- commit the result & push
git tag -a vX.X.X -m "tag message"
- git push origin vX.X.X
Once the tag ref is pushed to origin the version is available to install in chapstick or elsewhere.