Page MenuHomePhabricator

Code Splitting: Define set of needed Co-occurring components
Closed, DeclinedPublic2 Estimated Story Points

Description

Summary

In discussing code splitting options with Web, we determined that we should sync with them to define the set of frequently co-occurring components, so as to better inform our bundling strategies in the future.

Consider both current features and upcoming features such as font size + dark mode (near-to-mid term) and content exploration (longer-term)

Acceptance Criteria

  • Have a discussion with Web about which components frequently co-occur
  • Document this set

Event Timeline

Catrope renamed this task from Code Splitting: Define set needed Co-occurring components to Code Splitting: Define set of needed Co-occurring components.Jul 31 2023, 5:05 PM
Catrope moved this task from Up Next to Design-Systems-Sprint-5 on the Design-System-Team board.
Catrope set the point value for this task to 3.
Catrope changed the point value for this task from 3 to 2.Jul 31 2023, 5:14 PM
AnneT lowered the priority of this task from High to Low.Aug 14 2023, 5:05 PM
AnneT subscribed.

Setting priority to low as we have decided not to do this immediately

egardner raised the priority of this task from Low to Needs Triage.Oct 2 2023, 9:12 PM
egardner moved this task from Needs Refinement to Backlog on the Design-System-Team board.
CCiufo-WMF subscribed.

Declining as the approach in T349423 will not require DST to manage a set of co-occurring components.