Hi Nicola, On Thu, Dec 13, 2018 at 10:19 AM Nicola Ferraro <[email protected]> wrote: > > I've started to refactor current Camel K doc for Antora. Results are > promising, I've rendered them in a temporary site > https://www.nicolaferraro.me/website-experiments/. > Website is rendered from [1] using the Antora default template, so I think > it would look nicer with the official Camel template.
The current template in the `camel-website` git repostory[1] is really basic adaptation of the default theme, I'll polish it a bit more, at least by using the color palette from the logo and adding the logo in the top navigation bar. But this is something I'd like to see contributions from someone with design skills. The Hugo theme there is also super basic (well, just a header and a footer right now), but it loads the Camel Antora UI theme, so any changes to that will reflect both in the documentation and in the other website pages. > The only issue I've found so far is about links. I've used > xref:module/thefile.adoc to add cross links between pages, but this way > it's no more possible to navigate the adoc pages on github in [2]. Yeah, I've noticed that also, I think this is one of the core principles of Antora and it's one that we have to adopt to on our end. But it also has the great opportunity to link to pages between modules, so a page from Camel-K can easily point to a page in the user manual or component reference without knowing the exact URL or path in the directory structure to it. > That is fine, but this means we'll switch to Antora-based doc in Camel K > only when the staging site is available (so we can point users to that from > the README). Cool :) I'm seeing some permission issues as I run the node/antora/yarn/hugo within a Docker container on the build server. Hope to get that sorted soon. > Wdyt? Awesome work, glad it works on Camel in the clouds also :) zoran [1] https://github.com/apache/camel-website/tree/master/antora-ui-camel -- Zoran Regvart
