Hi everybody, I think one of the biggest remaining shortcomings of the documentation is the component reference. The automated generation of the component reference is nice, but it has certain drawbacks.
For example, in the new documentation, the http://tapestry.apache.org/documentation.html page links to the Component Reference at http://tapestry.apache.org/tapestry5.2-dev/tapestry-core/ref/, but the latter is really part of the *old* documentation set. And once people follow links into it, they are "stuck" there, with plenty of navigation links to the old (non-Confluence) documentation but none back to the new (Confluence) documentation. Beyond this, I think the component reference documentation needs to be more browseable (e.g. related components grouped together) and it needs screen shots, more examples, links to other component libraries like Tapx and ChenilleKit, and maybe even an interactive demo for each visual component (should that be built into Hotel Booking? How do we make the component documentation better? Should each component have its own page in the User Guide, like already exists for BeanEditForm (http://tapestry.apache.org/beaneditform-guide.html)? Or is there some better approach? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
