Feature Wiki

Information about planned and released features

Tabs

Introduction of banners for the tree in ILIAS learning modules

This request is part of the feature proposal Customizable Navigation-Menu in ILIAS-learning modules.

1 Initial Problem

To give our ILIAS learning modules an optical identifier we would like to have the option to add a banner image at the top of the tree.

2 Conceptual Summary

  • The banner image should be optional (not mandatory)
  • Default = "no banner"
  • Option «Banner»
    • Place to select/upload the banner: We think the banner could be a new class in the individual sub-contentstyle of the individual learning module. Alternatively it could be added to the Einstellungen in the section Darstellung (the same spot where the user can select the Kachelbild, the Standardlayout etc.)
    • Banner size  We would be prefer a solution, where the image is proportionally scaled to the width of the learning module tree. In other words the user can upload a image with any width to height ratio. The width then will be scaled to the width of the tree and the height will be scaled to keep the proportions of the original image.

Banner width = same as tree ; height = flexible
Banner width = same as tree ; height = flexible

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: {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

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

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

Last edited: 18. May 2020, 10:28, Mela, Alix [ILIAS_LM]