> On Aug 4, 2020, at 11:55 PM, David Jencks <[email protected]> wrote: > > I updated the navigation in the preview to include all the common pages (most > of which are from apache CMS and previously hard to find) and the doc pages > to more closely match the existing sections. > > https://tomee-preview.s3-us-west-2.amazonaws.com/index.html > > There are some pages I used to help generate the navigation that will be > useful until things stabilize a bit more. > > This isn’t perfect but I think it’s in a state where it could replace the > current site, with the exception of examples and javadoc.
It's definitely a large step forward. I think there needs to be some TomEE 9 presence even if the docs are a 100% copy of 8 -- i.e. you point Antora at the same place as where 8 docs are getting pulled, but publish it as 9. Ultimately I just did a very surgical javax-to-jakarta rename on the 8 docs to turn them into 9. Would any of these be an option we could employ? - post-processing: perform some final edits to the Antora-generated html pages before they are committed to git - pre-processing: supply a non-git source for TomEE 9 asciidoc files (perhaps a zip) so we ourselves can clone/edit them and hand them to Antora - hooks: does Antora have any way to allow us to hook in so we can do our own prep before the generation happens? > I think that the apache git website deploy system allows a preview site, so i > may investigate and see if I can get that set up. The Apache CMS has staging built into it (it's not great for a site of our size). I asked about similar capabilities in the git-based publishing that is there now and I swear there was something that allowed you to create branches, but I have to go back and read those emails. -David
smime.p7s
Description: S/MIME cryptographic signature
