Skip to content

Performance settings: simplify Search section to a dashboard link#48773

Draft
kangzj wants to merge 2 commits into
trunkfrom
update/search-161-performance-search-section
Draft

Performance settings: simplify Search section to a dashboard link#48773
kangzj wants to merge 2 commits into
trunkfrom
update/search-161-performance-search-section

Conversation

@kangzj
Copy link
Copy Markdown
Contributor

@kangzj kangzj commented May 13, 2026

Fixes SEARCH-161

Proposed changes

  • Removes the duplicate Classic/Instant Search toggles from Jetpack → Settings → Performance, plus the two contextual cards underneath (Add Search Widget, Customize search experience).
  • Replaces them with a short intro that names the available experiences (embedded results page, overlay, theme search) and a single "Manage Search settings" link pointing to admin.php?page=jetpack-search, where the full experience picker (Embedded / Overlay / Theme search / Off) already lives.
  • The SettingsCard upsell banner for sites without a Search plan continues to render automatically — that path was driven by feature={ FEATURE_SEARCH_JETPACK }, not by anything removed here.

The previous UI predates the new feature selector and had no entry point for the embedded experience. Two surfaces showing similar-but-not-identical toggles was confusing, so this PR collapses Performance down to the description + link agreed on in the issue thread.

Before / after

Before (trunk) After (this PR)
before after

Related product discussion/links

  • SEARCH-161

Does this pull request change what data or activity we track or use?

No.

Testing instructions

  1. Build the Jetpack plugin (pnpm jetpack build plugins/jetpack).
  2. On a site with Jetpack Search active: visit wp-admin → Jetpack → Settings → Performance.
    • Expect: the Search card now shows only the intro paragraph and a Manage Search settings link.
    • Click the link — it should go to admin.php?page=jetpack-search.
  3. On a site without Jetpack Search: same page.
    • Expect: the existing Jetpack Search upsell banner renders inside the card (unchanged behavior).
  4. With the site in Offline Mode: same page.
    • Expect: card shows "Unavailable in Offline Mode" and the dashboard link is hidden.
  5. Run the gui tests: pnpm test-gui -- _inc/client/performance/test/component.js.

Checklist

  • My code is tested.
  • My code follows the WordPress Coding Standards for PHP, JS, and accessibility.
  • My code has proper inline documentation.
  • I have added changelog files, or determined they are not needed.

The Search section in Jetpack → Settings → Performance duplicated the
Classic/Instant Search toggles already shown on the Search dashboard,
and offered no entry point to the new embedded search experience.

Replace the toggles + widget/customize cards with a short intro that
acknowledges the available experiences (embedded results page, overlay,
theme search) and a single CTA linking to the Search dashboard, where
the full experience picker lives. The SettingsCard upsell banner for
sites without a Search plan continues to render automatically.

SEARCH-161
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 13, 2026

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

  • To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack), and enable the update/search-161-performance-search-section branch.
  • To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack update/search-161-performance-search-section

Interested in more tips and information?

  • In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
  • Read more about our development workflow here: PCYsg-eg0-p2
  • Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

@github-actions github-actions Bot added [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Status] In Progress [Tests] Includes Tests Admin Page React-powered dashboard under the Jetpack menu labels May 13, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 13, 2026

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

  • ✅ Include a description of your PR changes.
  • 🔴 Add a "[Status]" label (In Progress, Needs Review, ...).
  • ✅ Add testing instructions.
  • ✅ Specify whether this PR includes any changes to data or privacy.
  • ✅ Add changelog entries to affected projects

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖


Follow this PR Review Process:

  1. Ensure all required checks appearing at the bottom of this PR are passing.
  2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
  3. You can use GitHub's Reviewers functionality to request a review.
  4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!


Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

  • WordPress.com Simple releases happen as soon as you deploy your changes after merging this PR (PCYsg-Jjm-p2).
  • WoA releases happen weekly.
  • Releases to self-hosted sites happen monthly:
    • Scheduled release: June 2, 2026
    • Code freeze: June 1, 2026

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

@github-actions github-actions Bot added the [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. label May 13, 2026
The Jetpack plugin's changelogger config only accepts major, enhancement,
compat, bugfix, or other. CI flagged "changed" as invalid; switch to
enhancement, which fits the simplification best.
@jp-launch-control
Copy link
Copy Markdown

jp-launch-control Bot commented May 13, 2026

Code Coverage Summary

Coverage changed in 5 files.

File Coverage Δ% Δ Uncovered
projects/plugins/jetpack/_inc/client/state/initial-state/reducer.js 56/120 (46.67%) -0.83% 1 ❤️‍🩹
projects/plugins/jetpack/_inc/client/state/site/reducer.js 36/104 (34.62%) -0.96% 1 ❤️‍🩹
projects/plugins/jetpack/_inc/client/state/modules/reducer.js 46/58 (79.31%) 1.72% -1 💚
projects/plugins/jetpack/_inc/client/state/connection/reducer.js 52/79 (65.82%) 2.53% -2 💚
projects/plugins/jetpack/_inc/client/performance/search.jsx 5/5 (100.00%) 41.67% -10 💚

Full summary · PHP report · JS report

@kangzj kangzj closed this May 13, 2026
@github-actions github-actions Bot removed [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. [Status] In Progress labels May 13, 2026
@kangzj kangzj reopened this May 13, 2026
@github-actions github-actions Bot added [Status] In Progress [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. labels May 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Admin Page React-powered dashboard under the Jetpack menu [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Status] In Progress [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. [Tests] Includes Tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant