WordPress / WordPress/Documentation-Issue-Tracker

[HelpHub] Typography heading video and description misplaced in Styles Overview page

Open
#2,191 3 comments 0 reactions 1 assignee View on GitHub

@chekle is already working on this.

Since May 13, 2026.

Customization user documentation (HelpHub)
Dominant language
Shell
Stars
109
Forks
73
PR merge metrics
No merged PRs in 30d

Description

Issue Description :

The heading typography video and its accompanying description are currently misplaced in the Typography section of the Styles Overview page.
Additionally, point 7 in the Typography list should be removed.
The video and description are not positioned directly under the relevant heading typography section, which disrupts the logical flow of the content.

URL of the Page with the Issue :

https://wordpress.org/documentation/article/styles-overview/

Section of Page with the issue :

Typography section – specifically the part describing typography settings for heading elements (H1–H6).

Why is this a problem?

The current placement of the heading typography video and description interrupts the structure of the content and makes it harder for users to follow the explanation.
Point 7 in the list is unnecessary and should be removed to maintain clarity and accuracy.
Proper placement of the description and video will improve readability and instructional clarity for users learning how to customize heading typography.

Suggested Fix

  1. Remove point 7 from the Typography list.
  2. Move the heading typography video to appear directly after the section explaining typography customization for heading elements.
  3. Add (or correctly position) the following description immediately before the video:

You can change the typography settings for heading elements from H1 through H6.

  1. Keep the video:
    https://wordpress.org/documentation/files/2023/03/typography-heading-6.8.mp4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.