[Usability] Menus inside Administration

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[Usability] Menus inside Administration

Ecaterina Moraru (Valica)
Hi,

This mail is also part of the Usability priorititzation list [1]

Admins expect to manage custom navigation from the Administration.

This proposal integrates the Menu application in Administration, see
http://design.xwiki.org/xwiki/bin/view/Proposal/IdeaMenuInAdministration#HProposals

Let me know what you think,
Caty

[1]
http://design.xwiki.org/xwiki/bin/view/Proposal/Usability/Tasks5/Prioritization/
Reply | Threaded
Open this post in threaded view
|

Re: [Usability] Menus inside Administration

Alex Cotiugă
Sounds like a good idea to me. If this would be a voting session, it would
be +1 from me.


On Fri, Feb 9, 2018 at 4:25 PM, Ecaterina Moraru (Valica) <[hidden email]
> wrote:

> Hi,
>
> This mail is also part of the Usability priorititzation list [1]
>
> Admins expect to manage custom navigation from the Administration.
>
> This proposal integrates the Menu application in Administration, see
> http://design.xwiki.org/xwiki/bin/view/Proposal/IdeaMenuInAdministration#
> HProposals
>
> Let me know what you think,
> Caty
>
> [1]
> http://design.xwiki.org/xwiki/bin/view/Proposal/Usability/
> Tasks5/Prioritization/
>
Reply | Threaded
Open this post in threaded view
|

Re: [Usability] Menus inside Administration

Thomas Mortagne
Administrator
+1

On the implementation detail side I hope the plan is not to add a
special #if for an extension and instead the extension itself will be
able to place itself there.

On Fri, Feb 9, 2018 at 3:35 PM, Alex Cotiugă
<[hidden email]> wrote:

> Sounds like a good idea to me. If this would be a voting session, it would
> be +1 from me.
>
>
> On Fri, Feb 9, 2018 at 4:25 PM, Ecaterina Moraru (Valica) <[hidden email]
>> wrote:
>
>> Hi,
>>
>> This mail is also part of the Usability priorititzation list [1]
>>
>> Admins expect to manage custom navigation from the Administration.
>>
>> This proposal integrates the Menu application in Administration, see
>> http://design.xwiki.org/xwiki/bin/view/Proposal/IdeaMenuInAdministration#
>> HProposals
>>
>> Let me know what you think,
>> Caty
>>
>> [1]
>> http://design.xwiki.org/xwiki/bin/view/Proposal/Usability/
>> Tasks5/Prioritization/
>>



--
Thomas Mortagne
Reply | Threaded
Open this post in threaded view
|

Re: [Usability] Menus inside Administration

Alex Cotiugă
That would also mean that we remove the AWM dependency from the Menu
application.

On Fri, Feb 9, 2018 at 4:42 PM, Thomas Mortagne <[hidden email]>
wrote:

> +1
>
> On the implementation detail side I hope the plan is not to add a
> special #if for an extension and instead the extension itself will be
> able to place itself there.
>
> On Fri, Feb 9, 2018 at 3:35 PM, Alex Cotiugă
> <[hidden email]> wrote:
> > Sounds like a good idea to me. If this would be a voting session, it
> would
> > be +1 from me.
> >
> >
> > On Fri, Feb 9, 2018 at 4:25 PM, Ecaterina Moraru (Valica) <
> [hidden email]
> >> wrote:
> >
> >> Hi,
> >>
> >> This mail is also part of the Usability priorititzation list [1]
> >>
> >> Admins expect to manage custom navigation from the Administration.
> >>
> >> This proposal integrates the Menu application in Administration, see
> >> http://design.xwiki.org/xwiki/bin/view/Proposal/
> IdeaMenuInAdministration#
> >> HProposals
> >>
> >> Let me know what you think,
> >> Caty
> >>
> >> [1]
> >> http://design.xwiki.org/xwiki/bin/view/Proposal/Usability/
> >> Tasks5/Prioritization/
> >>
>
>
>
> --
> Thomas Mortagne
>
Reply | Threaded
Open this post in threaded view
|

Re: [Usability] Menus inside Administration

vmassol
Administrator
In reply to this post by Ecaterina Moraru (Valica)
Hi,

Some thoughts:

