You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 71 Next »

This is an informal list of suggested improvements to the Tapestry 5 site documentation – things to work on soon. Most of these have come from users on the Tapestry Users mailing list.

Error formatting macro: contentbylabel: com.atlassian.confluence.api.service.exceptions.BadRequestException: Could not parse cql : null

These are merely suggestions from Tapestry users. Some might be bad ideas. Consider carefully which of these ought to be done and how, and start a discussion on the dev mailing list about any change that could be controversial.

9%

Task List

  1. handler

    Need more cross-linking between the wiki pages, especially between FAQ pages, User Guide pages, Cheat Sheet pages and Cookbook pages that cover the same topic.

    Priority HIGH
    N/A
  2. handler

    Component Cheat Sheet should have, for each of the listed annotations, a link to the corresponding API page.

    Priority MEDIUM
    N/A
  3. handler

    Some pages don't link to all of their child pages

    Priority MEDIUM
    N/A
  4. handler

    Move some of the best MoinMoin wiki content into Confluence?

    Priority MEDIUM
    N/A
  5. handler

    Need an article on clustering & high availability, then link to it from the clustering sections of Persistent Page Data, IoC - serialization, Persistent State, [Securing your application with HTTPS], and other pages that mention clustering

    Priority MEDIUM
    Nov 27, 2010
  6. handler

    Need a "Support" page that lists support options. This is where the mailing lists should be mentioned., as well as Howard's trainig, etc

    Priority MEDIUM
    Nov 27, 2010
  7. handler

    The links to "Tapestry Home" in the breadcrums on pages like Tutorial link to the "Home" page but should link to the index.html page

    Priority MEDIUM
    Nov 27, 2010
  8. handler

    Make it more obvious how to contribute to documentation improvements

    Priority MEDIUM
    Nov 27, 2010
  9. handler

    Add to Community Contributions page a link to http://lombok.demon.co.uk/tapestry5Demo/

    Priority MEDIUM
    Nov 27, 2010
  10. handler

    in the "create your first tapestry project" tutorial, don't make the user choose an archetype or a tapestry version. Write the instructions for the latest stable version. It's better to have that be out of date when a new version comes out (because it still will work) than have the user decide at this stage. Same for the groupId, artifactId, version and package. It's a test project the user is creating, those values are not going to matter. Give the defaults so people can copy and paste the command and have the project created, built and run.

    Priority MEDIUM
    javier@anatomicsoft.com
    Nov 27, 2010
  11. handler

    After the test project has been created, give the user some pointers on where to find things (pages go in src/main/java/com/example/pages, page templates go in webapp). Although there is a link to the tutorial, if this first experience is too frustrating, people might not even bother to go there.

    Priority MEDIUM
    javier@anatomicsoft.com
    Nov 27, 2010
  12. handler

    add something to the archetype with commented out code that the user can uncomment and see something cool happen. It has to be a few lines only, to be easily understandable, and clearly link components in the template with their methods in the page class.

    Priority MEDIUM
    Nov 27, 2010
  13. handler

    the tapestry tutorial starts unnecessarily verbose about topics not really related to me getting code running and out the door. Strip it to the essentials. If you want to mention Struts and the Servlet API compared to the tapestry way, mention them in a separate chapter so they are easy to find / skip as needed.

    Priority MEDIUM
    Nov 27, 2010
  14. handler

    there is no table of contents for the tutorial and no indication of how long it takes to complete

    Priority MEDIUM
    Nov 27, 2010
  15. handler

    There are too many callouts, warnings and decorations in the tutorial. It is very distracting visually and that makes it hard to follow. It's impossible to scan the pages to get a feel for what you've got ahead of you.

    Priority MEDIUM
    Nov 27, 2010
  16. handler

    Add a page about testing your Tapestry app (not just testing of pages)

    Priority MEDIUM
    Nov 27, 2010
  17. handler

    On the ComponentCheetSheet, add a sentance or two more on each annotation would be great.

    Priority MEDIUM
    Nov 27, 2010
  18. handler

    The tutorial Setting up your environment should be improved. Alternatives should be described on how to run T5 apps in the Eclipse or other IDEs, but not in the text as that would make it too long. I think there should be links for alternative setups - like how to run the T5 app from a main class and even start VisualVM for early debugging and optimizing (each alternative has pros and cons). There is no mention of m2eclipse plugin. Of course one can use JDK 6 also - only 1.5 is there. There is a sentence: "You should not have to download this directly". Why are then download links on the download page and no mention of maven at the same time. It is confusing for newbs.

    Priority MEDIUM
    Nov 27, 2010
  19. handler

    Add a link to JIRA in the About page

    Priority MEDIUM
    Nov 27, 2010
  20. handler

    Create a [Deployment Notes] page. The Documentation page already links to this non-existent page.

    Priority MEDIUM
    bobharner
    Nov 27, 2010
  21. handler

    Resolve the TODO at the bottom of Component Classes ("May want a more complex check; what if user uses prop: in the template and there's a conflict?")

    Priority MEDIUM
    Nov 28, 2010
  • No labels