Repository navigation
Update remaining <p> tags to use the new Typography approach. #11266
Copy link
Copy link
Labels
P2Low priorityLow priorityTeam MIssues for Squad 2Issues for Squad 2Type: EnhancementImprovement of an existing featureImprovement of an existing feature
Description
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
Pcomponent (that usesTypographyunder 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
<pacross the codebase and replace it by usingPcomponentexport default function P( { type = TYPE_BODY, size, children, ...props } ) { - Each default
ptag replaced withPcomponent will most likely have defaultsizepropSIZE_MEDIUM, so it will only need replacing of existingptags withPcomponent.- Where adjusting is needed, you can use available props
sizeandtypeandweightto match the style.
- Where adjusting is needed, you can use available props
- Keep the
classNameprop 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-spacingand/orline-height, as well asfont-family) where applicable after component has been replaced
- Remove extra styles if they are overriding the default values for the headings if present (
- Each default
- 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.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P2Low priorityLow priorityTeam MIssues for Squad 2Issues for Squad 2Type: EnhancementImprovement of an existing featureImprovement of an existing feature
Activity
eugene-manuilov commentedon Aug 27, 2025
IB ✔️
46 remaining items
hussain-t commentedon Oct 15, 2026
@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?
mohitwp commentedon Oct 15, 2026
QA Update ✅
Verified:
All previously reported typography observations have been resolved.
Details
hussain-t commentedon Oct 19, 2026
@mohitwp the fix for the email reporting panel regression @kelvinballoo found has been merged into main in #13889. Could you take another look?
mohitwp commentedon Oct 19, 2026
QA Update ✅
Details