openshift/openshift-logos-icon

Name: openshift-logos-icon

Owner: OpenShift

Description: OpenShift Logos Icon Font

Created: 2017-06-20 13:47:44.0

Updated: 2018-05-08 22:50:24.0

Pushed: 2018-04-23 15:01:46.0

Homepage: null

Size: 293

Language: HTML

GitHub Committers

UserMost Recent Commit# Commits

Other Committers

UserEmailMost Recent Commit# Commits

README

OpenShift Logos Icon Font

To view a list of all the glyphs in the font along with their codes/ligatures visit:

https://rawgit.com/openshift/openshift-logos-icon/master/demo.html

Contributing
Getting Started

Development dependencies are managed using NPM; therefore, NPM is required.

install
Modifying Font Files

The font files are generated using IcoMoon.

Go to Manage Projects

image

Import the project selection.json and Load it:

image

To add new icons to the set, click on the right-hand kabob menu and select ?Import To Set?.

image

Move the newly added icon(s) to the end of the list (by default, icomoon adds them to the beginning). This prevents the re-indexing of all icons, thus reducing the diff in selection.json.

Ensure the new icons you added are selected.

Generate the font files by clicking on the ?Generate Font? button at the bottom of the page:

image

In that same location, click on the ?Download? button. This will download a zip file. Expand the zip file and copy the following (overwriting your existing files):

Update less/variables.less and less/openshift-logos-icon.less with your new icons.

Run a build.

Building

Builds are done via Grunt.

t
Releasing

To release a new version version, edit bower.json and package.json accordingly.

Update the version listed in bower.json by editing the file and changing the line:

sion": "<new_version>"

Update the version listed in package.json by editing the file and changing the line:

sion": "<new_version>"

Commit the version bump:

commit -a -m "Version bump to <new_version>"

Tag and push upstream (assuming you have commit access):

tag <new_version>
push && git push --tags

The Bower package manager determines available versions and installs based upon git tags, so the new version will now be automatically available via Bower.

To publish a new version to npm, execute:

publish

This work is supported by the National Institutes of Health's National Center for Advancing Translational Sciences, Grant Number U24TR002306. This work is solely the responsibility of the creators and does not necessarily represent the official views of the National Institutes of Health.