[andresilva-guardian]

What does this change?

Updates the heading typography on the puzzles archive page to match the design:

• Page title (h1, PuzzlesArchiveLayout): headline.bld.24 below 740px and headline.bld.28 from 740px (tablet) up. It was headline.bld.34 at every breakpoint.
• Game title (h2, PuzzlesArchiveCalendar): headline.med.28 below 740px and headline.med.34 from 740px (tablet) up. It was headline.bld.34 at every breakpoint, with a line-height: 1.05 override that is now removed so the token's 1.15 applies.

Only existing @guardian/source/foundations tokens are used (headlineBold24, headlineBold28, headlineMedium28, headlineMedium34), so there are no shared library changes.

Why?

Design QA tickets on the archive page:

• Title of page should be 28px, not 32px (tablet to wide)
• Title of page should be 24px, not 32px (mobile to phablet)
• Game title font size should be headline.med.34, currently headline.bld.34 (tablet to wide)
• Game title font size should be headline.med.28, currently headline.bld.34 (mobile to phablet)

The tablet values for the game title were not specified in the design, so they follow the desktop value, the same pattern as the page title.

How has this change been tested?

• Type check, Prettier and ESLint pass on the changed files.
• Checked the archive layout in Storybook (Layouts/Puzzles Archive)

Screenshots

Before	After

[github-actions]

🚀 Image pushed to AWS ECR

Image digest: sha256:c031b42cc01d2ff87c770932950b93f3029caa4c8ad2265442b524d0f890c64c

🐛 Run the image locally

The following can be used to run the image locally:

# Refer to image using the immutable digest. Find alternatives below.
IMAGE_IDENTIFIER="@sha256:c031b42cc01d2ff87c770932950b93f3029caa4c8ad2265442b524d0f890c64c"

# Refer to image using branch tag
# IMAGE_IDENTIFIER=":branch-afs-fix-puzzles-archive-title"

# Refer to image using build tag
# IMAGE_IDENTIFIER=":build-32910"

# Set environment variables for the AWS CLI
AWS_PROFILE="<A_PROFILE_FROM_JANUS>"
AWS_DEFAULT_REGION="eu-west-1"

IMAGE_ACCOUNT_ID=$(aws ssm get-parameter --name /organisation/accounts/artifacts --query "Parameter.Value" --output text)
REGISTRY="${IMAGE_ACCOUNT_ID}.dkr.ecr.${AWS_DEFAULT_REGION}.amazonaws.com"
IMAGE="${REGISTRY}/guardian/dotcom-rendering/dotcom-rendering${IMAGE_IDENTIFIER}"

# Login to AWS ECR https://docs.aws.amazon.com/AmazonECR/latest/userguide/registry_auth.html
aws ecr get-login-password | docker login --username AWS --password-stdin $REGISTRY

# Pull the image
docker pull $IMAGE

# Run the image. You'll likely need to set additional flags. See https://docs.docker.com/reference/cli/docker/container/run.
docker run $IMAGE

---

From guardian/actions-ecr.

[github-actions]

Deploy build 32910 of dotcom:rendering-all to CODE

All deployment options

• Deploy build 32910 of dotcom:rendering-all to CODE
• Deploy parts of build 32910 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.

[github-actions]

Hello 👋! When you're ready to run Chromatic, please apply the run_chromatic label to this PR.

You will need to reapply the label each time you want to run Chromatic.

Click here to see the Chromatic project.

[gu-prout]

Seen on PROD (merged by @andresilva-guardian 5 minutes and 6 seconds ago) Please check your changes!