WordPress / WordPress/secure-custom-fields
Support Custom Field Editing in Editor Sidebar
@cbravobernal is already working on this.
Since May 20, 2025.
- Dominant language
- PHP
- Stars
- 131
- Forks
- 64
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
This project introduces a new beta feature for Secure Custom Fields (SCF) that moves field group elements from their traditional location in the main content area to the WordPress editor sidebar. The goal is to create a more streamlined and modern editing experience by allowing users to view and edit custom fields directly within the Block Editor’s sidebar, similar to how core WordPress features like featured images and categories appear. This approach aligns with SCF’s broader initiative to modernize admin screens, reduce clutter in the main content area, and provide a more intuitive interface for managing structured content.
Additional Context
-
Risks:
- There may be UX challenges in presenting complex or numerous custom fields in the limited sidebar space, potentially leading to clutter or confusion.
- Reimplementing each field type leveraging
@wordpress/componentsis a huge undertaking; we should follow the 80-20 rule and consider alternatives for more niche field types.
-
Dependencies:
- May require enhancements in WordPress core for advanced custom field types and improved sidebar extensibility.
- May require improvements to
@wordpress/componentsto handle some field types.
-
Other Considerations:
- This feature will be introduced as an opt-in beta that administrators can enable.
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.