Thanks Matt. So right now I was looking at a theme enhancement to provide more options for the color scheme of the site. Like I said, I'd prefer not to alter the code base, but just drop in a specific component that can import the script/css and work within the existing framework from there. My thanks again for the information.
take care, --alex On Mon, Nov 6, 2017 at 8:52 AM, Matt Gilman <[email protected]> wrote: > The only supported front end extension points are for custom processor UIs > and data viewers (for viewing content of a flowfile in a queue or content > associated with a provenance event). Typically, when front-end capabilities > are added, a JIRA is filed so that some of UX focused community members can > offer suggestions. Because of this, there are no generic means for adding > stuff to the UI. What sort of functionality are you looking to add? > > Matt > > On Mon, Nov 6, 2017 at 8:14 AM, Alex Aversa <[email protected]> wrote: > > > Hello, > > > > I am trying to determine the best practice to inject my own custom UI > > components to the main NiFi user interface (not just custom processor > > UI's) without having to modify the Apache Nifi code base. I was hoping > > there was a property available in the nifi.properties file that could > point > > to a directory containing a custom package.json and corresponding > component > > files that would allow front end developers to inject their custom web > > components into the main NiFi user interface. Is this something that is > > supported, or is there a better practice available to address adding > custom > > components into main user interface aside from having to fork the code > > base? My thanks in advance for any information you can provide. > > > > Take care, > > > > Alex > > >
