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

Add wp-theme-<name> and wp-child-theme-<name> classes to body tag #7038

Open
wants to merge 5 commits into
base: trunk
Choose a base branch
from

Conversation

nirajgiriXD
Copy link

Description

This PR introduces new classes to the body tag in WordPress themes. The classes wp-theme-<name> and wp-child-theme-<name> (if child theme) are added, where <name> represents the sanitized name of the active theme and child theme, respectively.

Changes Made

  • Added wp-theme-<name> class to the body tag for the current theme.
  • Added wp-child-theme-<name> class to the body tag for the current theme (if child theme).

Screenshots

  • For twentytwentyfour theme
theme
  • For a child theme named childtheme having twentytwentyfour as parent theme
child-theme

Trac ticket: https://core.trac.wordpress.org/ticket/19736

Copy link

github-actions bot commented Jul 16, 2024

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @[email protected], @jonnynews.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

Core Committers: Use this line as a base for the props when committing in SVN:

Props nirajgirixd, poena.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Copy link

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@carolinan
Copy link
Contributor

If these class names are intended to help plugins with theme specific styles, they also need to be present in the Site Editor.
(They are already available in the Customizer preview)

src/wp-includes/post-template.php Outdated Show resolved Hide resolved
src/wp-admin/admin-header.php Outdated Show resolved Hide resolved
src/wp-admin/admin-header.php Outdated Show resolved Hide resolved
src/wp-includes/post-template.php Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants