Content
View differences
Updated by Henriette Darge 8 months ago
**Context**
An extension of the work done in ##67203.
**Acceptance criteria**
* For the project description widget:
* On the **overview** tab, there is a pencil icon in the header which is an invisible icon button
* When clicking that, the description will switch to CKEditor edit mode (similar to meeting notes), with two actions:
* Save (primary)
* Cancel (secondary)
* For the project status widget:
* On the **overview** **dashboard** tab, there is a pencil icon in three dots menu.
* Clicking on the header which is three dots, will open a menu with:
* an invisible icon button
option to edit the description
* When clicking that, the description will switch to CKEditor edit mode (similar to meeting notes), notes) with two actions:
* Save (primary)
* Cancel (secondary)
* an option to remove the widget
* When lacking the permission, the description text can also be read-only to some users (no pencil button or option in the menu).
**Screens**
Display mode on the dashboard tab:
<img class="image_resized op-uc-image op-uc-image_inline" style="width:352px;" src="/api/v3/attachments/785777/content">
<br>
Edit edit mode of the description field:
<figure class="image image_resized op-uc-figure" style="width:281px;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/785764/content"></div></figure>
**Open questions:**
1. Shall we apply the same pattern to the dashboard page?
* On the **dashboard** tab, there is a three dots menu.
* Clicking on the three dots, will open a menu with:
* an option to edit the description
* When clicking that, the description will switch to CKEditor edit mode (similar to meeting notes) with two actions:
* Save (primary)
* Cancel (secondary)
* an option to remove the widget
* Problem: The dashboard is Angular based. The widget themselves are Angular (including the header), only the content is part of a TurboFrame. In order to use more or less the same code on both Overview and Dashboard, we'd need to weaken the `WidgetBoxComponent` and implement a lot of hacks
* Possible solution: Switching from the edit button in the header to actual click-to-edit fields once we have them?
<br>
An extension of the work done in ##67203.
**Acceptance criteria**
* For the project description widget:
* On the **overview** tab, there is a pencil icon in the header which is an invisible icon button
* When clicking that, the description will switch to CKEditor edit mode (similar to meeting notes), with two actions:
* Save (primary)
* Cancel (secondary)
* On the **overview**
* Clicking on
*
*
Display mode on the dashboard tab:
<img class="image_resized op-uc-image op-uc-image_inline" style="width:352px;" src="/api/v3/attachments/785777/content">
<br>
Edit edit mode of the description field:
<figure class="image image_resized op-uc-figure" style="width:281px;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/785764/content"></div></figure>
**Open questions:**
1. Shall we apply the same pattern to the dashboard page?
* On the **dashboard** tab, there is a three dots menu.
* Clicking on the three dots, will open a menu with:
* an option to edit the description
* When clicking that, the description will switch to CKEditor edit mode (similar to meeting notes) with two actions:
* Save (primary)
* Cancel (secondary)
* an option to remove the widget
* Problem: The dashboard is Angular based. The widget themselves are Angular (including the header), only the content is part of a TurboFrame. In order to use more or less the same code on both Overview and Dashboard, we'd need to weaken the `WidgetBoxComponent` and implement a lot of hacks
* Possible solution: Switching from the edit button in the header to actual click-to-edit fields once we have them?
<br>