In reply to Weston Ruter.

I agree but too often that's not the message that seems to get out. It's "The Customizer will be increasingly important" which gives the message that more and more things will be stuffed into it.

As I said in another comment here, what I'd like to see is a clear statement of what the Customizer is and is NOT. It started life as a way to customize themes, not a front end editor, admin, etc. Then I'd like to see some discussion around what else should be done and HOW. For things that are out of scope of the customizer, launch new projects. Ideally, these would define a new admin experience.

To me, the customizer should be a rarely used, but powerful way to edit theme settings, including things like tagline, etc. It should NOT be a way to do day to day admin tasks. Those should be out of scope for the Customizer, but the need for them should drive people to start rethinking the admin interface.

Also, don't name the API the Customize API - that lends itself to confusion.