Caution: This PR has changes that must be merged to WordPress.com
Hello gibrown! These changes need to be synced to WordPress.com - If you 're an a11n, please commandeer, review, and approve D40623-code before merging this PR. Thank you!

This is an automated check which relies on PULL_REQUEST_TEMPLATE. We encourage you to follow that template as it helps Jetpack maintainers do their job. If you think 'Testing instructions' or 'Proposed changelog entry' are not needed for your PR - please explain why you think so. Thanks for cooperation 🤖

Generated by 🚫 dangerJS against 23132c8d958f656f31f40e67ab1513a89172ffef

@gibrown Pushed a few changes to use a Card component for the Search onboarding. A few notes:

• I've not added the full show/hide Card logic here.
• On jetpack-notices I'm calling the new SearchOnboarding component for ease of use. I'm guessing that's not where we want to call it.
• Also noticed the component shows up on any and all sections of the Jetpack app as long as the URL contains ?search-thank-you.

Desktop:

Tablet:

Mobile:

If we just use a query param then I don't think there is any reason we need to store whether this has been dismissed or not anywhere, so maybe just clear the query param with something like:

	dismissCard = () => {
		const query = decode( window.location.search.substring( 1 ) );
		if ( 'search-thank-you' in query ) {
			delete query['search-thank-you'];
		}
		window.location.search = encode( query );
		analytics.tracks.recordJetpackClick( {
			target: 'search-onboarding',
			button: 'dismiss',
			page: this.props.path,
		} );
	};

Though I suspect there is a better way to do this.

That's a valid point — it depends on whether we want to make it semi-persistent or a one-time thing — but I agree we can show it just once right after purchase.

As per agreement to display the Thank you note in the purchase flow in Calypso, closing this PR (for now).