djencks commented on pull request #670: URL: https://github.com/apache/tomee/pull/670#issuecomment-657955889
Hi Willes, > On Jul 13, 2020, at 7:58 PM, Willes Reis <[email protected]> wrote: > > > Hi @cesarhernandezgt <https://github.com/cesarhernandezgt>, it's a pleasure. > > As @djencks <https://github.com/djencks> mentions, there was an Asciidoc fixes a couple of months ago. I didn't remember that by the time I wrote in this ticket the first time. My recommendation would be to check out the mailing list archives to get context about it. > > I took a search in mail archive about asciidoc and not found comments about this specific case, the rendering of tables from asciidoc syntax, but I am looking around yet. > About @djencks <https://github.com/djencks> mentions, I noticed the proposal to use the Antora as "toolset" to process documentation. Is this a goal or possibility as well? > > My initial goal was to see what it was like to convert an existing non-Antora site with documents already in asciidoc to Antora. What I discovered was a horrible mess, with the alleged asciidoc documents half converted from markdown with fairly bogus asciidoc syntax, enormous amounts of thoughtless duplication, large amounts of content with unknown source (that turned out to still be in markdown), and a build process that no one seemed to understand, with the possible exception of David Blevins. I found all the content, converted it to syntactically correct asciidoc, put it in Antora organization, and eliminated most of the duplication. I also posted pretty frequent updates on my progress, with previews of the Antora site. To me, the main benefit of Antora is that the organization of content it suggests makes it very easy to think logically about a documentation web site. I think I got all the content in the beginnings of a reasonable organization, enough to consider how to refine it. However, it’s useful to also make it look good and, when moving a site to Antora, perhaps to make the appearance similar. I didn’t start on this aspect. After asking whether avoiding some duplicated content was acceptable, I got so little community response that I went on to other projects. I still think that an Antora based site would be to TomEE’s advantage, and am willing to work on it some more, but I’d need some expression of community interest in the result. I learned what I wanted to from my work and don’t want to push something that’s not wanted. However, if you are interested in fixing the asciidoc in the existing site, it might be worthwhile to look into my work. I also hope that somehow the hidden sources I discovered and converted to asciidoc get put into whatever builds the website. thanks David Jencks > As for the spring-integration demo, I would suggest working that on a separate ticket and therefore a separate PR. > Usually, when I have increased the scope of a ticket it also increases the complexity of communication, feedback, and therefore review. Also, I recall hearing on another email thread about the spring demo [1], so maybe that is already a work in progress, feel free to check on the mailings list and join that email thread if it's related, ask if there is some clarification need it, we are happy to help. > > [1] https://openejb.markmail.org/thread/mswam5jyitfes5v6 <https://openejb.markmail.org/thread/mswam5jyitfes5v6> > About this, I started a mail thread [2] some days ago, on which is possible understand the why to bring this project. We could say that carry the spring-integration project was a consequence, not a goal. > > [2] http://markmail.org/message/vitlaunuq26gp2fy <http://markmail.org/message/vitlaunuq26gp2fy> > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub <https://github.com/apache/tomee/pull/670#issuecomment-657937078>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAELDXXLCNVIQHANVLENBKLR3PCVXANCNFSM4OSMJSOQ>. > ---------------------------------------------------------------- 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]
