# Feature DREAM-93 - Create a SplitScreenHeader component

Project: Stream Design System
Status: in specification
URL: https://community.openproject.org/work_packages/DREAM-93

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.1.0 |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Work packages, Frontend components and Primer design system |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Henriette Darge |
| Accountable |  |
| Product manager |  |
| Developers | OP Dev Dream Team |
| Designer | Parimal Satyal |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

# Pain

*   With the ongoing primerisation we are now approaching the split view of WorkPackages
    
*   This is currently written in Angular and needs to be transformed to rails-based ViewComponents ideally with Primer components
    

# Acceptance

*   There is a new component which can be used inside the "primerised" split view 
    
*   The header is fixed, when switching tabs so that I know on all tabs which WP I am on.
    
*   Technical: For reusable parts (e.g. the status button or the colored type) we inroduce re-usable components which can be applied on other places later
    

## Open

*   **Name**: SplitScreen vs SplitView
    
    *   NL: No preference from my side
        
*   **Mobile:** ~~Shall the header shrink when I scroll?~~
    
    *   NL: I think it would be nice to have something more elaborated. Would it be possible to develop this independently? Do we need to decide this now?
        

## Out of scope

*   The header should not shrink or do anything magically when users scroll on a mobile device.
    

# Visuals

TBD