For me, it would be easier to convert the pages to Markdown then write the css to make asciidoc work. I dislike working with css.
As for the description, I provided something but it isn’t particularly specific. I would have expected that if they were going to provide support for the Maven Site Plugin that they would have supplied a css file that makes the generated pages render properly. Without that the Maven Site Plugin isn’t really supported. Ralph > On Apr 29, 2019, at 11:25 AM, Gary Gregory <[email protected]> wrote: > > Based on the reply to my comment I just saw on the github page for the > issue, it seems like the developer is willing to help, we just need to > provide PRs or a description of what we'd like to change... > > Gary > > On Mon, Apr 29, 2019 at 12:48 PM Ralph Goers <[email protected]> > wrote: > >> The issue isn’t marked as fixed. The problem I am having is that tables >> are rendered without borders. This is because asciidoc doesn’t include its >> css file when building the site because the “normal” asciidoc css would >> break the site. Asciidoc generates tables with css class names to generate >> the borders and grids. According to the Jira issue other markup has the >> same issue. >> >> Ralph >> >>> On Apr 29, 2019, at 8:50 AM, Matt Sicker <[email protected]> wrote: >>> >>> I had converted them to asciidoc a while back because it provided more >>> syntactical features than markdown. Many of the files I converted >>> weren't markdown but xdoc. >>> >>> Also, there was a new asciidoctor release just the other day. Unsure >>> if it's related. >>> >>> On Mon, 29 Apr 2019 at 10:34, Ralph Goers <[email protected]> >> wrote: >>>> >>>> The master branch was converted to use AsciiDoctor. To be honest, I >> don’t remember why. But after trying to create a new page with it I >> discovered that AsciiDoctor simply doesn’t work properly with the Maven >> Site Plugin. See >> https://github.com/asciidoctor/asciidoctor-maven-plugin/issues/166 < >> https://github.com/asciidoctor/asciidoctor-maven-plugin/issues/166>. As >> such I believe the site documents in Master need to be converted back to >> Markdown. >>>> >>>> Ralph >>> >>> >>> >>> -- >>> Matt Sicker <[email protected]> >>> >> >> >>
