Content
View differences
Updated by Niels Lindenthal almost 2 years ago
# Pain
* With the ongoing primerisation we are not 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
* As of now, only the notifications page is ready for that but we will prepare the other pages as well
* 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?
# Visuals
TBD
* With the ongoing primerisation we are not 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
* As of now, only the notifications page is ready for that but we will prepare the other pages as well
* 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
* **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?
TBD