Show Advanced KnowledgeHide Advanced Knowledge

Customizable Navigation-Menu in ILIAS-learning modules

This feature request provides an overview of the concept of making the repository tree in ILIAS learning modules customizable. To better understand the complexity of the proposal, the feature is divided into the following requests:

• Introduction of banners for the tree in ILIAS learning modules
• Introduction of Content Style Classes for Tree Entries in ILIAS Learning Modules
• Customizable learning progress icon in ILIAS learning modules

1 Initial Problem

At the PH Zürich we produce a large number of learning modules. More and more these modules are open educational ressources. While we can customize the content with stylesheets to give it a pleasant and modern look and feel, the navigation-tree cannot be customized and looks old fashioned and does not meet our graphic standards.

2 Conceptual Summary

For the big customer we created several learning modules, where we decided to hide the default navigation and manually created a nice customized navigation-tree to satisfy the demand of our customer. Of course to create and maintain such menus manually is very tedious and error-prone.

We would like to have a style-sheet and a style-sheet editor which lets us create these kind of navigation tree/menu dynamically.

3 User Interface Modifications

3.1 List of Affected Views

{Please list all views (screens) of ILIAS that should be modified, newly introduced or removed.}

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.}

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: Caspar Noetzli, caspar.noetzli@phzh.ch PH Zürich
• Maintainer:
• Implementation of the feature is done by: 

6 Funding

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

• Pädagogische Hochschule Zürich, Werner Willi

7 Discussion

Killing, Alexander [alex], 4 June 2019: Thank you very much for this suggestion. I share the general point that the presentation of the navigation structure is not very attractive. There are several points that might need discussion.

• Currently (4 June 2019) this feature page does not specify what style classes should be introduced and used to fulfill the requirements. There will be some conceptual work and specification needed before this can be discussed in the Jour Fixe.
• The Page Layout Revision (Desktop) will reorganise the presentation of the learning modules fundamentally. The tree navigation will be placed in the main bar slates. The trees should be rendered by using the kitchen sink tree implementation. Alternatively we might introduce drill down menues at this place in the future.
• There are no sound concepts how the content styles can/should influence components of the UI framework. Up to now this has not been necessary since UI framework components are not used within the content. There is an approach in the SCORM editor content style classes, but I doubt that this will gain the acceptance of the UI framework coordinators since it would need either inject content style classes into the components or to create dependencies to the component style classes within the content style editor.
• We might even decide to create new UI framework components to realise the requirements.

I think we need a smaller group of people (including at least one UI framework coordinator) to move this forward to a specification that can be brought to the Jour Fixe meeting.

8 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}.