I’ve fixed all the broken links from components v 2 and 3 and moved data formats into a module under components. I have yet to work on eips as a separate component. Does anyone else have an opinion on this?
If this work is going to be accepted and merged into master, I’d prefer it happen soon. I see some doc updates happening and would rather deal with as few of them as reasonably practical. FWIW there are a few errors from other components building the site: asciidoctor: WARNING: contributor-guide.adoc: line 123: invalid style for listing block: code asciidoctor: WARNING: native-mode.adoc: line 11: invalid style for listing block: code asciidoctor: WARNING: native-mode.adoc: line 20: invalid style for listing block: code asciidoctor: WARNING: skipping reference to missing attribute: camel-version asciidoctor: WARNING: skipping reference to missing attribute: server-name asciidoctor: WARNING: skipping reference to missing attribute: database-name asciidoctor: WARNING: skipping reference to missing attribute: table-name asciidoctor: WARNING: skipping reference to missing attribute: server-name asciidoctor: WARNING: skipping reference to missing attribute: database-name asciidoctor: WARNING: skipping reference to missing attribute: table-name asciidoctor: WARNING: skipping reference to missing attribute: server-name asciidoctor: WARNING: skipping reference to missing attribute: database-name asciidoctor: WARNING: skipping reference to missing attribute: table-name asciidoctor: WARNING: skipping reference to missing attribute: server-name asciidoctor: WARNING: skipping reference to missing attribute: database-name asciidoctor: WARNING: skipping reference to missing attribute: table-name The first three are in camel-quarkus. I haven’t found the others. Thanks David Jencks > On Mar 13, 2020, at 2:27 AM, Zoran Regvart <zo...@regvart.com> wrote: > > Hi David, > I'll just quickly focus on the questions > > On Fri, Mar 13, 2020 at 3:03 AM David Jencks <david.a.jen...@gmail.com> wrote: >> - Should the dataformats be split into a components module? > > I think that makes sense, we only publish the `latest` of user manual, > and we build versioned `components` and we add or change data formats > with new versions. > >> - There are several eip related pages in the “main” user manual, such as >> `enterprise-integration-patterns.adoc`. Would these be better logically >> moved to the rest of the eip pages in the eips module? If so I think it >> would make the most sense to move the source to the core/camel-core-engine >> with the partially generated pages, although it would work equally well from >> Antora’s standpoint to leave them in docs/user-manual and just change the >> module. >> - Would it even make sense to have the eip pages in a separate component? > > Also makes sense, we also change/add EIPs (not as often as components) > so putting all the relevant EIP documentation together allows us to > version. > > zoran > -- > Zoran Regvart
