Proposed Changes
This PR implements the onboarding help widget for the agency dashboard and licenses page
Testing Instructions
Prerequisites
Since these changes are made specifically for agencies, you must set yourself(partner) as an agency – 2c49b-pb. Make sure to switch it back to the previous type.
Instructions
- Run
git checkout add/agency-dashboard-onboarding-help-widget and yarn start-jetpack-cloud
- Open http://jetpack.cloud.localhost:3000/, and you’ll be redirected to the /dashboard.
- Logout from your existing account or use an incognito window
- Open http://jetpack.cloud.localhost:3001/agency/signup and signup as an agency after creating a new WP.com account.
- After signing up -> You’ll be redirected to the licenses page -> Verify that you see the new onboarding widget as shown in the screenshot below. Also, verify that the
Issue New License on the header is not the primary button(no green background)
- Visit http://jetpack.cloud.localhost:3001/dashboard and verify that you see the new onboarding widget, as shown in the screenshot below.
-
Now create a new JN site and add it to the newly created account and visit the dashboard -> verify that you can now see the sites but not the onboarding widget.
-
Visit the licenses page and verify that the first step is completed and looks like the screenshot below. Please note you might have to refresh the page.
- Now click the
Issue New License button on step 2 and issue/assign a license to a site -> Verify that you can now see the licenses but not the onboarding widget. Also, make sure now the Issue New License on the header is now the primary button(green background)
Screenshots
Dashboard view – 375px
Dashboard view – 768px
Dashboard view – 1024px
Licenses view – 325px
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)?
Related to 1202619025189113-as-1203672006055800 & 1202619025189113-as-1201942917845805
Unfortunately, no screenshots were provided by the developer.