* On http://design.xwiki.org/xwiki/bin/view/Proposal/IdeaMenuInAdministration#HProposals I see: "Users confuse Panels and Menus. Since creating the navigation is an Admin activity, they expect Menus to be in Administration.”
** It's not that user confuse them, it’s that they’re confusing! :) The fact that you create Panels with Menus and that you can also create Panels manually is also confusing. We need to decide what we want to promote and explain a lot better when one should be used vs the other. If the Menu app was limited to creating Menus the difference would be much simpler. Panels app for panels and Menu app for menus. IMO we may need to reintegrate some of the features of the menu app inside the panel app instead.
** "they expect Menus to be in Administration”. This is a discussion we’ve been having for a long time. Right now the strategy is NOT to do this but instead to make the Admin apps visible only to admins. I just noticed that the Menu app is visible to *everyone* by default. That’s wrong IMO. It should have default permissions to be visible to Admins only *by default* (admins could change that if they want), similar to Scheduler, Stats, Panels, etc.
** I’m ok to have a section in the Admin that lists all Admin apps (as a shortcut) if we think that’s useful, but it should only contain links to those apps and those apps should also be listed in the App Index. This allows Admins to change permissions for them, for ex if they want to allow such group of users the ability to create menus, etc.

So I wouldn’t fold the Menu app itself in the Admin UI for now for consistency reason, OR we need to decide that we want to move all Admin apps to the Admin UI (and thus remove the use case I mentioned above of being able to give permissions to some users or groups to use them).

Thanks
-Vincent

> On 9 Feb 2018, at 15:25, Ecaterina Moraru (Valica) <[hidden email]> wrote:
>
> Hi,
>
> This mail is also part of the Usability priorititzation list [1]
>
> Admins expect to manage custom navigation from the Administration.
>
> This proposal integrates the Menu application in Administration, see
> http://design.xwiki.org/xwiki/bin/view/Proposal/IdeaMenuInAdministration#HProposals
>
> Let me know what you think,
> Caty
>
> [1]
> http://design.xwiki.org/xwiki/bin/view/Proposal/Usability/Tasks5/Prioritization/

Reply | Threaded
Open this post in threaded view
|

Re: [Usability] Menus inside Administration

Ecaterina Moraru (Valica)
IMO configurations and admin stuff should be all in one place. If we don't
have a central location for them, they will not be discoverable. Also Admin
might see them (because of the Rights object provided) but not know they
are intended only for Admins.

Same for Panels. Not really sure why Panels.WebHome is accessible to
everyone. Even if you create a new panel, you need admin rights to use it
and display it. Now, admins can be global or space admin, but still, the
creation and enabling of panels is done though the WebPreferences.

We now can add entries in each of the Administration menu categories. We
also have the search in Administration. We just need to integrate them in
the right location and provide a flow.

I agree Menus and Panels are confusing, since they kind of do the same
thing. Panels are very technical since you need to write code, so the
difference Menu brought was the "easiness" to create them, using the list
syntax. Now, user are expecting even simpler interactions to create menus.
Most of them wanted drag&drop for the entries, listing the available
entries (scalability problems) and visual ways of creating them. Not to
mention the https://jira.xwiki.org/browse/XWIKI-10112 which is also listed
as P1.


On Mon, Feb 12, 2018 at 12:15 PM, Vincent Massol <[hidden email]> wrote:

> Hi,
>
> Some thoughts:
>
> * On http://design.xwiki.org/xwiki/bin/view/Proposal/
> IdeaMenuInAdministration#HProposals I see: "Users confuse Panels and
> Menus. Since creating the navigation is an Admin activity, they expect
> Menus to be in Administration.”
> ** It's not that user confuse them, it’s that they’re confusing! :) The
> fact that you create Panels with Menus and that you can also create Panels
> manually is also confusing. We need to decide what we want to promote and
> explain a lot better when one should be used vs the other. If the Menu app
> was limited to creating Menus the difference would be much simpler. Panels
> app for panels and Menu app for menus. IMO we may need to reintegrate some
> of the features of the menu app inside the panel app instead.
> ** "they expect Menus to be in Administration”. This is a discussion we’ve
> been having for a long time. Right now the strategy is NOT to do this but
> instead to make the Admin apps visible only to admins. I just noticed that
> the Menu app is visible to *everyone* by default. That’s wrong IMO. It
> should have default permissions to be visible to Admins only *by default*
> (admins could change that if they want), similar to Scheduler, Stats,
> Panels, etc.
> ** I’m ok to have a section in the Admin that lists all Admin apps (as a
> shortcut) if we think that’s useful, but it should only contain links to
> those apps and those apps should also be listed in the App Index. This
> allows Admins to change permissions for them, for ex if they want to allow
> such group of users the ability to create menus, etc.
>
> So I wouldn’t fold the Menu app itself in the Admin UI for now for
> consistency reason, OR we need to decide that we want to move all Admin
> apps to the Admin UI (and thus remove the use case I mentioned above of
> being able to give permissions to some users or groups to use them).
>
> Thanks
> -Vincent
>
> > On 9 Feb 2018, at 15:25, Ecaterina Moraru (Valica) <[hidden email]>
> wrote:
> >
> > Hi,
> >
> > This mail is also part of the Usability priorititzation list [1]
> >
> > Admins expect to manage custom navigation from the Administration.
> >
> > This proposal integrates the Menu application in Administration, see
> > http://design.xwiki.org/xwiki/bin/view/Proposal/
> IdeaMenuInAdministration#HProposals
> >
> > Let me know what you think,
> > Caty
> >
> > [1]
> > http://design.xwiki.org/xwiki/bin/view/Proposal/Usability/
> Tasks5/Prioritization/
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [Usability] Menus inside Administration

