User personalization should be covered, but maybe more valuable would be basic portal customization. (Exemple: How do i change the logo, header or footer, not something that leads to recreate a whole theme but something simple). It should also point to the reference guide for "advanced" customization. The new wizard should be there but probably not replace the manual process since you cannot pick a CMS content or Google widget yet. The risk of "bloating" is real, we should be able to add content and still define some kind of path through it (by skipping some sections). Maybe by having a "pre-required chapters" section on each chapter. Security is missing from the doc, we should explain how to restrict access to a page or window. So here is an idea that i through away. Maybe we should reorganize the doco as a set of tutorials (with some chapters 'dependencies') each tutorial would have a clearly defined goal that makes sense as a whole (creating an instance is not end-user oriented, adding a window on a page is). Each tutorial could end with a section explaining how to go from that little step to something wider. (If you know how to secure a page, you know how to secure a portal) Exemple: - Tutorial 0: Basic concepts - Tutorial 1: Adding a window on a page Pre-requisite: Tutorial 0 - Tutorial 2: Deploying a new portlet Pre-requisite: Tutorial 0 Pre-requisite: Tutorial 1 - Tutorial 3: Securing a page Pre-requisite: Tutorial 0 - Tutorial 4: Changing the header and footer Pre-requisite: Tutorial 0 - Tutorial 5: Managing users and roles Pre-requisite: Tutorial 0 - Tutorial 6: ... I'm not sure myself if it is a good idea. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060100#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...