On Jan 20, 2013, at 5:22 PM, Sergiu Dumitriu <[email protected]> wrote:

> Hi devs,
> 
> For content pages, the bottom tabs (comments, attachments, history,
> information) are very useful features. But does it make sense to keep
> those active for very technical pages?
> 
> For example, when viewing details about a tag, (Main/Tags?do=viewTag),
> why should people be allowed to comment? They might wrongly think that
> they're commenting on a tag, but that's just one complex page that
> handles almost everything about tags, so a comment like "this tag has a
> typo" doesn't help at all.
> 
> Other pages should have no bottom tabs as well: user directory, blog
> category management, the whole scheduler space, share by email...
> 
> While the homepage is a technical page (by default), it does make sense
> to leave the comments active, since it's the entry point for every user
> (although I think that the messaging system is a better way to send
> global messages).
> 
> 
> IMO, the advantage is that we're hiding actions that are rarely useful,
> but could be misused. The disadvantage is that we're breaking the
> universality of the UI.
> 
> I'm +1 for hiding, fewer mis-usable features is always better.

What if admins want to leave comments on a tech page modified by another admin 
to ask some question for example?

Said differently, shouldn't bottom tabs (comments, attachments, etc) be visible 
to admins for example? This could be achieved by only giving view rights to non 
admins by default on tech pages.

Another use case: imagine I'm an admin and I want to modify a tech page and I'd 
like to add an attachment to that page… IMO bottom tabs are still useful for 
admins on tech pages.

IMO the issue is different. If a tech is not supposed to be modified by the 
user then users should have only view rights on the page and NOT edit rights. 
This will solve this issue.

WDYT?

Thanks
-Vincent

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

Reply via email to