Proposal for view/edit page Permissions(Rights) UI

[tkrieck]

@vmassol

I think that we should also propose what we want to do for XS, and that proposals should be made together for both Cristal and XWiki since we want to merge their UIs in the not-too-far future

You’re right, actually I did consult the admin page on XS before making this proposal, so at least it is based on it.

@vmassol

The downside is that there’s less space for admin UI options. Can you see this working for XS too?

I do for the page options at least. For the general Wiki Admin, there’s a specific proposal for it. Also, the dialog can be almost the size of the viewport so we can be generous on this aspect (on mobile the dialog should spans 100% of the width and height of the viewport).

Now, this brings an interesting discussion, if both should be the same screen as in XS or specialized screens (one for general admin and one for page admin).

There are pros for both approaches.

Discrete screens: we can specialize each for the needs of each use case. Page admin requirements are smaller in scope, so a dialog can work best as it does not completely remove context from the user (close the dialog and the users are back to where they were).

Same screen: there’s only one resource to maintain.

One question to be answered, is it technically feasible to have the same children pages but being opened by different parents? Like the same page that can be called by a discrete page OR by a dialog, depending on context?

@vmassol

It seems to me that we’re doing the same mistake than what we did in XS, ie consider that the # of rights is small and fits on the screen or almost fits (I already don’t like in your screenshot that Admin or Programming Rights are not shown, I think that’s not good enough and will be misleading for users).

I will make some mockups with more content to make more clear the behavior on each scenario. Hope that helps.

Thanks for the feedback!