WordPress / WordPress/secure-custom-fields

Migrate the SCF post editing pages to leverage Core Components

Open
#156 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

[Type] Enhancement Project
Dominant language
PHP
Stars
131
Forks
64
Avg merge
10m
Merged PRs (30d)
1

Description

SCF currently uses custom PHP form and field helper functions to build interfaces for creating and editing Field Groups, Post Types, Taxonomies, and Options Pages post types. This project aims to rebuild the SCF's post types editing logic (post.php) by leveraging native WordPress components such as DataForms and other core UI elements. The goal is to modernize and simplify these editing pages, improving maintainability and user experience by aligning with WordPress core design patterns.

Additional Context
  • It should be started after #142 begins.
  • It should be implemented with reusability in mind, e.g., to integrate them in the block editor for quick editing.
  • We should start with Taxonomies, as it is closely related to #155 and simpler than other types.
  • It should be introduced as an opt-in Beta feature.
Tasks
  • Migrate the Taxonomies editing page to native components
  • Migrate the Field Groups editing page to native components
  • Migrate the Post Types editing page to native components
  • Migrate the Options Pages to native components
  • Explore embedding these in the Editor, for example to Edit Taxonomies as in #155

Contributor guide

No contributing guide indexed for this repository

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

Start with post.php after #142 begins, and review the related scope in #155. Begin with the Taxonomies editing page and study how WordPress DataForms and other native components can support reusable editing interfaces. Done means the editing pages are migrated with an opt-in Beta feature, covering the listed post types and documenting the Editor embedding exploration.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
frontend, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.