WordPress / WordPress/create-block-theme

Templates tab persistence

Open
#842 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Edit Theme settings enhancement
Dominant language
JavaScript
Stars
417
Forks
66
PR merge metrics
No merged PRs in 30d

Description

Part of #836. Wires the Templates tab. Depends on the Color/foundation PR. Final per-tab PR if scheduled last; can also land before others — order among PRs 2–5 is flexible.

Scope

  • TemplatePartsPanel → top-level templateParts array.
  • CustomTemplatesPanel → top-level customTemplates array (each entry: { name, title, postTypes: [...] }).
  • Update readme.txt to document the Edit Theme Settings feature (if this PR lands last; otherwise the readme update goes with whichever per-tab PR completes the feature).

Acceptance criteria

  • Adding / removing / editing template parts persists.
  • Adding a custom template with multiple post types persists with the array intact.
  • Removing a template removes the entry only (does not touch template files on disk — that's a separate concern).
  • If this is the last per-tab PR: readme.txt describes the feature in the Description and Changelog sections.

Out of scope

  • Touching template files on disk when entries are removed.
  • WP-CLI.

References

  • Tracking issue: #836

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.

Research direction

Trace TemplatePartsPanel and CustomTemplatesPanel to find the persistence path and how the top-level templateParts and customTemplates arrays are represented. Verify adding, editing, and removing entries, including multiple postTypes and entry-only removal. If this is the last per-tab PR, update readme.txt Description and Changelog sections.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.