Content
View differences
Updated by Marc Alcobé 10 months ago
**As** a user \[enter role of user\]
**I want to** see the same loading everywhere in the app \[enter objective\]
**so that** the UI of the app is harmonised and doesn't disturb \[enter desired result\]
**Acceptance criteria**
* Use the already implemented skeleton loading for the `Portfolios` module in the rest of pages:
<br>
**Technical notes**
* `Home` page: Use a block of the skeleton for the favourite projects with two columns <br>
**Permissions and 3–4 rows. And the normal skeleton for lists in the recent work packages.
visibility considerations**
* `Work packages` details page:
_To whom is this feature visible?_
* Overview: Use a skeleton list block on the description of the work package, and fake two skeleton loading sections below the description.
* The rest of the tabs are loaded using the time to load the overview so they don't need skeleton.
* `Notification centre` page: Use the list skeleton loading view below the notification filters.
* `Global search` page: Use the list skeleton loading view below the search filters.
**Technical notes** _When is it not visible?_
**Translation considerations**
* Reuse _Key terms and phrases in the skeleton loading implemented for the BMDS portfolios module. key languages_
**Out of scope**
* <br>
**I want to** see the same loading everywhere in the app
**so that** the UI of the app is harmonised and doesn't disturb
**Acceptance criteria**
* Use the already implemented skeleton loading for the `Portfolios` module in the rest of pages:
**Technical notes**
**Permissions
* The rest of the tabs are loaded using the time to load the overview so they don't need skeleton.
* `Notification centre` page: Use the list skeleton loading view below the notification filters.
* `Global search` page: Use the list skeleton loading view below the search filters.
**Technical notes**
**Translation considerations**
* Reuse
**Out of scope**
* <br>