Separate Page Actions of Wiki Pages

1 Initial Problem

Currently, actions that can be done for one wiki page are mixed with other general wiki functions in a secondary panel. Because the individual actions are grouped together in a dropdown, it is only visible at the second click (opening the dropdown) what can be done with the page. Frequently searched actions such as "Rename page" could be found more quickly by the user if they were directly visible.

2 Conceptual Summary

A new Secondary Panel "Page Actions" is introduced.

In this panel, the page actions that were previously grouped together in a button group in the secondary panel "Wiki Functions" will be listed in its own secondary panel.

This makes important actions such as "Rename Page" and the display of hidden metadata more directly visible. The display of action "Show/Hide Metadata" depending on the request Hide individual metadata block.

This panel should be visible for users who have the "Edit Content" permission and can make at least 1 page action. The individual page actions should be available as before depending on the permissions.

3 User Interface Modifications

3.1 List of Affected Views

• Wiki > Content
• Wiki > Content > Wiki Functions

3.2 User Interface Details

3.3 New User Interface Concepts

No new UI concepts.

3.4 Accessibility Implications

Shy buttons must be controllable with the keyboard.

4 Technical Information

{ The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

5 Privacy

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Seiler, Yvonne [yvseiler] (Universität Bern)
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• Universität Bern

9 Discussion

10 Implementation

{ The maintainer has to give a description of the final implementation and add screenshots if possible. }

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Privacy

Information in privacy.md of component: updated on {date} by {user} | no change required

Approval

Approved at {date} by {user}.