Content
View differences
Updated by Henriette Darge 10 months ago
###
This is **As** a preconditional work that needs to be done in order to render rails components within the (angular) project overview widgets \[enter role of user\]
**I want to** \[enter objective\]
**so that** \[enter desired result\]
#### Acceptance criteria **Acceptance criteria**
* For the project overview page:
<br>
**Technical notes**
* Create a (abstract) grid widget that renders a turbo frame inside
<br>
**Permissions and visibility considerations**
* Actual widgets can inherit from/use that and just pass in the href
_To whom is this feature visible?_
* Note: A candidate to test this would be the project status widget as we already have the components at hand (without the inline edit), however _When is it is not required to migrate this widget visible?_
**Translation considerations**
* _Key terms and phrases in the scope key languages_
**Out of this ticket (especially if it is too complicated)
scope**
* _Ideally (if quickly possible):_ Get rid <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the custom HTML for the split layout on the overview page and use `Primer::Alpha::Layout` instead changes._
This is
**I want to** \[enter objective\]
**so that** \[enter desired result\]
#### Acceptance criteria
* For the project overview page:
**Technical notes**
**Permissions and visibility considerations**
**Translation considerations**
* _Key terms and phrases
**Out
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed