cartodb
/
CartoAssets
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
77 Commits
16 Branches
5 Tags
10 MiB
 
 
 
 
 
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '7e330cbe90'
${ noResults }
Go to file
Javier Arce 7e330cbe90
Gives format 		9 years ago
icon-font Adds svgs back 9 years ago
src Adds svgs back 9 years ago
styleguide Added a new basic section for styleguide 9 years ago
tasks Adds generate-font command 9 years ago
.gitignore Adds svgs back 9 years ago
.hound.yml Adding HoundCI 9 years ago
.scss-lint.yml Added some excluded files from scss-linting 9 years ago
.styleguide Added gh-pages task 9 years ago
Gruntfile.js Adds generate-font command 9 years ago
Gulpfile.js Renamed icon_font to icon-font 9 years ago
Icon-Fonting.md Gives format 9 years ago
LICENSE-MIT Yay CartoAssets 9 years ago
README.md Moved icon font help to a new file 9 years ago
package.json Add contributors. Bump version 9 years ago

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