WordPress / WordPress/Documentation-Issue-Tracker
[Theme handbook] Just a confirmation about the “Header fields” section in `theme/core-concepts/main-stylesheet.md`.
Open
Nobody has claimed this yet.
developer documentation (DevHub)
themes
- Dominant language
- Shell
- Stars
- 109
- Forks
- 73
- PR merge metrics
- No merged PRs in 30d
Description
I am participating in the “Theme Development Handbook” Japanese translation project.
Issue Description
Doesn't WordPress detect the translation when the theme is activated?
URL of the Page with the Issue
theme/core-concepts/main-stylesheet.md
Section of Page with the issue
Why is this a problem?
* **Domain Path:** A relative path to where theme translations are stored. WordPress uses this field when the theme is disabled to detect translations. Defaults to `/languages`.
Doesn't WordPress detect the translation when the theme is activated?
Suggested Fix
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the Header fields section in theme/core-concepts/main-stylesheet.md and compare its Domain Path description with WordPress's theme translation behavior. Confirm whether the wording about detecting translations while the theme is disabled is accurate, then update the documentation to resolve the question and verify the rendered page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wordpress
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100