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

Phill Brown

<p><strong><a href="https://wordpress.org/extend/plugins/context-manager/" rel="ugc">This plugin has been replaced by Context Manager</a></strong></p>
<p>Context Manager does the same job as Menu Rules, but comes with many more features to save you time and unnecessary coding.</p>
<p>Menu Rules can run alongside Context Manager while you migrate your rules across. <a href="http://twitter.com/phill_brown" rel="nofollow ugc">Speak to me on Twitter</a> if you need any help with the transfer.</p>
<h4>About Menu Rules</h4>
<p>In WordPress there’s no way to apply context to the menu system. Menu Rules solves this problem and gives you a framework to write your own menu extensions.</p>
<h4>Example usage</h4>
<p>You have an e-commerce website that has a custom post type called ‘products’. You have a page that lists products which is listed in your main menu. A user visits the page and the menu item becomes ‘active’. You click through to a product and the menu item loses its active state. This is how to fix it with menu rules:</p>
<ol>
<li><a href="https://wordpress.org/extend/plugins/menu-rules/installation/" rel="ugc">Install</a> the Menu Rules plugin</li>
<li>Add a menu rule</li>
<li>Give it a meaningful name in the title field. This is just for administration purposes</li>
<li>In the conditions field enter <code>is_singular( 'product' )</code></li>
<li>Choose <em>Emulate current page as a child but do not create a menu item.</em> as the menu rule</li>
<li>Find your products page in the menu dropdown</li>
<li>Hit publish</li>
</ol>
<h4>Extending Menu Rules</h4>
<ol>
<li>Create a class that extends <code>Menu_Rules_Handler</code> and includes a <code>handler</code> method.</li>
<li>Write your custom functionality</li>
<li>Register your class using <code>add_action( 'plugins_loaded', create_function( '', 'Menu_Rules::register( "Your_Menu_Rule_Class" );' ) );</code></li>
</ol>
<p>Built-in rules are found in <code>menu-rules/rules/</code></p>
<h4>Support</h4>
<p>If you’re stuck, ask me for help on <a href="http://twitter.com/phill_brown" rel="nofollow ugc">Twitter</a>.</p>


Menu Rules

An extension of the menu system with context-based rules and a flexible framework to write your own.

In-Context Comment vs Menu Rules