djencks commented on pull request #537: URL: https://github.com/apache/camel-website/pull/537#issuecomment-778362927
I have decidedly mixed feelings about this. My original point was simply that if the UI is made available to builds separate from the website build, it’s worth considering the latest way to do it, which happens to only work on GitHub at this point, rather than using the really problematical way the Antora default UI is “distributed” as an unstable snapshot. Some points in favor of a versioned UI, independent of the website playbook project or content repos: * It allows going back to a "known good state" of the UI to build the production website or comparing UI versions without dealing with git branches or rollbacks. * Each content repo could have a "local playbook" that builds that source, using whatever UI version is desired. * Better separation of concerns (although this is questionable, since not all the site is built by Antora) Against: * Involves some "legal" questions, although I'm confident they could be resolved to allow this in some way. * Might be more complicated. * (AFAIK) puts the Antora UI in a different repo than the non-Antora UI, or at least puts it on a different timeline. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
