This makes me wonder how documentation is going to work with the registry, should the documentation show all the nars that are in the registry and available or all the cars local? etc.
From: Pierre Villard <pierre.villard...@gmail.com> <pierre.villard...@gmail.com> Reply: dev@nifi.apache.org <dev@nifi.apache.org> <dev@nifi.apache.org> Date: November 9, 2021 at 18:17:30 To: dev@nifi.apache.org <dev@nifi.apache.org> <dev@nifi.apache.org> Subject: [DISCUSS] Docs from non packaged NARs Hi team, I'd like to discuss the possibility to change the release process we have for the next releases so that the documentation of all components we have in the repository are published as part of the release process. All of the documentation for components that are in specific profiles are not only skipped for the final convenience binary but also for the documentation. We have a tremendous amount of great components in this "by default excluded" NARs and it would be helpful to have the corresponding documentation to at least redirect users when we get some questions on the users mailing list. I feel like this should only be a release process thing but I could be wrong. Something that could be even better would be to enable all the profiles by default but only for nifi-docs module? Not sure if that is even a possibility. Thoughts? Thanks, Pierre
