Hi Hiram Thanks for experimenting with this.
Better documentation and ... website is something I would love to see happen. All the hard work we have done with making Camel components "self documenting" plays a part here, as we should be able to auto generate part of the documentation, such as all the component / endpoint options. And in addition the EIPs, languages, and data formats. Also we know if an endpoint options is only to be used on the consumer side or the producer etc. For example the file component has a lot of options, but we can make a website, where the user can see the options grouped nicely. Or even make the website a bit more interactive so the user can click "consumer" and only see the options relevant for that. On Thu, Jan 21, 2016 at 4:29 PM, Hiram Chirino <hi...@hiramchirino.com> wrote: > Hi folks, > > The artemis project has been using a gitbook based tool chain to > generate their docs from project source that seems kinda cool. I know > a while back we discussed moving more of our docs out of confluence > and have it versioned with the project source code. So a first step > toward that goal, I'm going to replicate that gitbook toolchain setup > in the camel project > > Next step after that would be figuring out a good conversion/migration > plan for the actual content. > > Expect that to show up soon. > > -- > Hiram Chirino > Engineering | Red Hat, Inc. > hchir...@redhat.com | fusesource.com | redhat.com > skype: hiramchirino | twitter: @hiramchirino -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
