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.

dimitryz

With the Custom Pagination plugin, a user may customize the look of a post’s next and previous links using the HTML editor. It is built by <a href="http://webit.ca" rel="nofollow ugc">WebIT.ca (Dimitry Zolotaryov)</a> and funded by <a href="http://datedaily.com" rel="nofollow ugc">DateDaily.com</a>: an online dating and relationship blog.
The link is created by selecting the text label within a post’s body and clicking the link icon. In the Link URL field, the following values will produce a link to another page:
<ul>
<li>page:next links to the next page</li>
<li>page:prev or page:previous links to the previous page</li>
<li>page:first links to the first page of the post</li>
<li>page:last links to the last page of a post</li>
<li>page:n links to the nth page of a post (e.g. page:2 for the second page)</li>
</ul>
If link is directing to a page that does not exist — for instance page:next on the last page –, the link and the link text do not appear.
All links processed by Custom Pagination will have the added class name ‘page’. If you wish to style such links, in your CSS, add the line:
<pre><code>a.page { /* page style goes here */ }
</code></pre>
For more information, visit the <a href="http://webit.ca/2009/08/custom-pagination-plugin-for-wordpress/" rel="nofollow ugc">Custom Pagination plugin homepage</a>.

Custom Pagination

The Custom Pagination plugin allows a user to insert custom next, previous or numbered page links into a post.

Customize Inline Editing vs Custom Pagination