Feature Wiki

Information about planned and released features

Tabs

Internal Links in Content Snippets

1 Initial Problem

The page editor does not offer the use of internal links when the following content-types are used in content-snippets:

  • Paragraphs
  • Sections
  • Media Objects: Instance Link Areas / Default Link Areas

Please note that the above content types are often used inside of other content types, a paragraph inside a data table or a column layout for example. We assume that once internal links work within paragraphs in a content-snippet, we then will be able to use them in data tables as well by:

- creating a content-snippet in a media pool
- adding a column layout
- adding a paragraph in one column of the layout
- insert an internal link in the text paragraph

2 Conceptual Summary

We propose to add internal links to the content types above for use within content snippets. Internal links can be created the exact same way as it would be if the content type the link gets added to exists outside a content-snippet.

3 User Interface Modifications

3.1 List of Affected Views

When working with content-types in a content-snippet:

  • editing text / paragraphs
  • inserting / editing a section
  • inserting / editing the advanced properties of media objects (instance linked areas and default linked areas)

3.2 User Interface Details

3.2.1 Current Problem

Problem: Only External Links in Content-Snippets
Problem: Only External Links in Content-Snippets

3.2.2 Proposed Solution

3.2.3 Edit Text (in content snippet)

Link Menu for editing a text paragraph within a content snippet

3.2.4 Insert Section (in content snippet)

Internal Link Option for a Section within a content snippet

3.2.5 Media Object: Advanced Settings (in content snippet)

Editing the Default Link Areas of an image within a content snippet
Editing the Instance Link Areas of an image within a content snippet
Adding Internal Link to image area (image added to content snippet)

3.3 New User Interface Concepts

No new interface concepts.

3.4 Accessibility Implications

No accessibility implications.

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

No privacy implications.

6 Security

No security implications.

7 Contact

  • Author of the Request: Sesterhenn, Fabian [sesterhenn]
  • 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

Sesterhenn, Fabian [sesterhenn], 29 Feb 2024: Aside from the ILIAS core/trunk development for ILIAS 10 we would like a patchfile for ILIAS 8 and 9 to be able to use this feature earlier.

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: 26. Mar 2024, 15:05, Sesterhenn, Fabian [sesterhenn]