Skip to content

Blaze: move the "Learn more" link into the page description - #113950

Open
sbarbosa wants to merge 1 commit into
trunkfrom
sbarbosa/MARMON-38-move-blaze-learn-more-link
Open

Blaze: move the "Learn more" link into the page description#113950
sbarbosa wants to merge 1 commit into
trunkfrom
sbarbosa/MARMON-38-move-blaze-learn-more-link

Conversation

@sbarbosa

@sbarbosa sbarbosa commented Aug 31, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Fixes MARMON-38

Proposed Changes

  • Move the "Learn more" link out of the header's button area and into the header description, so it now reads: Promote your posts and pages across WordPress.com and Tumblr. Learn more.
  • The button area is now just the "Promote" button.
  • The description is one sentence with the link inside it, so it's a new string for translation.

Why are these changes being made?

Sitting next to "Promote", the link looked like a second button and was easy to skip past, so the help doc behind it wasn't getting found. Putting it at the end of the sentence that already explains what Blaze does makes it much easier to notice.

Testing Instructions

  1. Open Advertising for a site — /advertising/:site on WordPress.com, or Jetpack → Blaze Ads in wp-admin.
  2. "Learn more" should appear at the end of the description under the page title, and should no longer be next to the "Promote" button.
  3. Click it. It opens the "Promote a post" support doc — in the Help Center on WordPress.com and Atomic, in a new tab on self-hosted Jetpack.
  4. The same header is used by the Blaze setup page (the one shown when a site can't run campaigns yet), so the link appears there too.

In wp-admin this arrives with the next blaze-dashboard deploy.

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?
  • For UI changes, have you tested the affected components in dark mode?
  • Have you tested accessibility for your changes? Ensure the feature remains usable with various user agents (e.g., browsers), interfaces (e.g., keyboard navigation), and assistive technologies (e.g., screen readers) (PCYsg-S3g-p2).
  • 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)?

@sbarbosa
Blaze: move the "Learn more" link into the page description
9078cae 
It sat next to the Promote button, where it read as a second button and
was easy to miss. It now sits at the end of the description that already
explains what Blaze does, where people are more likely to find it.

The description and the link are shared by the Blaze setup page, so it
shows up there too.
@github-actions

github-actions Bot commented Aug 31, 2026 •
edited by matticbot
Loading

Copy link
Copy Markdown

WordPress.com

Automattic for Agencies

Jetpack Cloud Live (direct link)
https://calypso.live?image=registry.a8c.com/calypso/app:build-195297&env=jetpack

@matticbot matticbot added the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Aug 31, 2026
@github-actions

github-actions Bot commented Aug 31, 2026

Copy link
Copy Markdown

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

Sections (~9 bytes removed 📉 [gzipped])

Details
Name Parsed Gzip
promote-post-i2 +61 B +0.0% -9 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.

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.

@sbarbosa sbarbosa self-assigned this Aug 31, 2026
therocket-gr
therocket-gr approved these changes Sep 1, 2026
View reviewed changes

@therocket-gr therocket-gr left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested locally and code changes LGTM

Adding screenshots for reference

BEFORE VERSION:

Image

AFTER:

Image

@therocket-gr

therocket-gr commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

🤖 Code LGTM

The link now sits inside the explanatory subtitle and the action area contains only the primary Promote button, matching MARMON-38.
The rich translation uses Calypso's established components interpolation pattern, so translators can reposition the linked text safely.
Self-hosted Jetpack still opens the support article in a new tab, while WordPress.com and Atomic keep the Help Center modal. The selector logic is equivalent to the behavior removed from PromotedPosts.
The change adds no new expensive operation. Bundle impact is effectively neutral.
Relevant CI is green, including code style, unit tests, E2E, translation extraction, and ci/i18n.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@therocket-gr therocket-gr therocket-gr approved these changes
@jjolmo jjolmo Awaiting requested review from jjolmo

Assignees

@sbarbosa sbarbosa

Labels

[Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@sbarbosa @therocket-gr @matticbot