Hi

For the docs/website, then I think camel-spring-boot should be similar
to camel-quarkus, where Spring Boot would be listed under "projects"
on the website.

And for camel-quarkus we have a tool that generates the list of
components, and its documentation.
https://github.com/apache/camel-quarkus/tree/master/tooling/package-maven-plugin
https://github.com/apache/camel-quarkus/blob/master/docs/modules/ROOT/pages/list-of-camel-quarkus-extensions.adoc

We could have that too for camel-spring-boot. And for the component
documentation with the extra information about spring-boot
auto-configuration, then we could maybe

- keep it as-is (and find a way for camel-spring-boot to update on
camel main project) maybe via some script or java/maven tool

or

- copy over the existing documentation from the camel releases (you
can find the adoc files in the camel-catalog JAR).
- remove the spring-boot auto-configuration from the camel documentation
- add the spring boot auto-configuration section in the camel-spring-boot tool

or

- remove all the auto-configuration documentation all together, they
are almost identical to the component level options which is already
listed
- the options are generated in the -starter JARs and there are spring
tools that can do code assistances in editors




On Thu, Dec 12, 2019 at 7:39 PM Zoran Regvart <[email protected]> wrote:
>
> Hi Guillaume,
>
> On Thu, Dec 12, 2019 at 4:27 PM Guillaume Nodet <[email protected]> wrote:
> > On the web site side of things, I haven't paid a close attention to how the
> > web site is published.  The camel source tree has some content (
> > https://github.com/apache/camel/tree/master/docs), but how is that pushed
> > to the web site ? Same question for blogs actually ;-)
>
> Website build is described in the README[1] of the camel-website
> repository. We have a Jenkins job[2] that takes care of building it
> and publishing it to the `asf-site` branch from which it's pulled by
> INFRA to the web server.
>
> Parts of it are in Markdown (e.g blog) and published by Hugo,
> reference documentation is pulled from camel, camel-k and
> camel-quarkus repositories and built by Antora.
>
> Hope this helps, if anyone else misses this information I can add more
> on the build/publish process to the README,
>
> zoran
>
> [1] https://github.com/apache/camel-website/blob/master/README.md
> [2] https://builds.apache.org/job/Camel.website/
> --
> Zoran Regvart



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Reply via email to