**[ This description is mirrored from README.md at [github.com/arsnebula/nebula-icons](https://github.com//arsnebula/nebula-icons/blob/v2.0.1/README.md) on 2019-05-22 ]** [](https://www.webcomponents.org/element/arsnebula/nebula-icons) [](https://www.polymer-project.org) [](https://saucelabs.com/beta/builds/aa51c233627249d78e2d5e6d46ecf8cb) [](https://gitter.im/arsnebula/webcomponents) [](https://www.patreon.com/arsnebula) # \ Share SVG icons resources between custom elements. - Compatible with [Polymer Custom Iconset Generator](https://poly-icon.appspot.com) - Define custom iconsets and share them between custom elements - SVG tags are rendered into Light DOM for easy styling ## Installation ```sh $ bower install -S arsnebula/nebula-icons ``` ## Usage Import the element. ```html ``` Define your iconsets once, anywhere in your application. Each iconset is defined by a unique name. ```html ``` Render icons anywhere in your application. Icons are accessed with a compount key formatted as `[iconset]:[id]`. ```html ``` Style the icon using CSS variables or standard CSS properties. ```css ``` *For more information see the API Reference documentation.* ## Contributing We welcome and appreciate feedback from the community. Here are a few ways that you can show your appreciation for this package: * Give us a **Star on GitHub** from either [webcomponents.org](https://www.webcomponents.org/element/arsnebula/nebula-element-mixin) or directly on [GitHub](https://github.com/arsnebula/nebula-element-mixin). * Submit a feature request, or a defect report on the [Issues List](https://www.webcomponents.org/element/arsnebula/nebula-element-mixin/issues). * Become a [Patreon](https://www.patreon.com/arsnebula). It takes a lot of time and effort to develop, document, test and support the elements in our [Nebula Essentials](https://www.webcomponents.org/collection/arsnebula/nebula-essentials) collection. Your financial contribution will help ensure that our entire collection continues to grow and improve. If you are a developer, and are interested in making a code contribution, consider opening an issue first to describe the change, and discuss with the core repository maintainers. Once you are ready, prepare a pull request: 1. Fork it! 2. Create your feature branch: `git checkout -b my-new-feature` 3. Commit your changes: `git commit -am 'Add some feature'` 4. Push to the branch: `git push origin my-new-feature` 5. Submit a pull request :D ## Change Log See [CHANGELOG](/CHANGELOG.md) ## License See [LICENSE](/LICENSE.md)