Weston Ruter

In WordPress 4.5 the <a href="https://make.wordpress.org/core/2016/02/16/selective-refresh-in-the-customizer/" rel="nofollow ugc">selective refresh</a> framework was introduced in core. One of the key concepts in this framework is the “partial”, the region in a document which is selectively refreshed when a related setting is modified. This means that one or more settings are linked with a given element in the preview. When selective refresh was first was introduced it supported the ability for a user to “shift click” on a partial to jump to and focus on the related control in the pane. In WordPress 4.7 this was then enhanced with <a href="https://make.wordpress.org/core/2016/11/10/visible-edit-shortcuts-in-the-customizer-preview/" rel="nofollow ugc">visible edit shortcuts</a> so that users could click (touch even) on the icon to be able to reveal the control in the pane.
The Customize Inline Editing plugin builds on edit shortcuts by allowing the setting to be modified inline via direct manipulation in the preview without having focus removed and placed on the controls pane. This is particularly useful on mobile devices on small screens where a user cannot both see the controls and preview at the same time, as can be compared here:
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/w7WfSEtT8pc?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
Inline editing in this way is also helpful for accessibility since keyboard focus remains in the preview at the element being edited, as can be seen in this demonstration of inline editing on a desktop browser:
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/KesM3vo5WyE?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
This plugin provides one example implementation of inline editing this can be accomplished in the customizer. Version 0.1 of this plugin from 2014 was a precursor in some ways to selective refresh, specifically in regards to how CSS selectors are associated with customizer settings.
Themes can opt-in to support this plugin’s inline editing within the customizer by assigning the appropriate type to the registered partials:
<pre>
add_action( 'customize_register', function( $wp_customize ) {
 $opt_in_partials = array_filter( array(
 $wp_customize->selective_refresh->get_partial( 'blogname' ),
 $wp_customize->selective_refresh->get_partial( 'blogdescription' )
 ) );
 foreach ( $opt_in_partials as $partial ) {
 $partial->type = 'inline_editable';
 }
}, 100 );
</pre>
Click on the edit shortcut to begin editing the element, with keyboard focus then given to the editable element. If the value has a server-side rendered value (e.g. where PHP filters like <code>wptexturize</code> apply to improve typography), the raw value will be supplied when editing starts. Editing can be completed by clicking out of the editable element, tabbing out of the element (blurring it), or clicking the edit icon which then appears as a “done” checkmark icon. You may also shift-click on an element to edit it.
Currently only basic text fields can currently be edited; styling and any tags added to <code>contentEditable</code> areas will be stripped out. Eventually rich text formatting may be allowed, specifically for integrations with the Text widget (via <a href="https://github.com/xwp/wp-js-widgets" rel="nofollow ugc">JS Widgets</a>) or post content (via <a href="https://github.com/xwp/wp-customize-posts" rel="nofollow ugc">Customize Posts</a>).
The <a href="https://make.wordpress.org/core/2016/02/16/selective-refresh-in-the-customizer/" rel="nofollow ugc">selective refresh</a> writeup from 4.5 concludes with a section on a possible future for it and inline editing:
<blockquote>
If we can eliminate full-page refreshes from being the norm for the Customizer, we can start to introduce controls inline with the preview. If the entire preview does not reload, then the inline controls won’t get destroyed by the refresh with each change. For example, consider a widget control floating immediately next to the widget in the sidebar it is editing. With selective refresh, it will then also be possible to eliminate the Customizer altogether. The Customizer could be available to anyone who is logged in, with the controls being bootstrapped on demand when a user wants to edit a given element. There would be no need to navigate way from a page on the frontend to enter a unique Customizer state: the Customizer would come to the user. Any controls not relevant to being inline could remain in the Customizer pane, but it could slide in only as needed instead of appearing by default. That is to say, selective refresh makes the Customizer a much better framework for implementing frontend editing.
</blockquote>
Development of this plugin is done <a href="https://github.com/xwp/wp-customize-inline-editing" rel="nofollow ugc">on GitHub</a>. Pull requests welcome. Please see <a href="https://github.com/xwp/wp-customize-inline-editing/issues" rel="nofollow ugc">issues</a> reported there before going to the <a href="https://wordpress.org/support/plugin/customize-inline-editing" rel="ugc">plugin forum</a>.

