17 Comments

  1. Michael Beil

    I wonder what it would be like to develop this into somewhat of a Twitter-esque experience? Where the user clicks on a preexisting post/page and can then edit the content in the context of the surrounding elements. Somewhat of an edit-in-place UX.

    Report

  2. Weston Ruter

    Thanks, Sarah!

    This would only be possible with the new Panels API

    A correction: the plugin actually doesn’t use the Panels API. It just registers one “Posts” section and adds controls to it. Using panels may be a better approach when editing multiple posts concurrently.

    The plugin also grants customize capability to authors and editors who wouldn’t normally have access.

    This new customize capability was introduced in 4.0 (#28605).

    On themes like Twenty Fourteen, where you have featured images that appear on single posts, the plugin adds a convenient way to live preview various images without having to go back and forth between the admin and the frontend.

    Actually, and I only realized this relatively recently myself, but did you know that changing the featured image actually makes the change live even before you save the post? I found this very surprising behavior. The only way to truly preview a change to a featured image is to use something like Customize Posts.

    Likewise, something else I learned recently, did  you know that changing a page template cannot be previewed from the post editor? When you change the selected page template, the change will not show up when you preview the post (see #11049). However, in Customize Posts you can preview changes to the page template just by changing the dropdown selection, and then you can see what your page would look like with the new template after the preview refreshes.

    Most other changes to metaboxes containing data that gets saved to custom fields (postmeta) also get written when clicking the Preview button. The Customize Posts plugin provides a way to get around this, and also provides a live preview of the changes. Fixing this underlying issue of incorrectly persisting postmeta when doing a preview is captured in #20299. The current Customize Posts UI for editing postmeta is just a non-user-firendly first stab; future iterations should make it easy to add new controls to manage postmeta, just as metaboxes are added to the post editor.

    If a frontend editor does wind up landing in core in the future, do you think that the concept shown here for editing posts and postmeta could be a compliment to the experience?

    I’m collaborating with @avryl on integrating the Front-end editor with the Customizer. We have a couple issues open where we’ve been discussing ways to collaborate, along with @celloexpressions. She’s actually re-writing the Front-end editor to use the Customizer as the underlying framework for managing changes as well. So it’s not an either/or but a both/and.

    Customize all the things!

    Report

    • Sarah Gooding

      Thanks for the clarification and feedback, Weston! WordPress is really in a major transition now as it concerns live editing the main content of a post. Your plugin is a great experiment and it will be interesting to see where the collaboration leads. I have to admit that typing right there in the customizer and seeing it update on the page was a little bit thrilling, even if the preview was a little slow. :)

      Report

      • Weston Ruter

        Thanks! Regarding the slowness, this is just due to the postMessage transport not being implemented. Adding such live-updating previews actually requires explicit opt-in by the theme or post type since it is not known how the template is going to render the bits of information. Nevertheless, there is an issue logged to support this.

        Report

  3. Rémy

    This is going to far with the customizer in my opinion.

    The customizer settings should be focused on theme layout and options, and this is going out of scope. It would be better to focus on the frontend editor plugin, and give users a good, easy UX with it, instead of the strange workaround.

    Report

  4. mac2net

    Short answer – not a good idea. Just look at the picture and it is obvious.

    Report

  5. Jeff Chandler

    I like it when Weston Ruter puts on his lab coat and goes to town with the customizer. In this case and as I’ve seen mentioned already, editing should be done inline and not with boxes popping up around the content. With the Front-end Editor using the Customizer as a framework, I wonder if the interface will look similar to this experiment? I hope not.

    Ultimately, I’m interested to see how the Front-end Editor comes into play when previewing a post or writing a draft post. Will we be able to use it to write a post or will the editor be refrained from use until after a post/page is published?

    What will Weston think of next to use the Customizer for? Maybe order me a pizza :)

    Report

  6. blair2004

    it seems not working, “posts” fields is empty on customize screen

    Report

Comments are closed.

%d bloggers like this: