Fronts migration/replatforming

[jamesgorrie]

OKR

Increase percentage of pressed Fronts supported via DCR from 0% to 100%

• Project board
• Dashboard
• Milestone

Release plan

A front is supported when a set of criteria are met, as seen in FaciaPicker. This will set "DCR Supports" (dcrCanRender) = true.

We also have an experiment running for serving supported fronts (currently at 0%).

When a person is in that experiment, and the front is supported, a person will get a DCR front).

GitHub labels:

• dotcom-rendering: https://github.com/guardian/dotcom-rendering/labels/Fronts%20%3Anewspaper%3A
• frontend: https://github.com/guardian/frontend/labels/Fronts%20%3Anewspaper%3A

Resources

• Questions from Alex and design (Internal)
• Context to fonts

Figma

Note Harry said these are out of date:

• Containers overview: https://www.figma.com/file/EEuMzp8yUSrHfOooE5bio9/
• Card variation: https://www.figma.com/file/fyYTHGFesaVAMp6sIIRcCQ/
• Front container: https://www.figma.com/file/sx2vMFHbL7SsUo0LcpsKNe/

Dependency issues (and relevant teams)

• Container simplification (design and editorial/CP teams) - can/should happen pre-migration
• New container introduction (design and ed tools) - can/should happen after migration
• Ad placement and rendering (Commercial) - can happen during or after migration
• Personalisation (Identity, editorial, design) - can/should happen after migration

[ajbreuer]

I forgot we had Kat's study on that! I will go through those figmas and also create a file with all the patterns we currently get from the dynamic containers, I started yesterday and it feels like there are some simplifications

[rhiannareechaye]

@jamesgorrie where best do you think we should put this ticket?