WordPress / WordPress/Documentation-Issue-Tracker
[Themes handbook] Document recommendations for naming conventions for slugs in theme.json when configuring preset settings
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 109
- Forks
- 73
- PR merge metrics
- No merged PRs in 30d
Description
What is the new page you are requesting?
Continuation of #563
Add more detail about recommendations for using more semantic slugs This page should be written from a high level since slug names are used across all presets in theme.json.
Ideally, mentions of creating preset slugs in theme.json can link out to this page to support more specific recommendations for individual preset settings.
How will this new page help you?
Begin to provide information about best practices for naming conventions used in theme.json across presets to encourage consistent standards across block themes.
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
Start by reviewing the related issue #563 and the existing guidance about preset slugs in theme.json. Draft a high-level Themes handbook page covering semantic slug naming recommendations across presets, and ensure references to creating preset slugs can link to it. Done means the page provides consistent naming guidance for block themes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json, wordpress
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100