Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Launchpad Widget: Introduce the launchpad widget to the WP Admin Dashboard #39806

Draft
wants to merge 16 commits into
base: trunk
Choose a base branch
from

Conversation

arthur791004
Copy link
Contributor

@arthur791004 arthur791004 commented Oct 17, 2024

Related to https://github.com/Automattic/dotcom-forge/issues/9429

Proposed changes:

  • Introduce the Launchpad widget into the WP Admin Dashboard and we will customize the Launchpad by the site intent (here) in the follow-up PR
  • The feature is disabled by default and you have to enable it by the wpcom_launchpad_widget=true query string

Screenshots

image

Other information:

  • Have you written new tests for your changes, if applicable?
  • Have you checked the E2E test CI results, and verified that your changes do not break them?
  • Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

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

Testing instructions:

  • Apply changes to your site
  • Go to /wp-admin?wpcom_launchpad_widget=true
  • Make sure you can see the Launchpad widget

Copy link
Contributor

github-actions bot commented Oct 17, 2024

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 WordPress.com Simple 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, and enable the exp/launchpad-widget branch.

    • For jetpack-mu-wpcom changes, also add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php file.
  • To test on Simple, run the following command on your sandbox:

    bin/jetpack-downloader test jetpack exp/launchpad-widget
    
    bin/jetpack-downloader test jetpack-mu-wpcom-plugin exp/launchpad-widget
    

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

Copy link
Contributor

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 Team 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 🤖


The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.


Follow this PR Review Process:

  1. Ensure all required checks appearing at the bottom of this PR are passing.
  2. Choose a review path based on your changes:
    • A. Team Review: add the "[Status] Needs Team Review" label
      • For most changes, including minor cross-team impacts.
      • Example: Updating a team-specific component or a small change to a shared library.
    • B. Crew Review: add the "[Status] Needs Review" label
      • For significant changes to core functionality.
      • Example: Major updates to a shared library or complex features.
    • C. Both: Start with Team, then request Crew
      • For complex changes or when you need extra confidence.
      • Example: Refactor affecting multiple systems.
  3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!


Mu Wpcom plugin:

  • Next scheduled release: WordPress.com Simple releases happen semi-continuously (PCYsg-Jjm-p2).

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


Wpcomsh plugin:

  • Next scheduled release: Atomic deploys happen twice daily on weekdays (p9o2xV-2EN-p2).

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

@arthur791004 arthur791004 self-assigned this Oct 18, 2024
@arthur791004 arthur791004 changed the title WIP Launchpad Widget: Introduce the launchpad widget to the WP Admin Dashboard Launchpad Widget: Introduce the launchpad widget to the WP Admin Dashboard Oct 18, 2024
@arthur791004
Copy link
Contributor Author

@lucasmendes-design Do you have any idea how to make the Launchpad widget fit the styles on the WP Admin Dashboard? Thank you!

@fushar
Copy link
Contributor

fushar commented Oct 18, 2024

Do you have any idea how to make the Launchpad widget fit the styles on the WP Admin Dashboard?

Can we maybe do something like this? Still need some design on the progress bar though:

image

It's inspired by an existing native Core widget:

image

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

Successfully merging this pull request may close these issues.

2 participants