Dogfood the Settings API
|Reported by:||johnbillion||Owned by:||johnbillion|
|Component:||Options, Meta APIs||Keywords:||needs-patch settings-api|
WordPress has had a Settings API for eight years, but the core settings screens in WordPress don't use it. Instead, these screens use hardcoded sections and fields, which means it's impossible for a plugin to remove sections or fields without removing the entire screen.
There's a new Fields API in development but this doesn't mean the core settings screens shouldn't be improved in the meantime by switching to the Settings API.
I think the best approach for this is to address one screen at a time, starting with General Settings, and go from there.
If anyone thinks this change should not be made, speak now or forever hold your peace.