Feature Wiki
Tabs
Use ILIAS Page Editor for Welcome and Exit page of LSO
Page Overview
[Hide]This seems to be a duplicate of Learning Sequence: Replace TinyMCE with Page Editor.
1 Initial Problem
The options one has when creating the welcome and exit page of a learning sequence are currently restricted to the rich-text editor. The problem is that the rich-text editor has only few options in order to create a page that looks appealing. Thus we want to introduce the "page editor" instead of the rich-text editor and the picture upload it is combined with.
2 Conceptual Summary
The rich-text editor which creates welcome and exit page of a learning sequence should be replaced by the page-editor. To achieve this two new subtabs are needed, one for "Customize welcome page" and one for "Customize exit page". Those tabs should allow the lso-owner to create good-looking welcome and exit pages for the learning sequence using the page editor. For the welcome page the page editor should offer a "curriculum-option" where one can place the curriculum on the content page.
3 User Interface Modifications
3.1 List of Affected Views
- Modified:
- Settings screen of learning sequence
- Newly introduced:
- Welcome Page subscreen of settings screen of learning sequence
- Exit Page subscreen of settings screen of learning sequence
- Removed:
- Rich-text editor on settings screen of learning sequence
3.2 User Interface Details
Figure 1: New settings screen of LSO.
Figure 2/3: New welcome screen of LSO.
Figure 4: Add Curriculum in page editor. It should be in second place, as in "login-page editor".
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.}
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 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.}
6 Funding
- Uni Freiburg
7 Discussion
8 Implementation
{The maintainer has to give a description of the final implementation and add screenshots if possible.}
Test Cases
- {Test case number linked to Testrail} : {test case title}
Approval
Approved at {date} by {user}.
Last edited: 28. Mar 2022, 15:27, Klees, Richard [rklees]



