Try: extract template metadata from the HTML files directly #38984
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Spin-off from #36751
The templates & parts of block themes are declared via
.html
files. The metadata for each of those files (translatable title, area, post types, etc) is provided via an external file, thetheme.json
(seecustomTemplates
andtemplateParts
keys). This PR explores pulling metadata directly from the.html
files, spinning off from #36751Each template & part would add a top-level comment such as:
How to test
parts/header.html
file in the theme directory:trunk
, it'd be "header".TODO and related work.
wp-cli
: implement extracting the fields available for translation from the.html
templates.theme.json
mechanism if no metadata was found in the template & part.