Documentation

Kitchen Sink documentation of style: 'Delos' of skin: 'ILIAS'

Alignment

Purpose: An Alignment positions content blocks in relation to each other and defines breakpoints for changing screensizes. It therefore does not have an visual manifestation by itself, but rather groups and arranges content. Alignments do not carry any deeper semantics than those of the positioning. Their public usage hence is restricted to situations where the UI framework cannot feasibly know any deeper semantics for the relation of the contained components. Examples for these situations could be: - content that is completely created and arranged by users, such as pages from the page editor - content that is heavy on text, images or data presentations, such as reports, i.e. classic print layout situations - content where legacy components need to be included for the moment From the perspective of the UI framework it is always better to have meaningful semantics for components. Decisions like: How should this be arranged? How should this be styled? How should this be treated on small screens? are a lot easier then. This should be kept in mind when Alignments are used: Could there be a way to use a component with richer semantics? Could we create a component with richer semantics?
Composition: Alignment will accept Components implementing the "Block"-Interface. It will not alter the appearance of the Component.
Effect: When available screensize changes, the Alignment will arrange Blocks according to its rules.

Context

The presentation of Test & Assessment results MAY use Alignments within the contents of Presentation Table to compare the user's solution with the anticipated best solution.

Usage

Alignments MUST NOT be used when there is another component that fits the requirements (see purpose).
Due to the semantic weakness of the component, we request to decide using this UI element in new components at the Jour Fixe. You MUST only use this component in contexts stated here.

Parents

Descendants