Generate custom icon webfonts from SVG/EPS files via Grunt. Based on Font Custom.
This task will make all you need to use font-face icon on your website: font in all needed formats, CSS/SASS/LESS/Stylus and HTML demo page.
- Very flexible.
- Semantic: uses Unicode private use area.
- Cross-browser: IE8+.
- BEM or Bootstrap output CSS style.
- CSS preprocessors support.
- Data:uri embedding.
- Ligatures.
- HTML preview.
- Custom templates.
This plugin requires Grunt 0.4.
brew install fontforge ttfautohint
npm install grunt-webfont --save-dev
You may need to use sudo for brew, depending on your setup.
sudo apt-get install fontforge ttfautohint
npm install grunt-webfont --save-dev
Note that if ttfautohint is not available in your distribution, your generated font will not be properly hinted.
Add somewhere in your Gruntfile.js:
grunt.loadNpmTasks('grunt-webfont');Inside your Gruntfile.js file add a section named webfont. See Parameters section below for details.
Type: string|array
Glyphs list: SVG or EPS. String or array. Wildcards are supported.
Type: string
Directory for resulting files.
Type: string Default: dest value
Directory for resulting CSS files (if different than font directory).
Type: string Default: icons
Name of font and base name of font files.
Type: boolean Default: true
Append font file names with unique string to flush browser cache when you update your icons.
Type: string|array Default: 'font,icon'
List of styles to be added to CSS files: font (font-face declaration), icon (base .icon class), extra (extra stuff for Bootstrap (only for syntax = 'bootstrap').
Type: string|array Default: 'eot,woff,ttf'
Font files types to generate.
Type: string|array Default: 'eot,woff,ttf,svg'
Order of @font-face’s src values in CSS file.
Type: string Default: bem
Icon classes syntax. bem for double class names: icon icon_awesome or bootstrap for single class names: icon-awesome.
Type: string Default: null
Custom CSS template path (see tasks/templates for some examples). Should be used instead of syntax. (You probably need to define htmlDemoTemplate option too.)
Template is a pair of CSS and JSON files with the same name.
For example, your Gruntfile:
options: {
template: 'my_templates/tmpl.css'
}my_templates/tmpl.css:
@font-face {
font-family:"<%= fontBaseName %>";
...
}
...my_templates/tmpl.json:
{
"baseClass": "icon",
"classPrefix": "icon_"
}Type: object Default: {}
Extends/overrides CSS template or syntax’s JSON file. Allows custom class names in default css templates.
options: {
templateOptions: {
baseClass: 'glyph-icon',
classPrefix: 'glyph_',
mixinPrefix: 'glyph-'
}
}Type: string Default: 'css'
Stylesheet type. Can be css, sass, scss, less... If sass or scss is used, _ will prefix the file (so it can be a used as a partial).
Type: string Default: null
Custom font path. Will be used instead of destCss in CSS file. Useful with CSS preprocessors.
Type: boolean Default: true
If true, an HTML file will be available (by default, in destCSS folder) to test the render.
Type: string Default: null
Custom demo HTML template path (see tasks/templates/demo.html for an example) (requires htmlDemo option to be true).
Type: string Default: destCss value
Custom demo HTML demo path (requires htmlDemo option to be true).
Type: string|array Default: false
If true embeds WOFF (only WOFF) file as data:uri.
IF ttf or woff or ttf,woff embeds TTF or/and WOFF file.
If there’re more file types in types option they will be included as usual url(font.type) CSS links.
Type: boolean Default: false
If true the generated font files and stylesheets will be generated with opentype ligature features. The character sequences to be replaced by the ligatures are determined by the file name (without extension) of the original SVG or EPS.
For example, you have a heart icon in love.svg file. The HTML <h1>I <span class="ligature-icons">love</span> you!</h1> will be rendered as I ♥ you!.
Type: function Default: path.basename
You can use this function to change how file names translates to class names (the part after icon_ or icon-). By default it’s a name of a file.
For example you can group your icons into several folders and add folder name to class name:
options: {
rename: function(name) {
// .icon_entypo-add, .icon_fontawesome-add, etc.
return [path.basename(path.dirname(name)), path.basename(name)].join('-');
}
}Type: boolean Default: false
If true task will not be ran. In example, you can skip task on Windows (becase of difficult installation):
skip: require('os').platform() === 'win32'webfont: {
icons: {
src: 'icons/*.svg',
dest: 'build/fonts'
}
}webfont: {
icons: {
src: 'icons/*.svg',
dest: 'build/fonts',
destCss: 'build/fonts/css',
options: {
font: 'ponies'
}
}
}webfont: {
icons: {
src: 'icons/*.svg',
dest: 'build/fonts',
syntax: 'bem',
templateOptions: {
baseClass: 'glyph-icon',
classPrefix: 'glyph_',
mixinPrefix: 'glyph-'
}
}
}webfont: {
icons: {
src: 'icons/*.svg',
dest: 'build/fonts',
destCss: 'build/styles',
options: {
stylesheet: 'styl',
relativeFontPath: '/build/fonts'
}
}
}webfont: {
icons: {
src: 'icons/*.svg',
dest: 'build/fonts',
options: {
types: 'woff',
embed: true
}
}
}You can change CSS file syntax using stylesheet option (see above). It change file extension (so you can specify any) with some tweaks. Replace all comments with single line comments (which will be removed after compilation).
If stylesheet option is sass or scss, _ will prefix the file (so it can be a used as a partial).
If stylesheet option is less, regular CSS icon classes will be expanded with corresponding LESS mixins.
The LESS mixins then may be used like so:
.profile-button {
.icon-profile;
}The changelog can be found in the Changelog.md file.
The MIT License, see the included License.md file.