improve metadata sections on info page

1 Initial Problem

The metadata sections on info pages aren't presented with kitchen sink elements yet. Therefore the outer appearance should be improved.

2 Conceptual Summary

1. The metadata sections should be presented as
   1. proposal one: descriptive listings in panels (https://docu.ilias.de/goto_docu_stys_387_ListingDescriptiveDescriptive_default_delos.html)
   2. proposal two: properties in standard items (https://docu.ilias.de/goto_docu_stys_387_ItemStandardStandard_default_delos.html)

Tags: alle bestehenden Tags sind shy buttons und öffnen einen Modal zum Editieren und dann sind es halt nur buttons. Neu-hinzufügen button auch nur button

3 User Interface Modifications

3.1 List of Affected Views

• info page of any object (e.g. file, course, ...)

3.2 User Interface Details

3.3 New User Interface Concepts

Depending on which proposal should be used, there are some updates needed for the Kitchen Sink.

descriptive Listing: (https://test7.ilias.de/goto.php?target=stys_21_ListingDescriptiveDescriptive_default_delos&client_id=test7)
"Listings hold only textual information. They may contain Links but no Buttons." » so far not included: Preview Images, Perma Links, Licence-Icon, Tags, Tag-input field, Dropdown menu for manual setting of learning progress aswell as Save-Button (KS-element says: may contain NO Button)

standard item properties: (https://test7.ilias.de/goto.php?target=stys_21_ItemStandardStandard_default_delos&client_id=test7) 
"Property values MAY be interactive by using a Shy Buttons or a Link" » so far not included: Preview Images, Perma Links, Licence-Icons, Tags, Tag-input field, Dropdown menu for manual setting of learning progress aswell as Save-Button

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: Seibt, Alina [alina.seibt]
• Maintainer: Killing, Alexander [alex]
• 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}.