I'm not strongly opinionated on the tools to actually generate the content. In terms of the organization of the content, I've never quite felt it we had right. I know there's been user vs developer and version vs not-version discussions in the past.
I quite like the idea of the guide Gilberto has suggested below. If we followed that route, I'd still like to see it specific to a TomEE version. If it enabled us to provide a complete PDF for offline reading as well, that would be amazing. We probably have the content to produce a guide, but it would need some re-arranging from what's there I would imagine. Jon On Wed, Feb 19, 2020 at 1:24 PM gilbertoca <[email protected]> wrote: > David Blevins-2 wrote > > There's an entire facet of this discussion we probably should be talking > > about which is how to deal with our heaps of content in various states of > > health; how did it get unhealthy, how do we deal with it, how do we > > prevent it, how do we encourage more contribution to main docs. > > > > I think any tool in the hands of someone willing to lead an effort to > > improve our main docs is a good tool. > > > > -David > > We could follow (again) apache friends and others [1] condensing all > relevant content in something like a User Guide or Reference Guide - that > would help the Maintenance and contribution. This organization can reduce > the tooling and it easy integrate(asciidoctor-maven-plugin?) in build > system[2]. > > [1] > https://netbeans.apache.org/kb/docs/java/index.html > https://ci.apache.org/projects/wicket/guide/8.x/single.html > https://beanvalidation.org/2.0/spec/ > https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html > https://shiro.apache.org/reference.html > > [2] https://asciidoctor.org/docs/asciidoctor-maven-plugin/ > > Regards, > > Gilberto > > > > -- > Sent from: > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html >