Ecaterina Moraru (Valica)
FTR this discussion was split into:
- [Proposal] Admin targeted applications should be available in the
Administration http://markmail.org/thread/7noehfu5qckrronp (Feb 12, 2018)
- [Brainstorming] Menus vs Panels
http://markmail.org/thread/sbrk7zcn7hrmznyv
Thanks,
Caty

On Mon, Feb 12, 2018 at 12:26 PM, Ecaterina Moraru (Valica) <
[hidden email]> wrote:

> IMO configurations and admin stuff should be all in one place. If we don't
> have a central location for them, they will not be discoverable. Also Admin
> might see them (because of the Rights object provided) but not know they
> are intended only for Admins.
>
> Same for Panels. Not really sure why Panels.WebHome is accessible to
> everyone. Even if you create a new panel, you need admin rights to use it
> and display it. Now, admins can be global or space admin, but still, the
> creation and enabling of panels is done though the WebPreferences.
>
> We now can add entries in each of the Administration menu categories. We
> also have the search in Administration. We just need to integrate them in
> the right location and provide a flow.
>
> I agree Menus and Panels are confusing, since they kind of do the same
> thing. Panels are very technical since you need to write code, so the
> difference Menu brought was the "easiness" to create them, using the list
> syntax. Now, user are expecting even simpler interactions to create menus.
> Most of them wanted drag&drop for the entries, listing the available
> entries (scalability problems) and visual ways of creating them. Not to
> mention the https://jira.xwiki.org/browse/XWIKI-10112 which is also
> listed as P1.
>
>
> On Mon, Feb 12, 2018 at 12:15 PM, Vincent Massol <[hidden email]>
> wrote:
>
>> Hi,
>>
>> Some thoughts:
>>
>> * On http://design.xwiki.org/xwiki/bin/view/Proposal/IdeaMenuInAd
>> ministration#HProposals I see: "Users confuse Panels and Menus. Since
>> creating the navigation is an Admin activity, they expect Menus to be in
>> Administration.”
>> ** It's not that user confuse them, it’s that they’re confusing! :) The
>> fact that you create Panels with Menus and that you can also create Panels
>> manually is also confusing. We need to decide what we want to promote and
>> explain a lot better when one should be used vs the other. If the Menu app
>> was limited to creating Menus the difference would be much simpler. Panels
>> app for panels and Menu app for menus. IMO we may need to reintegrate some
>> of the features of the menu app inside the panel app instead.
>> ** "they expect Menus to be in Administration”. This is a discussion
>> we’ve been having for a long time. Right now the strategy is NOT to do this
>> but instead to make the Admin apps visible only to admins. I just noticed
>> that the Menu app is visible to *everyone* by default. That’s wrong IMO. It
>> should have default permissions to be visible to Admins only *by default*
>> (admins could change that if they want), similar to Scheduler, Stats,
>> Panels, etc.
>> ** I’m ok to have a section in the Admin that lists all Admin apps (as a
>> shortcut) if we think that’s useful, but it should only contain links to
>> those apps and those apps should also be listed in the App Index. This
>> allows Admins to change permissions for them, for ex if they want to allow
>> such group of users the ability to create menus, etc.
>>
>> So I wouldn’t fold the Menu app itself in the Admin UI for now for
>> consistency reason, OR we need to decide that we want to move all Admin
>> apps to the Admin UI (and thus remove the use case I mentioned above of
>> being able to give permissions to some users or groups to use them).
>>
>> Thanks
>> -Vincent
>>
>> > On 9 Feb 2018, at 15:25, Ecaterina Moraru (Valica) <[hidden email]>
>> wrote:
>> >
>> > Hi,
>> >
>> > This mail is also part of the Usability priorititzation list [1]
>> >
>> > Admins expect to manage custom navigation from the Administration.
>> >
>> > This proposal integrates the Menu application in Administration, see
>> > http://design.xwiki.org/xwiki/bin/view/Proposal/IdeaMenuInAd
>> ministration#HProposals
>> >
>> > Let me know what you think,
>> > Caty
>> >
>> > [1]
>> > http://design.xwiki.org/xwiki/bin/view/Proposal/Usability/Ta
>> sks5/Prioritization/
>>
>>
>