Big news for the web dev community! Ignite UI is now open source!

Ignite UI Team / Tuesday, October 25, 2016

For a while now, Ignite UI has been the choice for large enterprises to create beautiful and powerful modern web UIs on top of their enterprise data. To enrich the community, we're opening up the most powerful and easy-to-use UI framework for Modern Web Applications to everyone. That's right, we’ve made the majority of the line of business Ignite UI controls and components open source, and they're now available on GitHub for everyone! The open source part of Ignite UI is licensed under Apache 2.0.

As part of opening up Ignite UI, we’ve also created easy to grab NPM and Bower packages, and we’ve made the product fully AMD compliant. Just like any other open source project, Ignite UI is open to external contributions, provided that the contribution guidelines documented in our repository’s wiki page are being followed. The repository is still fully owned and maintained by the Ignite UI product team at Infragistics, so everyone is able to see how our own team contributes to the product. We’re also opening up our planning and tracking process: all of our plans are available on GitHub through the Issues and Projects tabs.

Open sourcing Ignite UI has been underway for quite some time now. We started by putting extensions for the product like the Ignite UI Angular and React extensions up on GitHub, then shared the native Angular 2 Ignite UI JS Blocks controls with the developer community.

Soon after, we moved all of the Ignite UI documentation topics, and now a large portion of the product.

The Ignite UI repository contains full information about what’s available in the open source version of the product. We wanted to empower individual developers and academia with a leading UI toolset, without having to pay for it, thus most of the product is available in the open source version.

The Ignite UI website has been updated to display which of the control samples can be built using the OSS package. Also, HTML versions of each sample are available in the GitHub repository, so you can clone, build and run each sample.

How can you contribute? Since everything related to the repository is public and visible through our repository issues, you can contribute by reporting issues, fixing and pull requesting, improving the test coverage, improving the API documentation. Checkout the repository for full information on how to do each of these!