You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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/components is 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/components to handle some field types.
Other Considerations:
This feature will be introduced as an opt-in beta that administrators can enable.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
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:
@wordpress/components
is a huge undertaking; we should follow the 80-20 rule and consider alternatives for more niche field types.Dependencies:
@wordpress/components
to handle some field types.Other Considerations:
The text was updated successfully, but these errors were encountered: