Re: Unable to see custom processor documentation in 2.0.0...

The intent with the change from HTML to Markdown was to ensure that the developer producing the additional details didn't need to handle UI concerns like theming and appearance (light/dark/mode). The Markdown should be used to structure the content in a meaningful way. The UI takes that content and

Re: Unable to see custom processor documentation in 2.0.0...

I can now answer my postscript below, though some may wish to post caveats, warnings about bad practices, etc. which will be gladly received. The following seems to work in NiFi 1.28.1. This is /additionalDetails.html/ for a custom processor I wrote and it's accompanied in the usual (special)

Re: Unable to see custom processor documentation in 2.0.0...

I can answer at least one of your questions and that is no the NIFI UI will not necessarily display as how you see it in Intellij. Please see NIFI-14101 for more details. On Tue, Feb 25, 2025 at 12:55 PM Russell Bateman wrote: > Just getting bac

Re: Unable to see custom processor documentation in 2.0.0...

Just getting back to this now... The examples of markdown given by Matt [2, below] appear to exhibit font weight bold, styles, headings, bulleted and numbered lists. Is there a conscious "markdown flavor" that we can adhere to in composition or must we reduce /additionalDetails.html/ to the r

Re: Unable to see custom processor documentation in 2.0.0...

Russell, The additional details were migrated to markdown in NiFi 2.0.0. I've included a bullet point in the migration guidance for it [1]. You should just need to migrate the contents of additionalDetails.html to Markdown and update the file extension to .md. Here's an example from when the chang