Page Editor » Reorganise Setting Text Content Menu in Editor Administration

1 Initial Problem

The text content menu needs explanation and takes up an excessive amount of space across many sub-tabs.
Moreover, it is unclear whether these functions are needed at all.

2 Conceptual Summary

In the context of the new controls on which page elements should be available in which contexts, the set of inventory forms should also be tidied up.
This concerns the option to allow or disable specific styles in the page element "Text".

Alternatively, the options should be abandon altogether.

New Menu should combines the previous entries:

• ILIAS Learning Modules
• Wikis
• SCORM Editing
• Glossaries
• Test and Assessment
• Repository Pages
• Content Pages

3 User Interface Modifications

3.1 List of Affected Views

• Administration » Editing » ILIAS Page Editor » Text Content Menu [New Subtab]
  • Menu combines the previous entries:
    • ILIAS Learning Modules
    • Wikis
    • SCORM Editing
    • Glossaries
    • Test and Assessment
    • Repository Pages
    • Content Pages

3.2 User Interface Details

{ For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour. }

3.3 New User Interface Concepts

{ If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this. }

3.4 Accessibility Implications

No special requirements in respect of accessibility are to be expected.

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

No personal data is stored or processed to implement this feature. 

6 Security

We do not see any changes for special security issues.

7 Contact

• Author of the Request: {Please add your name.}
• 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.

• …

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}

Approval

Approved at {date} by {user}.