Page History

...

Vítor Souza's Suggestions

Documentation:

One-paragraph description of what is WebWork. And then, an explanation of how the documentation is divided:

"If you're new to WebWork, please read the OVERVIEW Overview and proceed to the TUTORIAL Tutorial to get started. Experienced users can refer to the COOKBOOK Cookbook for advanced topics. WebWork users can use the REFERENCE Use the Reference on an as-needed basis for more specific details. For detailed information about WebWork project, read the section Project Information. Information about many projects related to WebWork can be found in Related Projects

If you have any questions, you can ask them at the user forum/mailing list. Please be sure to read the FAQ before asking any questions."

1. Overview
2. Project Information
3. FAQ
4. Tutorial
5. Cookbook
6. Reference
7. Related Projects

(details on each of the above follows)

Overview

1. What is WebWork
2. Comparison to Struts (Tapestry, VRaptor, JSF, etc.?)
3. WebWork community
   • Mailing lists / Forum
   • Bug tracker
   • Wiki
   • How to contribute?
4. Articles and press about WebWork
5. Projects using WebWork / Testimonials

Project Information

1. License
2. Deployment notes
3. WebWork versions
   • Current release
   • Previous releases
   • Migrating from WebWork 1.x;
   • Dependencies

FAQ

1. Category 1
2. Category 2
3. Etc.

Tutorial

I still need to think some more about this.

Cookbook

1. Tips and tricks on Application Servers (this was in "Overview")
2. Accessing application, session and request objects;
3. How to format dates and numbers;
4. Other stuff from the Cookbook...

All the tips in the Cookbook should be revised. Some of them could belong to the tutorial instead (basic stuff). 3rd party integration tips could be separated from the rest. Also, it would be good if all of them also followed the same structure, kind of like a tutorial lesson, but on advanced topics.

Reference

I like Jay Bose's reference TOC (below). On top of it, I'd suggest:

Remove "What is WebWork" and "Getting Started/Deployment Notes";

Replace them with "Introduction", in which there would be instructions to read the Overview first and proceed to the tutorial if the reader wants to get started;

Append "/ Dependency Injection" to "IoC", because some people may know it only by the name "Dependency Injection";

Group "JSP & Velocity Tags" with "WebWork Freemarker Support" to create a single section that contains everything related to user interface (in subsections)Will finish this later...;

"JSP Expression Language Comparison with WebWork 1.x" should be in "Migrating from WebWork 1.x", in the "Project Information" section;

Add to that same UI topic: JavaScript validation and DWR support (is this in 2.2?);

WebFlow would be in "Related Projects";

Have "3rd Party Integration" be links to Cookbook pages that explain how to integrate with SiteMesh, Spring, Pico, Hibernate, JUnit, Quartz, etc.

Related Projects

1. WebFlow (graphical chart tool)
2. EclipseWork (Eclipse Plugin)
3. IDEA Plugin
4. WebWork Optional
5. Etc. ?

Jay Bose's Suggestions

Suggested standalone documents (that may be viewed as single html, multiple html chapters, or PDF):

...