Behance Frontend Framework
JavaScript Other
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
Component CloudUploader: propagate the original file name Jan 17, 2017
Controller Build: replace jscs/jshint with eslint Sep 9, 2016
View Build: replace jscs/jshint with eslint Sep 9, 2016
docs HTML docs with grunt task to also push to gh-pages Jun 18, 2014
dom FileReader: nbd/Promise -> Promise Jan 9, 2017
ractive Build: replace jscs/jshint with eslint Sep 9, 2016
template Dialog: ported from be.net May 15, 2014
test CloudUploader: propagate the original file name Jan 17, 2017
trait Build: replace jscs/jshint with eslint Sep 9, 2016
ui/trait Build: replace jscs/jshint with eslint Sep 9, 2016
util util/image: window.atob() -> atob() for workers Jan 9, 2017
ux ScrollFloat: allow a content context used to measure distance from bo… Jan 11, 2017
.editorconfig Adding editorconfig for current settings Jul 20, 2016
.eslintrc Build: replace jscs/jshint with eslint Sep 9, 2016
.gitignore prevent infinitescroll execution when overflowY is hidden Dec 1, 2016
.travis.yml Build: remove bower and requirejs Sep 12, 2016
.vimrc Cleaning up vimrc May 16, 2014
Component.js Component: lift the "bind must return this" restriction Sep 25, 2014
Controller.js Controller and View: using nbd 1.1 Apr 22, 2015
Gruntfile.js Build: remove bower and requirejs Sep 12, 2016
LICENSE Updating License date Jul 7, 2014
README.md README: fix instructions to mention publishing. Jan 9, 2017
View.js Controller and View: using nbd 1.1 Apr 22, 2015
karma.conf.js util/uploadValidator: use native Promise Jan 9, 2017
package.json 4.2.0 Jan 17, 2017
webpack.config.js Build: remove bower and requirejs Sep 12, 2016

README.md

BeFF Build Status

Behance Frontend Framework

Documentation

View the Docs

You can manually generate the HTML documentation of our JSDoc blocks via:

grunt docs

That Grunt task will also push the generated html files to your fork's gh-pages branch

Cutting a Release

  • Before cutting a new release, make sure your changes are merged, your master branch is up to date (pull from upstream), and you're on your master branch.
  • To create a new release, use npm version major, npm version minor, or npm version patch to update package.json and create a release commit and git version tag.
  • Finally, use git push upstream master --tags (assuming your upstream is pointed at behance/poet) to push the version commit and tags to the Poet repo.
  • Run npm publish