Hi, On Thu, Apr 10, 2014 at 1:18 PM, vincent(a)massol.net <vincent(a)massol.net>wrote;wrote: Not sure what this 'template provider feature' is but ideally the buttons should all be grouped together. The problem is that right now the code for the buttons is found in menuview.vm so this layout with customized buttons after the #document-title/#document-info is more of a limitation we currently have with our extensibility. IMO the solution to this problem would be to have an extension point for the menus that allows applications to insert their functionality inside the menus, but maybe you can explain a bit more about 'template provider'. So I gave an example with: * a small description http://design.xwiki.org/xwiki/bin/download/Proposal/ForumApplicationDesign/… * big description http://design.xwiki.org/xwiki/bin/download/Proposal/ForumApplicationDesign/… The current layout accomodate ok if there is no text/small/big text. The hierarchy is done through space indentation. I've discussed with Max about making it more prominent by using background-color, but in the end this looked ok. This proposal focused very much on what is already implemented (with very small modifications/improvements) so the visible textarea is currently how it is now implemented. Your remark is good and is consistent with the way we add Topics or Answer: the textarea appears only when you press the 'Add' button. As I said before this proposals covers the current implementation. The problem with the Forum Application is that it is called Forum, but the functionality is not the classical one. Another application we have, called Bulletin Board, is more close to the standard implementation of how forums work. A new feature for this Forum App would be to provide a new view on the Forum's homepage where topics can be listed also as livetable, not just this current 'list view'. Currently this application only has 'List view' and a 'Sort' functionality in order to narrow down the entries, see http://design.xwiki.org/xwiki/bin/download/Proposal/ForumApplicationDesign/… Another improvement for the 'List view' would be pagination. The current implementation doesn't list any description, just the name. IMO is better to have this summary like mechanism. * In our Blog application we have a different field where the user can customize it; * we could try to automatic crop it - problems with the html macro used in WYSIWYG since it could break the display; * in my prototype I put the actual description and cropped with CSS - not so good from maybe a performance point of view. We can see what is the best solution for this, but IMO is better to provide some 'context' and not just the title. So as I said this is already implemented. There is an automatically page naming mechanism that creates pages and objects for topic's answers. It is very hard to attach an attachment to a particular answer since they are generated, example: http://localhost:8080/xwiki/bin/view/Forums/Topic_4#.U0ZJ7q2SyLP http://localhost:8080/xwiki/bin/view/Forums/Topic_4#Topic4Answer_0 Since this is how it's done it's useless to try to put attachments to them since they will not correspond to this 'internal mapping' (I haven't studied the code in depth to know how this is really implemented). So the answer is that this is already implemented and I've removed confusing / not-working functionality. Is a 'feature'/'limitation' of the current implementation. Attachments can be added to an answer/comment by using the WYSIWYG Image functionality. Thank you for all your comments, Caty