Well, there is also another way to tackle that problem, which is to make the HomePage easily configurable. I have never understand why the home should be Main.WebHome, which does not seems meaningful, in particular in french. Even the Main space is weird, imagine a Hand space in english ;) (WebHome could also seen weird, while being more usual words that I feel hurt less, and could be ommitted). So, back on track, why not having an easy way to say, "set current page as the HomePage", and to in fact use the Dashboard itself as the default WebHome ? Why the hell should we have to destroy some interface to have a different home page ? WDYT ? On Tue, Sep 16, 2014 at 3:52 PM, vincent(a)massol.net <vincent(a)massol.net> wrote: -- Denis Gervalle SOFTEC sa - CEO

I think that is a good idea to make a navigation easy to a simple user, we could give to user a liberty to customize easily his home page with app who he want, for the implementation i propose an idea to simplified the customization: - Make a page in the admin or in the editing of page who we will display all off applications of the wiki and under this block we display the actual home page, and we can added or delete the applications by using a drop and drag, this idea is appreciated by users. - and for editing the current app used on the home page we can added a button edit behind any app, and when we click we display a lightbox to change this app, the idea to use a lightbox is just to stay on the home page and make other changes easily. WDYT ? 2014-09-17 9:13 GMT+01:00 vincent(a)massol.net &lt;vincent(a)massol.net&gt;et>: -- <http://www.xwiki.com/>*Yacine KEBIR* Web Designer / Front End Developer yacine.kebir(a)xwiki.com *Mobile: *+213 550 749 033 *Web Site : *www.xwiki.com

On Thu, Sep 18, 2014 at 10:30 AM, Denis Gervalle &lt;dgl(a)softec.lu&gt; wrote: One advantage is that you won't have to merge Main.WebHome when you upgrade. Even if DW does a 3-way merge, generally it's better/safer not to edit the documents from the default distribution.

Hi, once taking into account all of Edy's remarks, it feels a bit like what we actually need is a better UI for the {{include /}} macro :-) And then use that macro on the home page of the wiki. Guillaume ᐧ On Wed, Oct 8, 2014 at 4:00 PM, Eduard Moraru &lt;enygma2002(a)gmail.com&gt; wrote:

Hello Edi, On Mon, Oct 20, 2014 at 12:34 PM, Eduard Moraru &lt;enygma2002(a)gmail.com&gt; wrote: I need to think a little more about this in order to make a complete answer, but I read the list of usecases and I remarked one thing: In all UC1 to UC5, I think your "user" is more of an "admin" than a user. I see the following flow in working with a wiki: Alice downloads the wiki and plays around with it locally, tests it and checks its features. Then, she is convinced by the tool and decides to move this to the next level and install the wiki on a server (or get it installed) so that she can collaborate with her colleagues, Bob, Billy and Bogdan. To me Alice is not a user, she's more like a wiki admin. Then when the wiki is installed on the server, the three B boys are the users and Alice might become a user as well, or might always stay a little more admin. When she moves from her private tests to a public tool, Alice prepares the homepage of the wiki so that it matches the purpose of the wiki and the B boys. Alice will need to "UC3: The user needs to be able to easily replace the home page with his content" but the B boys won't. I think that the admin (Alice) homepage needs cannot be analysed independently from the user (Bob, Billy and Bogdan) homepage needs, because we risk to provide the admin with customization tools that they will never need because the user will never need such a customization. Thanks, Anca

