Skip to content

Update remaining <p> tags to use the new Typography approach. #11266

Description

@eugene-manuilov

Feature Description

This is a follow-up issue for #10946.


Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

  • Remaining occurrences of the hardcoded p tags are replaced with the new P component (that uses Typography under the hood).
  • Any duplicated styles that are hardcoded for the replaced paragraphs, but now covered in Typography component styles, are removed.

Implementation Brief

  • Search for remaining <p across the codebase and replace it by using P component
    export default function P( { type = TYPE_BODY, size, children, ...props } ) {
    • Each default p tag replaced with P component will most likely have default size prop SIZE_MEDIUM, so it will only need replacing of existing p tags with P component.
      • Where adjusting is needed, you can use available props size and type and weight to match the style.
    • Keep the className prop and check for the extra styles targeting the custom classes
      • Remove extra styles if they are overriding the default values for the headings if present (font-weight, font-size, letter-spacing and/or line-height, as well as font-family) where applicable after component has been replaced
  • We should treat this issue with a time limit, so after number of paragraphs are replaced within the dedicated time, we should keep opening a follow up issues to keep replacing them until completed.

Test Coverage

  • No updates are expected.

QA Brief

  • Briefly smoke check as many screens as possible and make note of any text formatting that appears egregiously incorrect. Switch to the release version and double check those elements. Return to execution for any regressions, or open new issues for pre-existing issues. Things to check:
    • Initial setup flow, with Analytics enabled.
    • Dashboard widgets, quickly checking each tab where relevant.
    • Open Select Metrics, poke around, select an invalid number of options and confirm error notices look ok.
    • Open Select Groups and do the same.
    • Open email reports and sharing settings from the header and look around.
    • Step through the feature tour.
    • Go to Settings and check Admin Settings.
    • Connect each service and check their setup steps and settings. Only the plugin side needs to be checked.

Changelog entry

  • Update typography for consistency throughout the plugin.

Activity

  1. self-assigned this
    on Aug 13, 2025
  2. added
    Team SIssues for Squad 1
    Next UpIssues to prioritize for definition
    on Aug 13, 2025
  3. removed their assignment
    on Aug 19, 2025
  4. eugene-manuilov commented on Aug 27, 2025

    @eugene-manuilov
    CollaboratorAuthor

    IB ✔️

  5. removed their assignment
    on Aug 27, 2025
  6. self-assigned this
    on Jul 15, 2026
  7. 46 remaining items

  8. hussain-t commented on Oct 15, 2026

    @hussain-t
    Collaborator

    @mohitwp, the fixes from your QA feedback are now merged into main.

    @JakePT has opened #13865 to clean up the admin bar styles and typography more thoroughly.

    When you QA, could you also check the data block titles in the WP Dashboard widget?

  9. removed their assignment
    on Oct 15, 2026
  10. mohitwp commented on Oct 15, 2026

    @mohitwp
    Collaborator

    QA Update ✅

    • Tested on main environment.
    • Verified that above reported issues are now resolved.
    • Tested the typography changes and compared them against the latest release.

    Verified:

    • Initial setup flow and splash screen.
    • Setup notices, including success messages.
    • Analytics setup screen and enhanced measurement descriptions.
    • AdSense module setup screen.
    • WordPress Dashboard Analytics setup notice.
    • Site Kit Admin Bar.
    • Font family, font size, weight, line height, letter spacing, and text alignment.

    All previously reported typography observations have been resolved.

    Details Image Image Image
  11. removed their assignment
    on Oct 15, 2026
  12. removed their assignment
    on Oct 19, 2026
  13. self-assigned this
    on Oct 19, 2026
  14. hussain-t commented on Oct 19, 2026

    @hussain-t
    Collaborator

    @mohitwp the fix for the email reporting panel regression @kelvinballoo found has been merged into main in #13889. Could you take another look?

  15. mohitwp commented on Oct 19, 2026

    @mohitwp
    Collaborator

    QA Update ✅

    • Tested on main environment.
    • Verified the issue is resolve now.
    Details Image Image
  16. removed their assignment
    on Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Low priorityTeam MIssues for Squad 2Type: EnhancementImprovement of an existing feature

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions