Jetpack: Admin Page: Introduce a banner for the WP.com security checklist

[tyxla]

From https://github.com/Automattic/wp-calypso/issues/32565

wp-admin first visit
I think it's important we provide a linear pathway for customers who aren't familiar with jetpack. I'm suggesting that the first time they visit the jetpack dashboard in wp-admin, we display a dismissible banner welcoming them to their jetpack dashboard and informing them of the checklist.

Clicking "continue jetpack setup" will bring them to the actual checklist to complete tasks. Clicking the "wp-admin" sidebar link will return them to their jetpack dashboard under "my plan," where a permanent mention of the checklist will reside...

a home for the checklist indicator in wp-admin
I think the checklist deserves a permanent mention under the "my plan" tab in the jetpack dashboard in wp-admin (consistent with its location in calypso as well). I'm envisioning a visual that's simple and consistent with all the UI that we see in calypso for consistency.

[tyxla]

Seems like Jetpack 7.4 sounds reasonable for this @jeffgolenski - what do you think?

[jeherve]

Related: #12277

[jeherve]

Next step: #12404

[sirreal]

Adding live checklist data to WP Admin requires new endpoints in both WordPress.com and Jetpack. That's unlikely to be ready in time for the 7.4 release.

@jeffgolenski will get a simplified CTA prepared that doesn't depend on live checklist data from the API that should be easier to ship in 7.4.

[jeffgolenski]

@sirreal As discussed in slack, since we'll only be able to have a static CTA for the upcoming jetpack release, here's a quick mock of what we can do.

I'd like to simply add a primary button to the plan header card - on large screens it'll sit to the side of the paragraph. On small screens, it'll sit below just like the smaller cards.

Notable changes:

• Boost the p tag size of jp-landing__plan-features-text to 14px for this card only.
• Keep the primary CTA blue - make sure it's the only primary CTA button on the page

Let me know if you have any questions, Jon!

[MichaelArestad]

It looks like there is a static notice. Can this issue be closed?

[tyxla]

I'd be fine to close it, but I'd delegate to @Automattic/luna for the final decision.

[simison]

This feature is still on the table, let's keep it open for now.

We'll re-evaluate within next couple weeks what exactly we'll be working on and if we do these changes in the plugin.

@jeffgolenski feel free to close if you're certain we won't implement this, tho!

[simison]

@jeffgolenski do you know if "progress bar" component will be useful in Jetpack? We got it in merged already but it's not used there at the moment.

We could clean it out instead. :-) It's easy enough to add back when ever needed.

[jeffgolenski]

@simison I'd love to see it come to fruition if you all have the time and resources to make it happen.

[simison]

@jeffgolenski the API it needs is pretty involved so likely nope, but curious if just the visual "progress bar" component itself should stay in case it is needed in future?

[jeffgolenski]

@simison yes please.