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.

Sign up for GitHub

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

Jump to bottom

Onboarding: WordPress logo not aligned to the left of the page #101111

Open
zaguiini opened this issue Mar 10, 2025 · 2 comments
Open

Onboarding: WordPress logo not aligned to the left of the page #101111

zaguiini opened this issue Mar 10, 2025 · 2 comments
Labels
[Experiment] AI labels added [Feature] Appearance & Themes [Feature Group] Appearance & Themes Features related to the appearance of sites. [Pri] Normal Schedule for the next available opportuinity. [Status] Auto-allocated [Status] Escalated to Product Ambassadors [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended

Comments

@zaguiini
Copy link
Contributor

Context and steps to reproduce

On the goals screen, and potentially others, the WordPress logo is a bit to the right, not respecting the line.

Image

Site owner impact

Fewer than 20% of the total website/platform users

Severity

Critical

What other impact(s) does this issue have?

No response

If a workaround is available, please outline it here.

No response

Platform

No response
@zaguiini zaguiini added [Type] Bug When a feature is broken and / or not performing as intended Needs triage Ticket needs to be triaged labels Mar 10, 2025
@zaguiini zaguiini changed the title Onboarding: WordPress logo not aligned to borders Onboarding: WordPress logo not aligned to the left of the page Mar 10, 2025
@github-actions github-actions bot added [Status] Escalated to Product Ambassadors [Pri] High Address as soon as possible after BLOCKER issues [Feature Group] Appearance & Themes Features related to the appearance of sites. [Feature] Appearance & Themes labels Mar 10, 2025
@github-actions GitHub Actions
Copy link

OpenAI suggested the following labels for this issue:

  • [Feature Group] Appearance & Themes: The issue concerns the alignment of the WordPress logo, which is related to the visual presentation of the site.
  • [Feature] Appearance & Themes: This label is relevant because it directly addresses issues related to how elements like logos are displayed on the site.

@matticbot matticbot added the [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts label Mar 10, 2025
@Robertght
Copy link

Robertght commented Mar 11, 2025 •
edited
Loading

Replicated:

Image

@Automattic/quake would this be for you or a Groundskeeping thing?

I lowered the priority to Normal for nwo.

@Robertght Robertght added [Pri] Normal Schedule for the next available opportuinity. Triaged To be used when issues have been triaged. and removed Needs triage Ticket needs to be triaged labels Mar 11, 2025
@matticbot matticbot moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ Mar 11, 2025
@Robertght Robertght removed the [Pri] High Address as soon as possible after BLOCKER issues label Mar 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
[Experiment] AI labels added [Feature] Appearance & Themes [Feature Group] Appearance & Themes Features related to the appearance of sites. [Pri] Normal Schedule for the next available opportuinity. [Status] Auto-allocated [Status] Escalated to Product Ambassadors [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended
Projects
Automattic Prioritization: The One Board ™
Status: Triaged
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Robertght @matticbot @zaguiini