Hi Caty,

> On 21 Jun 2016, at 14:58, Ecaterina Moraru (Valica) <[email protected]> wrote:
> 
> Hi,
> 
> This thread is about deciding on a future for the Main.Welcome page. This
> page was used as the first gadget's content and was intended to be modified
> by the users. In 8.2M2 we changed the content of Main.WebHome page to
> provide simple wiki text instead of the Dashboard include, deprecating
> somehow the purpose of the Welcome page.
> 
> Problem: In the 'Navigation' panel the "Welcome to your wiki" is displayed
> as a child page of "Home". Users might ask what is the purpose of this page.
> 
> We could either:
> 1. Keep it
> 1.A and mark it as hidden: in order to not be displayed in the Navigation
> tree
> 1.B and move it to Dashboard: instead of being in the Main space, since now
> it's used only there.
> 1.C and change the text: from a generic 'Welcome' message, to instructions
> on how to edit the Dashboard (we would need a separate proposal on the
> content + if we want to display other gadgets)
> 
> 2. Remove it
> We could consider that its content is deprecated by the new Main.WebHome
> page, so no need for this page. So we could delete the page + remove it
> from Dashboard. Dashboard could highlight more advanced gadgets (needing
> the separate Dashboard proposal).
> 
> Let me know what you think,


+1 for 2. It’s not needed anymore since it’s been replaced by the new home 
page. It’s better to make the Dashboard useful right away (ie with useful 
content).

Now, I haven’t checked, but if we still generate subwiki’s home pages with the 
Dashboard, I believe we may also want to review this (for some of the same 
reasons we modified the main wiki’s home page, such as easiness of editing it) 
and replace it with a new subwiki home page.

For me we should definitely not have some welcome message in the Dashboard app 
anymore. It’s not its purpose.

Thanks
-Vincent

> Caty
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

Reply via email to