Hi Anca, Some comments
1) I agree about making the home page a simple page to teach the first user (admin usually) the main concepts of the wiki and to let him customize it for his/her own need. I agree that we need to teach the user a few things, like using the include macro (this allows the user to make the home page be any of the existing page, includes pages from extensions he/she installed). Explaining how to create a Dashboard could be interesting too. 2a) If we implement 1) then we should modify the Dashboard so that it's oriented fully towards being a dashboard to show what's going on in the wiki. 2b) Alternatively to 2a) we could bundle a few more Dashboards by default in the Dashboard Application (say we have 2 by default) and make Dashboard.WebHome be some kind of AWM application that lists all Dashboard that exist in the wiki in a LiveTable with a button to create new Dashboards. This would allow to explain in 1) how to perform an include and then direct the user to 2b) to create a new Dashboard that can then be included. 2c) Alternatively to 2a) we could decide that the Dashboard application doesn't register itself in the App Panel and instead introduce a new whatsnew application with a "What's New" page (or rather reuse the existing Index Application and add a "What's New" page in it) and make it appear in the App Panel. 2d) We could also do 2b) + 2c), ie. have both "Dashboards" and "What's New" entries in the Application Panel 2e) Alternatively to 2c) or 2d), we could also have a What's New feature in the nav bar somewhere (possibly even both in the Wiki menu and in the Space menu for the wiki-level what's new and space-level what's new) WDYT? Thanks -Vincent On 17 Oct 2014 at 18:26:36, Anca Luca ([email protected](mailto:[email protected])) wrote: > Hello all, > > so on the topic of "removing the dashboard from the homepage" and if people > need it they can access it independently. > > In my opinion, this dashboard does not really exist or have any value > beyond the homepage. I mean, what does it mean, what is it used for besides > the homepage? What would the dashboard be used other than having an > overview of the wiki? And if people remove it from the homepage of the > wiki, what would they put instead? An overview of the wiki? Isn't that what > dashboard means? > > By this logic, I would find it strange to have a homepage and a dashboard, > as 2 separate entities, because for me they would mean the same thing. So > multiple possibilities: > 1/ our _default_ dashboard displayed on the homepage (included or not, I > don't care) is not good enough because it does not offer a good _default_ > overview of the wiki. We need to change the dashboard. In this case, we > improve the way we modify this dashboard, to allow people to change the > "default" overview which guides the user through the wiki with an overview > that is more adapted to the user's usecase. > 2/ we change the homepage and we remove the dashboard from it and implement > an overview of the wiki differently (which would still be a dashboard at > the conceptual level but implemented differently). In this case, the > Dashboard.WebHome should be removed completely from the menu, because the > dashboard _is_ the home page (see my remark above) :) . We can make the > homepage a regular page so that users can edit it very easily by default, > but we also allow them to easily make it a dashboard with gadgets and drag > & drop, so that they can organize their content. I am thinking for example > of a button on the homepage, in view mode injected with javascript or UI > extension or I don't know, which runs a script that creates a new version > of the homepage which contains a dashboard macro call and a default gadget > and the user is taken to the edit mode of the homepage, with the dashboard > editor in it. > > The only reason why the dashboard is separate now, in Dashboard.WebHome, is > for legacy reasons, because it used to be included as the homepage of all > sort of default spaces, so we needed something that can be re-used for > spaces homes as well. Otherwise, from my point of view, it does not need to > be a separate entity. I mean, one should be able to create as many > dashboards as they'd want (on any page they want), but by default the > dashboard of the wiki is only one, the homepage of the wiki. > > Anca > > On Tue, Sep 16, 2014 at 3:23 PM, [email protected] > wrote: > > > Hi devs, > > > > As you know I started working on a Home Page Application, see: > > - JIRA with screenshots: http://jira.xwiki.org/browse/XWIKI-10586 > > - Discussion thread: http://markmail.org/message/ghelufamwucog46x > > > > I have it all done locally but I refrained from committing it because on > > the email thread some expressed their doubts. > > > > I started thinking about it and I expressed some idea in the thread > > started by Caty about "Wiki - Space - Page concepts pitch": > > http://markmail.org/message/jefze7nvprz36pkw > > > > I’m pasting it here again for discussion (with some edits): > > > > " > > BTW concerning the home page, I’m more and more leaning towards removing > > the dashboard from it (it’s accessible from the App panel anyway) and > > instead have it contain: > > - explanation about how the wiki is organized (wikis, spaces, pages) > > - explanation about base concepts (editing, saving, etc) > > - encourage the user to edit this home page to make it his own and put the > > content he wishes instead > > > > I think this would solve the following issues: > > - users always want to customize the home page and this makes it easy > > (it’s a standard page, no dashboard). This is also a way for them to take > > ownership of the wiki as theirs. > > - explains the main concepts of wiki, space, page > > > > Of course, we also need to provide a navigation panel for easy navigation > > in the wiki/spaces/pages. > > “ > > > > If we agree about the idea of removing the dashboard and instead have a > > simple page then we’ll need to discuss the exact content and for that I’m > > proposing to discuss with Caty/GuillaumeD and make a proposal for further > > discussion. Of course any idea in reply to this email would also be much > > appreciated. > > > > But first things first! We first need to decide if this is a good idea or > > not. > > > > WDYT? > > > > Thanks > > -Vincent > > _______________________________________________ > > devs mailing list > > [email protected] > > http://lists.xwiki.org/mailman/listinfo/devs > > > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
