InContext

<p>Comments are extremely critical for the success of a blog. All existing blog platform and commenting plugins only let readers add comments all the way at the bottom of a post, out of the context of the content in the post. When you write a long blog post with, say, 10 paragraphs, and readers are commenting on a particular statement or expression in paragraph 3, they have to scroll back and forth to read the context to figure out what the comments are about. The “In-Context Comment” plugin changes that: Now you can add an “In-Context Comment” icon using <in-context-comment:here:tag> (where “tag” is any word or words connected by hyphen ) at any place you want readers to comment on and they will be able to click and open a window to add comments right there, next to the context so other readers can see both the context and the comments in one glance. The comment window automatically closes when a reader clicks the cursor anywhere outside the comment window so it does not interfere with the reading.</p>
<p>This plugin can also help you grow your readership by posting the comments to the commenters’ Facebook and Twitter status updates to bring in new readers to your blog.<br />
You can also configure the “In-Context Comment” plugin to automatically add a comment icon at the end of each paragraph that is longer than a certain number of characters. This auto feature is enabled by default with a minimum character count of 360. Please go to the plugin’s Settings page to change.</p>
<h3>Documentation</h3>
<p>Visit http://wizag.com/incontext.php for example and documentation</p>


In-Context Comment

"In-Context Comment" lets readers leave comments right next to the content being commented, instead of only at the bottom of the blog post

Kaspars

James Collins

<p>Use <a href="https://widgetcontext.com" rel="nofollow ugc">Widget Context</a> to show and hide widgets on certain sections of your site — front page, posts, pages, archives, search, etc. Use targeting by URLs (with wildcard support) for maximum flexibility.</p>
<p><iframe loading="lazy" title="How to hide widgets in WordPress using the Widget Context plugin" width="750" height="422" src="https://www.youtube.com/embed/rEHvqsWoXAE?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></p>
<h4>Premium Support</h4>
<p>Subscribe to our <a href="https://widgetcontext.com/pro" rel="nofollow ugc">Premium Support service</a> and get the PRO 🚀 version of the plugin for free when it’s launched! Your support enables consistent maintenance and new feature development, and is greatly appreciated.</p>
<h4>Contribute</h4>
<ul>
<li>Suggest code improvements <a href="https://github.com/kasparsd/widget-context-wporg" rel="nofollow ugc">on GitHub</a>.</li>
<li>Report bugs and suggestions on <a href="https://wordpress.org/support/plugin/widget-context" rel="ugc">WordPress.org forums</a>.</li>
<li><a href="https://translate.wordpress.org/projects/wp-plugins/widget-context" rel="nofollow ugc">Help translate</a> to your language.</li>
</ul>
<h4>Documentation</h4>
<p>Widget visibility can be configured under individual widget settings under “Appearance <span aria-hidden="true" class="wp-exclude-emoji">→</span> Widgets” in your WordPress administration area or through the widget editing interface in the Customizer.</p>
<h4>Target by URL</h4>
<p>The “Target by URL” is a powerful feature for targeting sections of your website based on the request URLs. It was inspired by a similar feature in the <a href="https://www.drupal.org" rel="nofollow ugc">Drupal CMS</a>.</p>
<p>Use relative URLs such as <code>page/sub-page</code> instead of absolute URLs <code>https://example.com/page/sub-page</code> because relative URLs are more flexible and make the logic portable between different domains and server environments.</p>
<h4>Wildcards</h4>
<p>Use the wildcard symbol <code>*</code> for matching dynamic parts of the URL. For example:</p>
<ul>
<li>
<p><code>topic/widgets/*</code> to match all posts in the widgets category, if your permalink structure is set to <code>/topic/%category%/%postname%</code>.</p>
</li>
<li>
<p><code>page-slug/*</code> to match all child pages of the page-slug parent page.</p>
</li>
<li>
<p>Use a trailing <code>?*</code> to capture URL with all query arguments such as <code>utm_source</code>, etc. For example, for every <code>blog/post-slug</code> also include <code>blog/post-slug?*</code>.</p>
</li>
</ul>
<h4>Exclude by URL</h4>
<p>Specify URLs to ignore even if they’re matched by any of the other context rules. For example, enter <code>example/sub-page</code> to hide a widget on this page even when “All Posts” is selected under “Global Sections”.</p>


Widget Context

Show and hide widgets on specific posts, pages and sections of your site.

In-Context Comment vs Widget Context