+1 as long less effort has been made On Mon, 14 Oct 2019 at 11:02, Alex Dettinger <[email protected]> wrote:
> +1, it may even be clearer to users to have the whole list in a singe > place. > > Alex > > On Mon, Oct 14, 2019 at 10:41 AM Andrea Cosentino <[email protected]> > wrote: > > > +1, it's less effort in terms of maintaining. > > > > Il giorno lun 14 ott 2019 alle ore 10:39 Claus Ibsen < > > [email protected]> > > ha scritto: > > > > > Hi > > > > > > Before our new website, we were in a transition phase with the old > > > outdate wiki based website and then towards a new website. In that > > > phase we referred users to browse github directly for the up to date > > > documentation. > > > > > > The component list at > > > > > > > > > https://github.com/apache/camel/blob/master/components/readme.adoc#components > > > > > > Have direct links to each component docs in the source code with > > > relative folder paths. > > > > > > However now that we have a new website, then I wonder if we should > > > discontinue the pages on github, to keep maintenance lower, and avoid > > > duplicated effort. We can refer users to the website. > > > > > > We will continue to keep the component docs in the source code, > > > together with the component source, eg in the src/main/docs folder. As > > > we grab all of that when we build the website. > > > > > > So its more about reducing the documentation navigation and relative > > > links we have on github vs the new website. > > > > > > > > > > > > > > > > > > -- > > > Claus Ibsen > > > ----------------- > > > http://davsclaus.com @davsclaus > > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > >
