Add new link style class

1 Initial Problem

Content styles are often extended with elements that represent a button. Mostly sections are used for this purpose. Users create a section "Button" and link to e.g. an ILIAS object. 

Technically, this is not correct. From an accessibility point of view, links should not be on divs. So if you want to link from the content to an object, you SHOULD use a link for that. However, no new link style classes can be added at the moment.

2 Conceptual Summary

If you edit a content style, a toolbar is added to the 'Style Clases' tab in the 'Link' sub-tab. The button 'Add Style Class' can be used to add new link styles.

Needs to be clarified:

It needs to be discussed whether new styles can be added for all link types OR whether, for example, only new styles for internal links can be created. 

If only one link type can be expanded, the button in the toolbar could be customized so that the following form can be omitted. 

If multiple link types are to be expanded, a form will appear after users click on the button. Here users can select the appropriate link type. Then users can give the link a title and design it. 

In the page editor, the custom links are displayed in the link dropdown and can be selected there.

3 User Interface Modifications

3.1 List of Affected Views

• Edit a Content Style » 'Style Clases'-Tab » 'Link'-Subtab

3.2 User Interface Details

See Conceptual Summary.

3.3 New User Interface Concepts

None.

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: [amilz]
• 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}

Privacy

Information in privacy.md of component: updated on {date} by {user} | no change required

Approval

Approved at {date} by {user}.