WordPress / WordPress/secure-custom-fields
Integrate file-based definitions with WordPress Blueprints
Open
Nobody has claimed this yet.
[Type] Enhancement
- Dominant language
- PHP
- Stars
- 131
- Forks
- 64
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
This should be done parallel to #163, so that the "unified" CPT definitions can be integrated with WordPress Blueprints, not just in a separate file but even embedded in the main Blueprint JSON.
Contributor guide
No contributing guide indexed for this repository
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 #163 and the current file-based “unified” CPT definitions, then trace how WordPress Blueprints consume the main Blueprint JSON. Done when those definitions work both as a separate file and embedded in the main Blueprint JSON.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100