Hi Edi, I sort of understand from this mail that you think I am "defending" the dashboard on the homepage. I cannot figure out how you got that idea. The only thing I was saying in the previous mail is that 2 dashboards by default don't make sense for me, because dashboard means to me overview and I think we should rather make it easy for users to turn their homepage in a proper overview rather than have 2 overviews. Because if we have the dashboard separately (as today), then the Alices will create on the homepage their own overview of the wiki, and then Bob, Billy and Bogdan will have 2 of them. This is not necessarily bad, to be able to have multiple dashboards, because you can imagine multiple facets of the same wiki, but I think for a default wiki user is confusing (seeing the homepage which is an overview and having a link on the right that takes to an overview). When I said that the 2 personas need to be analyzed together it was more about what kind of customization we promote to the admin (Alice). E.g. explaining as a generic thing that they could include another page and they could customize could be too generic for the need of Alice, which is to create a proper welcome page for the B-boys. If we knew / decided on what is a proper welcome page for the B-boys, then we could make a choice about how to allow Alice to take ownership, encourage editing, etc AND, in addition, go towards the "users oriented homepage". On Tue, Oct 21, 2014 at 3:32 PM, Eduard Moraru &lt;enygma2002(a)gmail.com&gt; wrote: That would be proposal 1 here: http://design.xwiki.org/xwiki/bin/view/Proposal/HomepageProposal1Keepcurren… rather than a UC. Since I don't know anymore what this mail is about and I am sure we're gonna get lost in details, here is my proposal (corresponsad to by option 2) expressed in the initial mail): * By default the home page is a regular wiki page, with some text in it, that demonstrates all the features of the wiki, something like a Sandbox webhome. This should cover a couple of the usecases for Alice admin that needs to understand how wiki works. Also, she will be able to edit the homepage like a regular page. * Next to the edit button of this page, we add a button with an UIExtension which will say: "Turn this homepage in a dashboard with gadgets". Upon click, we open a wizard where we explain a bit what's gonna happen **and also that history rollback can always be used to fix whatever we might have done**. The wizard will put a dashboard macro on the homepage, force the default edit mode to be inline, add a couple of gadgets already (some of the most used, etc) and will take the admin back to edit mode of this page, which she will customize as she pleases. * There is no link to a dashboard in the menu, the dashboard on Dashboard.WebHome does not exist anymore. The homepage will be a dashboard itself (and not include a dashboard). Ideally, the way I see this used is that when the admin is done experimenting and has full ownership, they will click this dashboard button and create a dashboard for the wiki to give to B users. Why dashboard and not any other thing, like a page include or free text? Mainly because I think the dashboard is an interesting usecase for the users (B), with the proper gadgets available, of course, and directing the Admin A towards that usecase could help noob admins that don't want to understand all the concepts of the wiki to have a nice homepage. I just thought of another quite frequent usecase for the homepage for the users B, which is the homepage of an application (when the wiki is fully dedicated to an application). I think this should be a preference setting for admin A, not an include. As in, the Main.WebHome will not include the other application homepage, but the wiki will actually land on a different page when accessed. This configuration could be done in the preferences of the wiki. The case of including pages in the home could be limiting for the panels or space specific skin (if the application has specific panels, like the blog, then the same panels would need to be configured on the whole wiki in order for the usecase "land directly in application blog" to be fulfilled). This would mean http://design.xwiki.org/xwiki/bin/view/Proposal/HomepageProposal4Setthispag… . Note that this proposal does not collide with the proposal I made above about the dashboard. Thanks, Anca

On Tue, Oct 21, 2014 at 7:48 PM, Anca Luca &lt;lucaa(a)xwiki.com&gt; wrote: This homepage will be in one language only (we know how well translations for the homepage turned out, the last time we tried it) and it's language will be handled by the distribution wizard which will ask a question before doing anything. This language will be used for the DW itself + the homepage version to be installed. Anca

To clarify my point of view, I would say that: - UC6 is not only a use-case, it's a proposal in itself "Flavors need to be able to easily set/replace the homepage" I propose that flavors, and wiki creation wizard, should be the (first) way to set and replace the homepage. The second one being to customize it using the standard and natural features of the wiki (edit wiki/inline/wysiwyg/whatever), which is already feature-rich. If I'm not wrong it would cover UC2, UC3, UC4 and (obviously) UC6. - I would say that UC1 and UC5 should be covered by a dedicated Help application (with a button in the applications panel) My argument is that using the home page content to cover those use-cases, would satisfy only the needs of Alice, and only just after she created her wiki. She wouldn't need help on xwiki concepts or navigation in each and every sub-wikis. Once she would master the wiki concepts, she would replace the home page with what she wants, and would have to choose between leaving the default helping content in it (instead of using all the room available to put her own content), or removing it - and so remove it for the B-Boys too. By the way, last wizard step may even present a question to user like "do you want to see some explainations about xwiki concepts ?" that would bring user to the help instead of directing him to the home page. There were discussions about bootstrap being "mobile first", I've always seen xwiki specifically "wiki first" ;-) , so in a sense I believe "edit" should remain an essential feature - it should be easy in any case and whatever is in a page. 2014-10-21 21:04 GMT+02:00 Jeremie BOUSQUET &lt;jeremie.bousquet(a)gmail.com&gt;om>:

Hi Jeremie, Thanks for your proposal (and for highjacking this thread in doing so :) ). I will add an entry on the proposals page for it and I suggest we move discussions not related to the Simplified Home Page proposals on the general thread: http://xwiki.markmail.org/thread/a3umh6ihsdpxrhws Thanks, Eduard On Tue, Oct 21, 2014 at 11:21 PM, Jeremie BOUSQUET < jeremie.bousquet(a)gmail.com&gt; wrote:

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 (lucaa@xwiki.com(mailto:lucaa@xwiki.com)) wrote: