The Central Dashboard content area should provide a responsive, flexible layout where independent content parts can be placed.
Content parts are standalone UI elements. They may semantically belong to a specific domain, but technically they should be reusable on any page. Each content part defines its own preferred size constraints, while the page layout decides how much grid space it receives in a given context.
A responsive base layout is now required where the content parts can be dropped in.
Acceptance Criteria
Columns
- Experiment with maximum amount of columns per screen size and which breakpoints are suitable. Add final specs here.
- Idea/example: 2 columns by default; 6 for tablet sizes, 12 for full HD, 24 columns when 4k.
- Decide what CSS mechanism, or library (e.g. React Grid Layout) makes sense.
Example
- Apply the principles to current available content parts for evaluation.
The Central Dashboard content area should provide a responsive, flexible layout where independent content parts can be placed.
Content parts are standalone UI elements. They may semantically belong to a specific domain, but technically they should be reusable on any page. Each content part defines its own preferred size constraints, while the page layout decides how much grid space it receives in a given context.
A responsive base layout is now required where the content parts can be dropped in.
Acceptance Criteria
Columns
Example