Skip to content

Migrate editor preferences to new package. #31965

@talldan

Description

@talldan

What problem does this address?

The editor more menu is entirely implemented in the edit-post package and not reusable across editors.

The site and widgets editors are duplicating a lot of code to implement more menus, and this seems unnecessary. Much of the options could be implemented in a more generic and reusable way.

What is your proposed solution?

Either migrate the preferences to the interface package or create a new package.

Interface seems a good fit because it already has some similar UI concepts in the sidebar and tabs that it exposes. These are configurable, so migrating the more menu would involve similar work.

The preferences for some editors have now already been migrated to interface, but the plan is to now create a new preferences package, so they'll need to be migrated again.

Update - the new preferences package has now been shipped, and the next step is to migrate the preferences in each of our editors/packages.


Status

Metadata

Metadata

Assignees

Labels

[Feature] Site EditorRelated to the overarching Site Editor (formerly "full site editing")[Feature] Widgets CustomizerAbility to add and edit blocks in Customize → Widgets.[Feature] Widgets ScreenThe block-based screen that replaced widgets.php.[Package] Edit Post/packages/edit-post[Type] Code QualityIssues or PRs that relate to code quality[Type] New APINew API to be used by plugin developers or package users.[Type] Tracking IssueTactical breakdown of efforts across the codebase and/or tied to Overview issues.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions