Part of this discussion is about how to organize the website. I was just pointed to this, which I think has a very nice description of different purposes for different documentation, no matter what technology is used for the site:
https://lisk.io/blog/announcement/lisk-documentation-migrated-asciidoc-and-antora David Jencks <snip my previous replies> > >> On Feb 19, 2020, at 5:24 AM, gilbertoca <gilbert...@gmail.com> 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 >
