cartodb/CartoAssets
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
36 Commits 16 Branches 5 Tags 10 MiB
SCSS 92.4%
HTML 3%
JavaScript 2.2%
CSS 1.5%
EJS 0.9%
88fd6a7c82
Go to file
xavijam 88fd6a7c82 Fixed cartostyles path in styleguide template
2016-01-14 22:19:06 +01:00
.grunt/grunt-gh-pages/gh-pages Added gh-pages task 2016-01-14 22:17:06 +01:00
src/scss Changed sizes indentation 2016-01-14 19:23:10 +01:00
styleguide Fixed cartostyles path in styleguide template 2016-01-14 22:19:06 +01:00
tasks Added gh-pages task 2016-01-14 22:17:06 +01:00
.gitignore Removed styleguide generated html 2016-01-14 14:46:59 +01:00
.hound.yml Adding HoundCI 2016-01-14 19:09:08 +01:00
.scss-lint.yml Added some excluded files from scss-linting 2016-01-14 19:23:28 +01:00
.styleguide Added gh-pages task 2016-01-14 22:17:06 +01:00
Gruntfile.js Added gh-pages task 2016-01-14 22:17:06 +01:00
LICENSE-MIT Yay CartoAssets 2016-01-14 12:14:43 +01:00
package.json Added gh-pages task 2016-01-14 22:17:06 +01:00
README.md Added gh-pages task 2016-01-14 22:17:06 +01:00

README.md

CartoAssets NPM version

Share frontend assets between different CartoDB repositories

Installation

As easy as:

  • npm install

Build

If you want to use any of the CartoAssets components, after the installation just run:

  • grunt build

Development

It will generate a UI documentation about the components in this repository:

  • grunt dev

Publish a new version in NPM

In order to publish a new version of CartoAssets you need to:

  • Change version of the package.
  • Be a collaborator of the npm module (Send an email to xavijam[at]cartodb.com).

If you have these previous steps done:

  • npm publish

Publish CartoAssets styleguide and documentation in GH-Pages

Just run this command:

  • grunt publish