Well, there's always the usual: * More examples - More tests * More diagrams
In addition... * Compliance tests - RFCs - Interoperability - Etc. * Benchmarks and various performance/scaling/etc. tests. Particularly important in both of those areas, IMHO, for restlet is how do the various HTTP connectors (AsyncWeb, Simple, Jetty, embedded Servlet...) compare to each other *as used by a restlet solution*. But wait! There's more... * More ammo (comparisons, testimonials, examples, etc.) of restlet solutons compared to other Java "frameworks" and solutions built in other languages+frameworks. Features, development time, better compliance, less bugs, better performance, etc. * The site needs to be able to show pretty much all of the docs, files, etc. for all of the released versions. I.e., People need to be able to get and read the docs, examples, etc. for v1.0.x for the next couple of years even after v1.1.x and 1.2.x and 2.0.x and... are released and active and retired. Hope this helps, John

