Page Editor » Spacer

1 Initial Problem

Style classes for paragraphs, blocks or media objects come with pre-defined margin and padding settings that are defined for their general use. But when layouting a page of a course, category or learning module it is often necessary to place a page element with a different space related to the upper or lower page element than the defined in the CSS. Usual workaround here is to either add empty text lines or even paragraphs (with non-breakable spaces) or to add a modified copy of the style class with different margins. Both ways are not very satisfying and reliable.

2 Conceptual Summary

To keep the style classes themselves clean from custom margin modifications, this feature request suggests to introduce a new page element "Spacer". This page element allows to add additional space on all four sides of an element to ease layouting a page and support a clean placing of elements especially in multi-column and/or multi-row layouts.

Properties

The spacer element …

1. … has no content but CSS properties.
   1. Inputs for height and width (incl. all supported values)
   2. Support of media queries (differing CSS values depending on media query)
2. … can be copied, moved, deleted like any other page element.
3. … has no CSS class.

to be continued...

3 User Interface Modifications

3.1 List of Affected Views

• Page editor » page element dropdown

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

3.4 Accessibility Implications

As this page element is just for layout and has no content it should be invisible for screen readers to avoid confusing users.

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 issues

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: Kunkel, Matthias [mkunkel]
• 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.

• ILIAS-Verein

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