camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrea Cosentino <ancosen1...@yahoo.com.INVALID>
Subject Re: gitbook based doc generation
Date Wed, 29 Jun 2016 13:49:55 GMT
Maybe it's a good idea to use a list, we can avoid the tables scrolling problem in this way.

>From the other side the readability can be difficult when you have components/endpoints
with a lot of options.

What do you think, guys?
 --
Andrea Cosentino 
----------------------------------
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1985@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Wednesday, June 29, 2016 12:04 PM, arno noordover <anoordover@gmail.com> wrote:
When you search for best-practices for ascii-doc people say that you should
only use tables for data that needs to be presented as a table.
Based on this best-practice I would like to propose some kind of "list"
presentation for the configurations.
I have post my result on  http://www.noordover.net/ssh.html
<http://www.noordover.net/ssh.html>  .
Please provide comments on the way we should implement this.

If this is the way forward we must also find a solution for the
endpoint-configuration containing the groups.
I think we should present the configurations grouped by "group".
Does anybody know how this is done in mvel?



--
View this message in context: http://camel.465427.n5.nabble.com/gitbook-based-doc-generation-tp5776497p5784543.html
Sent from the Camel Development mailing list archive at Nabble.com.

Mime
View raw message