Hosting Dashboard v2: view transitions (part 1)

[ellatrix]

Fixes DOTCOM-13060

Please note: Firefox does not support view transitions.

Screen.Recording.2025-05-09.at.17.27.33.mov

Proposed Changes

Adds view transitions for routes:

• Main header will cross fade
• Secondary header will slide in/out when it appears/disappears only. When that happens the main body should be pushed down/up.
• Main body title should stay in place, main button should shrink/expand.
• Main card should shrink expand and stay in place.

Why are these changes being made?

Testing Instructions

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
  • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-143641

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-143641&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-143641&env=a8c-for-agencies

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• blaze-dashboard
• help-center
• notifications
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug try/view-transitions on your sandbox.

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

App Entrypoints (~406 bytes added 📈 [gzipped])

name                    parsed_size           gzip_size
entry-dashboard-dotcom      +1938 B  (+0.2%)     +302 B  (+0.1%)
entry-dashboard-a4a         +1938 B  (+0.2%)     +302 B  (+0.1%)
entry-stepper                +668 B  (+0.0%)     +189 B  (+0.0%)
entry-subscriptions          +632 B  (+0.0%)     +179 B  (+0.0%)
entry-reauth-required        +632 B  (+0.0%)     +179 B  (+0.0%)
entry-main                   +632 B  (+0.0%)     +150 B  (+0.0%)
entry-login                  +632 B  (+0.0%)     +179 B  (+0.0%)
entry-domains-landing        +632 B  (+0.1%)     +179 B  (+0.1%)
entry-browsehappy            +632 B  (+0.3%)     +179 B  (+0.3%)

Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[ntsekouras]

That's really cool to see!

[ntsekouras]

Why would we need to add VStack in various pages? Also have you removed the description intentionally?

[ellatrix]

Yes, the description is not present in the designs, so I removed it.

It's necessary for there to be some content because otherwise the content will slide in (from nothing) instead of cross fade.

[ntsekouras]

Should we just add a placeholder paragraph then instead of these? Also PageLayout is a VStack wrapper and its children are wrapped.

[ellatrix]

I don't understand what you mean. I added the VStack because billing has that too for the summary buttons. Why a paragraph? These should because summary buttons, not paragraphs.

[fushar]

This is so cool! I've added @Automattic/dotcom-design (apologize if I'm pinging too many folks) to check if this OK design-wise for dotcom.