Feature Wiki
Tabs
Info Section with Info Item
Page Overview
[Hide]1 Initial Problem
The launcher is fairly restricted in the way it can be used: It may contain a symbol, a messagebox, a link potentially opening a modal with a form or launching the object.
This maybe sufficient for some contexts but to launch a course for example more information is required to be passed on.
2 Conceptual Summary
Description
Purpose
An Info section organises one or more informational aspects of an entity within the system.
Composition
- An Info Section comprises one or more Info Items. It bears a headline H2.
- Info Items comprise a Headline H3 and Text. The Info Item may comrise a symbol.
Effect
Info Sections and Info Items are not interactive.
Rules
Usage
Info Items are to be used above Launchers.
3 User Interface Modifications
3.1 List of Affected Views
- Join Tab of Courses or Groups
3.2 User Interface Details
![](./data/docu/mobs/mm_99185/Infosection_.png?il_wac_token=7cfdc3ddf79c764a01af109578a5a780dd407989&il_wac_ttl=5&il_wac_ts=1725753384)
3.3 New User Interface Concepts
Unsure where to put it?
![](./data/docu/mobs/mm_99187/locate.png?il_wac_token=7cfdc3ddf79c764a01af109578a5a780dd407989&il_wac_ttl=5&il_wac_ts=1725753384)
3.4 Accessibility Implications
{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }
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: {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}
Privacy
Information in privacy.md of component: updated on {date} by {user} | no change required
Approval
Approved at {date} by {user}.
Last edited: 1. Aug 2023, 16:48, Tödt, Alexandra [atoedt]