id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,focuses 38734,Dogfood the Settings API,johnbillion,,"WordPress has had a [https://codex.wordpress.org/Settings_API 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 [https://make.wordpress.org/core/tag/fields-api/ 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. Related: #9296, #15691, #18801, #32396",enhancement,assigned,normal,Future Release,"Options, Meta APIs",2.7,normal,,needs-patch settings-api,,"accessibility, administration"