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

Site Migrations flow: Remove Jetpack logo from Plan screen or make it clearer what it means #96415

Closed
sixhours opened this issue Nov 14, 2024 · 2 comments
Labels

Comments

@sixhours
Copy link
Contributor

sixhours commented Nov 14, 2024

Image

The Jetpack logo in this screenshot looks out of place without surrounding context and doesn't mean anything to the average user. We should either:

  • Remove it.
  • Add contextual copy (ie. "Includes Jetpack features")
Copy link

OpenAI suggested the following labels for this issue:

  • [Feature Group] Site Migration: The issue relates to the migration process of sites and includes changes to the interface during this process.
  • [Feature] Ad-Free Experience & No WP.com Branding: The mention of the Jetpack logo suggests a concern about branding, which aligns with removing unwanted branding during site migrations.
  • [Feature] Appearance & Themes: The request to make the Jetpack logo clearer or remove it relates directly to the visual aspects of the site's theme and appearance.

@sixhours sixhours added [Feature] DIFM (Do It For Me) Flows All our services and tools where we build sites for users. [Feature] Site Migration Features related to site migrations to WPcom and removed [Feature] Ad-Free Experience & No WP.com Branding Features related to removing ads and WordPress.com branding from your site. labels Nov 14, 2024
@sixhours
Copy link
Contributor Author

sixhours commented Dec 9, 2024

This was fixed by #96987

@sixhours sixhours closed this as completed Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant