Hi David On Tue, Aug 17, 2021 at 7:42 AM David Jencks <david.a.jen...@gmail.com> wrote: > > I’ve made a lot of progress on this and put up a preview of the current > state. Only components in the latest branch are done (not dataformats, eips, > languages, other, and not other versions).
Perhaps we can create (sub)issues for outstanding work so folk can jump in and help as well? > The arrangement of, in particular, API data didn’t make much sense to me so I > reorganized it so relevant information is all together, and added a lot of > in-page links. What sometimes bothered me is that I could not point someone to an exact option in the table, perhaps this is for another time but I think it would be good to have much more anchors within the page, one of those would be for each individual option. Perhaps as a follow up on this work. > There are a couple of glitches… > - “debugging code” showing e.g. "pascalcasescheme: Twilio” I'd assume this would be trivial to fix :) > - For some reason lists don’t display properly in the first row of tables. At > https://camel-preview-1.s3.us-west-2.amazonaws.com/components/latest/twilio-component.html#_path_parameters_2_parameters > compare the apiName row and the methodName row. > > https://camel-preview-1.s3.us-west-2.amazonaws.com/components/latest/twilio-component.html > is the most complex page, and can be compared to the current site at > https://camel.apache.org/components/latest/twilio-component.html. Yeah, we could also add the enum values inline, i.e. not in a list, perhaps within a <code> tag, not sure if it's worth spending too much of an effort on this. I'd create a follow up issue for this and any other cleanup tasks... > I haven’t published the updates needed to the Asciidoctor extension that does > the generation, so a PR is not yet feasible. Would love to see how this is shaping up, even if you have it somewhere in a draft phase it would be good to get familiar with the code. Perhaps we can create a branch on the camel-website and work on it from there? Would be easy (I think) to set up a preview via GitHub Workflow + Netlify or a Jenkins build and a staging site hosted by ASF... I've noticed that the Kamelet catalog is not rendering correctly (https://camel-preview-1.s3.us-west-2.amazonaws.com/camel-kamelets/latest/index.html), not sure if that's a CSS issue or it has something to do with the changes you're making. Thanks David for taking this on, looking forward to this, it should cut down a lot of the complexity in how we build the website and remove some of the work needed in the main camel repository. I can even see us not needing to do as many regen commits as an outcome of this! zoran -- Zoran Regvart
