My understanding of the component doc generation process is that * Something partially generates the component .adoc files from javascript, in the component maven project; these are checked into git somehow * gulp is configured to find and copy all these .adoc files to a central location, and they are checked into git there. * something (gulp?) generates the component nav.adoc file * something runs Antora.
There are a couple of Antora issues suggesting that non-standard source layouts could be useful, and I’m wondering if collecting documentation out of multiple maven projects might be one such case. To see what was possible and easy I wrote some code… #520 <https://gitlab.com/antora/antora/issues/520> As it is today, the “copy to a central location” step could be replaced by a (presumably generated) components/antora.yml configuration like source_map camel-activemq/src/main/docs: modules/components/pages … (one line for each component) Does having an Antora capability like this seem at all useful, or is the current “copy and check in” approach better? What’s there now is just what I thought of first and was easy to implement, no doubt many improvements are possible. Thanks for any comments, David Jencks
