Hi The documentation is mainly viewed as static html, and there is a job that exports from wiki. And for that to work it has be be as before / simple.
Though in the future I would like to migrate documentation away from confluence wiki, and let the components be self documented and includes in the source code, eg for example readme.md files. And then there is a lot of tools that can generate pdf / epub / html from markdown / asciidoctor or whatnot. And .md files is already lovely to view using github, so ppl can browse Camel component documentation the usual github way. But there is still a long road ahead until that is done. On Thu, Dec 4, 2014 at 2:16 PM, Ruurtjan Pul <ruurt...@gmail.com> wrote: > Hi dev team, > > I've updated the documentation of one page so the example in java and xml > are shown in tabs in stead of below each other. This works in confluence, > but not on the main site: > https://cwiki.apache.org/confluence/display/CAMEL/Spark-rest > http://camel.apache.org/spark-rest.html > > The js and css files are not included on the site. Showing the same example > for different DSL's in tabs makes the documentation clearer in my opinion. > > Should we add the js and css files or should I revert the changes? > > Best, > Ruurtjan -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
