WordPress / WordPress/secure-custom-fields

SCF Roadmap

Open
#157 6 comments 10 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Editor Integration for Visual Flows

SCF currently relies on classic custom interfaces for content modelling and editing structured content, as well as meta boxes to edit content, which can fragment the experience for users. The aim is to integrate content modeling and custom field editing directly into the Block Editor, leveraging block features and workflows as the most effective way to deliver a seamless, intuitive, and future-proof experience for both content modeling and structured data editing.

  • #154
  • #155
  • Backlog: true in-context editing with block bindings and managing of CPT fields with blocks.

Modernizing Admin Screens

SCF’s classic wp-admin screens, while functional, rely heavily on custom components. This area focuses on upgrading these interfaces to leverage state-of-the-art WordPress components, providing a more appealing, user-friendly, and maintainable experience, while benefiting from the extensibility and iterative features of core components like DataViews.

  • #142
  • #136
  • #156
  • #172

Extensibility & third-party integrations

SCF is committed to being highly extensible and integrating seamlessly with the broader WordPress ecosystem. As such, this area focuses on enabling advanced workflows and third-party integrations as well as supporting other existing plugins.

  • #161
  • #166
  • #167
  • #171

Meta & Foundational work

This area encompasses foundational work and meta-initiatives that support SCF’s evolution as a canonical plugin for structured content management in WordPress.

  • #148
  • #158

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 by reviewing the linked issues listed under the four roadmap sections: Editor Integration, Modernizing Admin Screens, Extensibility, and Meta & Foundational work. This issue provides a strategic roadmap rather than a specific file, test, entry point, or independently verifiable change, so its completion criteria are not defined here.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
backend, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.