WordPress / WordPress/secure-custom-fields
Overhauling the file-based content modeling
@priethor is already working on this.
Since May 21, 2025.
- Dominant language
- PHP
- Stars
- 131
- Forks
- 64
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
SCF’s current approach to file-based definitions for Custom Post Types, Field Groups, Taxonomies, and Options Pages is limited (e.g., there are no schemas, making it challenging to create them from scratch without exporting existing content first) and does not fully align with emerging WordPress standards like Blueprints.
This project aims to overhaul the file-based configuration system, making it more flexible, easier to maintain, and compatible with modern WordPress workflows. The goal is to simplify content modeling, improve version control, and ensure SCF remains up-to-date with evolving best practices.
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.
Assessment
This issue has not been assessed yet.