Assembler - Remove blockGap between header/sections/footer in new assembler theme

[miksansegundo]

Related to #78097

Proposed Changes

Remove the block gap between:

• header and footer patterns in the assembler large preview
• section patterns in the assembler large preview and the editor and front-end

Notes

• Users still can add margins between patterns or change the block gap from the editor

Follow-up tasks

• Create a PR to add styles on Creatio theme.json to remove the block gap between header and footer patterns in the editor and front-end. See Creatio - Remove blockGap between first-level patterns themes#7288

Assembler Large Preview

BEFORE	AFTER

Site Editor

BEFORE	AFTER

Testing Instructions

• Access the assembler /setup/with-theme-assembler/patternAssembler?siteSlug={ YOUR SITE }
• Add a header, two section patterns, and a footer. Choose patterns with a background color, not white background, so it's easier to see if there are gaps
• Verify that there aren't gaps between patterns in the assembler large preview
• Click "Continue" and you will land on the editor
• Verify you still see gaps between header and footer patterns in the editor
• Sandbox your site and the public API
• Go to the folder /wpcom/public_html/wp-content/themes/pub in your sandbox and checkout the PR Creatio - Remove blockGap between first-level patterns themes#7288
  • Alternatively you can manually edit the file on your sandbox
• Refresh the editor to confirm that there aren't gaps between header and footer patterns

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 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-ajp-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:commit-63fe692e4080b8af48a20d599be945aba7accba8

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:commit-63fe692e4080b8af48a20d599be945aba7accba8&env=jetpack

[matticbot]

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

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

name           parsed_size           gzip_size
entry-stepper        +37 B  (+0.0%)      +25 B  (+0.0%)

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

Sections (~54 bytes added 📈 [gzipped])

name                    parsed_size           gzip_size
pattern-assembler-step        -76 B  (-0.0%)      -10 B  (-0.0%)
import-flow                   -76 B  (-0.0%)      -10 B  (-0.0%)
subscribers                   +37 B  (+0.0%)      +21 B  (+0.0%)
sites-dashboard               +37 B  (+0.0%)      +21 B  (+0.0%)
site-purchases                +37 B  (+0.0%)      +21 B  (+0.0%)
settings                      +37 B  (+0.0%)      +21 B  (+0.0%)
purchases                     +37 B  (+0.0%)      +21 B  (+0.0%)
hosting                       +37 B  (+0.0%)      +21 B  (+0.0%)
home                          +37 B  (+0.0%)      +21 B  (+0.0%)
email                         +37 B  (+0.0%)      +22 B  (+0.0%)
domains                       +37 B  (+0.0%)      +21 B  (+0.0%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Async-loaded Components (~42 bytes added 📈 [gzipped])

name                               parsed_size           gzip_size
async-load-masterbar-help-center         +37 B  (+0.1%)      +21 B  (+0.2%)
async-load-design                        +37 B  (+0.0%)      +21 B  (+0.0%)
async-load-automattic-help-center        +37 B  (+0.0%)      +21 B  (+0.0%)

React components that are loaded lazily, when a certain part of UI is displayed for the first time.

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.

[taipeicoder]

LGTM 👍

[arthur791004]

Tested and looks good 👍