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
Important: Updates to this repository are only required if you are targeting OpenShift console 3.6 or earlier. Starting in OpenShift 3.7, icons are mapped to and replaced with images (SVG, PNG, etc.), so there is no need to update this repo to add a new icon. For 3.7 - 3.11, see openshift/origin-web-console#3146 for an example of how to add a new icon as an image. For 4.1+, see openshift/console#2638.
Development dependencies are managed using NPM; therefore, NPM is required.
npm install
The font files are generated using IcoMoon.
Go to Manage Projects
Import the project selection.json and Load it:
To add new icons to the set, click on the right-hand kabob menu and select “Import To Set”.
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:
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):
- demo-files
- demo.html
- fonts
- selection.json
Update less/variables.less and less/openshift-logos-icon.less with your new icons.
Run a build.
Builds are done via Grunt.
grunt
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:
"version": "<new_version>"
Update the version listed in package.json by editing the file and changing the line:
"version": "<new_version>"
Commit the version bump:
git commit -a -m "Version bump to <new_version>"
Tag and push upstream (assuming you have commit access):
git tag <new_version>
git 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:
npm publish