cartodb/CartoAssets
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
76 Commits 16 Branches 5 Tags 10 MiB
SCSS 92.4%
HTML 3%
JavaScript 2.2%
CSS 1.5%
EJS 0.9%
71e661e557
Go to file
Javier Arce 71e661e557 Adds troubleshooting section
2016-01-18 18:32:26 +01:00
icon-font Adds svgs back 2016-01-18 18:30:56 +01:00
src Adds svgs back 2016-01-18 18:30:56 +01:00
styleguide Added a new basic section for styleguide 2016-01-18 17:48:11 +01:00
tasks Adds generate-font command 2016-01-18 11:16:53 +01:00
.gitignore Adds svgs back 2016-01-18 18:30:56 +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 Adds generate-font command 2016-01-18 11:16:53 +01:00
Gulpfile.js Renamed icon_font to icon-font 2016-01-18 16:31:43 +01:00
Icon-Fonting.md Adds troubleshooting section 2016-01-18 18:32:26 +01:00
LICENSE-MIT Yay CartoAssets 2016-01-14 12:14:43 +01:00
package.json Add contributors. Bump version 2016-01-18 11:48:50 +01:00
README.md Moved icon font help to a new file 2016-01-18 16:33:54 +01:00

README.md

CartoAssets NPM version

Share frontend assets between different CartoDB repositories

Installation

As easy as:

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

If you want to check the documenation, it is generated in the dist folder.

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