8 Responses

  1. Konstantin

    Great post Brian!

    While working on Twenty Fourteen I noticed how a lot of people haven’t realized the power of using the get_*() methods to just change previously defined behavior, rather than removing and re-adding it. We ended up using it a lot in 2014, mostly to enhance documentation.

  2. Chris McCoy

    great post, just starting to implement this into my theme(s).

    also a great boilerplate https://github.com/slobodan/WordPress-Theme-Customizer-Boilerplate

  3. Piet

    Chris Bennett just wrote an article to keep in mind to use the sanitize_callback when using the theme customizer, most likely also when customizing it: http://make.wordpress.org/themes/2014/01/30/using-the-theme-customizer-with-the-theme-mods-api/

  4. Piet

    that should of course be Chip Bennett, not Chris, feel free to edit my comment

  5. گوشت شترمرغ

    Thank you, we used

  6. Jason Pelker

    Not enough commercial themes take advantage of this amazing WordPress feature. Screw bespoken options pages. You can do everything with the Theme Customizer technology–you just have to be creative. Just look at the new Widgets Customizer coming up in 3.9.

    I’d love to see multiple pages of the Customizer, though. I’d also love to see the Customizer become the content editing tool somehow, e.g. live preview with all the tools of the edit screen!

  7. Brian

    This is the post I was referring to in the older post. I absolutely love that this was written. It’s something I’ve always thought, and that I’m glad some companies are taking notice. Themes are ridiculously complicated to the point of absurdity. I hate hacking into a ‘custom theme’ with its annoying admin panel. Theme developers need to remember the power of simplicity.

Leave a Reply