The new UI has progressed quite well and I agree with this stance. However, with 2.0 getting close, one could argue that new UI features should definitely land in the new UI but only really need to land in the original UI if desired or to support backward compatibility.
--Rob On Tue, Apr 23, 2024 at 7:55 PM Scott Aslan <scottyas...@gmail.com> wrote: > Thanks for sending this out Matt! I agree that at this point any new > features to the frontend should be implemented in both the new and the > existing UI. Updating the contributions guidelines seems appropriate as > well. > > -Scott > > On Tue, Apr 23, 2024 at 4:07 PM Matt Gilman <mcgil...@apache.org> wrote: > > > Team, > > > > Substantial progress has been made on modernizing the NiFi UI under [1] > and > > [2]. As detailed in the JIRAs, this effort has been largely motivated by > > moving away from deprecated and unsupported dependencies. As we begin the > > process to transition to the new UI, we are at a point where any UI > > contributions should target both the new UI and the existing UI. We've > > updated the PR template detailing this and the README for the new UI [3] > to > > help introduce folks making UI contributions to the layout of the > > repository. It discusses the steps needed to build NiFi with the new UI > > included and how to access it. > > > > Happy to discuss any questions folks may have. > > > > Matt > > > > [1] https://issues.apache.org/jira/browse/NIFI-11481 > > [2] https://issues.apache.org/jira/browse/NIFI-12400 > > [3] https://github.com/apache/nifi/pull/8693 > > > -- ------------------------------- Rob Fellows