Customize Inline Editing

Makes the whole text editing process smooth. From refresh to postMessage to inline editing awesome transition. Keep up the good work :)



Awesome

Demonstration of how inline editing can be implemented in the customizer.

Globalis

Sometimes happiness is about small things. What about being able to prepare a new version of your content while its original is still online?
Anticipating and preparing the next version of an article which is already online can quickly become a tedious and risky task. Indeed, most publishers will create a brand new post, fill it in, publish it once it’s ready and finally disable the original article.
<h4>Basic features:</h4>
<ul>
<li>creation of a new version of an article in 1 click;</li>
<li>direct access to other pending versions of an article;</li>
<li>update of an article to its new version in 1 click.</li>
</ul>
<h4>Advanced features:</h4>
<ul>
<li>duplication of an article into a brand new independent copy;</li>
<li>hookable 😉 </li>
<li>works with any post types, custom or not</li>
<li>makes coffee (we’re still working on that)</li>
</ul>
<h3>About</h3>
<h4>Hooks</h4>
pnv_duplicata_status_args 
Filter that can be used to alter arguments sent to ‘register_post_status’. 
Default arguments are:
<ul>
<li>
label => Duplicate
</li>
<li>
public => false
</li>
<li>
exclude_from_search => true
</li>
<li>
show_in_admin_all_list => false
</li>
<li>
label_count =>
</li>
<li>
<ul>
<li>singular => Duplicate (%s)</li>
</ul>
</li>
<li>
<ul>
<li>plural => Duplicates (%s)</li>
</ul>
</li>
</ul>
pnv_erase_content_destination 
Filter that can be used to alter $destination array before ‘wp_insert_post’ get called when a copy, duplication or replacement is triggered 
This filter sends 3 other parameters: the $source object (WP_Post instance) and the $copy boolean
pnv_filtered_metas 
Filter that can be used to alter meta names that must not be treated while a post is copied, duplicated or replaced 
The default metas is an array with these values:
<ul>
<li>_pnv_duplicata => true</li>
</ul>
pnv_erase_content 
Action triggered at the end of a copy, duplication or replacement. 
This action sends 4 parameters:
<ul>
<li>
the $source object (WP_Post instance)
</li>
<li>
the $destination array (represents post data)
</li>
<li>
the $copy boolean
</li>
<li>
the destination’s post ID
</li>
</ul>
pnv_action_url_redirect 
Filter that can be used to alter redirect URL after a copy, duplication or replacement. 
The default value is the admin edit page for the destination post (the one that has been saved) 
This filter sends 1 other parameter: the destination post ID 
pnv_{column_name}_column_value 
Filter that can be used to alter the value displayed on the posts list, in the ‘{column_name}’ column. 
This plugin comes with only one custom column for now, ‘duplicata’, so {column_name} will always be ‘duplicata’, and the default value will be the count of duplicates for the post. 
This filter sends 1 other parameter: the post ID
<h4>Thank’s</h4>
The original version of this plugin has been developed by Lionel POINTET (https://github.com/lpointet) who keeps following the project carefully.
A big thank-you to <a href="http://www.groupemoniteur.fr/" rel="nofollow ugc">Groupe Moniteur</a> for which a great part of this development was intended and which accepted enthusiastically to do a completely open source plugin from it. Thank you to <a href="http://uncategorized-creations.com/" rel="nofollow ugc">Uncategorized Creations</a> people, for their regular advice and their perseverance in making WordPress a leading CMS.
<h4>GLOBALIS</h4>
<a href="http://www.globalis-ms.com/" rel="nofollow ugc">GLOBALIS</a> is a web IT consulting company based in Paris, and a pioneer of the PHP and LAMP platform. Since 1997, we have been designing, making and maintaining Internet, intranet or mobile software. We have been working with open source CMS since 2000 and have regularly been using WordPress since 2007.

Prepare New Version

Create the next version of your post while preserving its already online version.

Customize Inline Editing vs Prepare New Version