You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Investigate if we can optimise our css and js used in our example assets. Additionally assess if we can separate out full page examples into their own asset set or combine them with example assets.
We discovered whilst working on the above issue that full page examples are also using the standard website assets, meaning that we're importing component assets that are only relevant to those examples. We think we can make performance gains by moving these out of the main website assets and potentially combining them with example assets.
Whilst we're here, it's worth seeing how much we can optimise examples. We presume that example need all js and scss but is that the case?
Who needs to work on this
Developers
Who needs to review this
Developers
Done when
We have investigated if moving full page examples out of the website asset set is beneficial
We have investigated if we can optimise example assets
We have made any changes
The text was updated successfully, but these errors were encountered:
What
Investigate if we can optimise our css and js used in our example assets. Additionally assess if we can separate out full page examples into their own asset set or combine them with example assets.
Why
An offshoot of #3732
We discovered whilst working on the above issue that full page examples are also using the standard website assets, meaning that we're importing component assets that are only relevant to those examples. We think we can make performance gains by moving these out of the main website assets and potentially combining them with example assets.
Whilst we're here, it's worth seeing how much we can optimise examples. We presume that example need all js and scss but is that the case?
Who needs to work on this
Developers
Who needs to review this
Developers
Done when
The text was updated successfully, but these errors were encountered: