Ignition Exchange

Ignition claims to be a global SCADA/IIoT platform, yet it still lacks native multi-language interface support. Forcing customers to manually maintain translations through Translation Manager is inefficient and unacceptable. We demand official built-in language packs (Spanish, Chinese, German, French, etc.) with runtime switching across all modules (Designer, Vision, Perspective, Gateway, Alarms, Reports). This is a mandatory requirement for global usability and competitiveness. Provide a clear roadmap and timeline for implementation.

Furthermore, when I then try to install Ignition on my personal computer (using my school account), it asks me to fill out a free trial form. So it looks like I need to first set up my Educational License, because the free trial version expires before I can complete training.

I was given all the offical data for the license but cannot find the URL where I can set this up.

It would be very helpful to have a built-in rating system for resources on the Ignition Exchange. This could include a 5-star rating and an optional written review from users who’ve downloaded and used the resource. It would allow the community to easily identify which resources are reliable, useful, and high-quality. This system could help surface the best tools and encourage more engagement and feedback.

Ignition Exchange is incredible and after filtering for the specific resources you are after, the filter is lost if you navigate to said resource and then back.

Google calendar (or icloud calendar) widget to add to some of the dashboard views.

When viewing a resource on Ignition Exchange, one can see an underlined 'By: <author>' and the underline should mean that it is a clickable link, but its not. Please add the ability to see all resources provided buy a specific author or team.

Many times, I see a resource in the exchange, that is nice, but when I use it, I tend to upgrade it/make it better first. I'd like an option where I could do a pull request on the exchange resource, so it can be iterated. I think this will make the resources on the exchange way more high quality.

We want the ability to be able to change the visibility (scope) of resources from public to private, and vice-versa.

It's currently possible to host an Exchange resource on an open-source repository like Github, but it's not an ideal experience, because there's no way to hook up "continuous delivery", so that updates to the repo are automatically published to the Exchange resource. If a REST-ful API were exposed and documented, you could use a tool like Github Actions to easily push changes from Github to the Exchange on demand.