alexlundin

This is the long description. No limit, and you can use Markdown (as well as in the following sections).
For backwards compatibility, if this section is missing, the full length of the short description will be used, and 
Markdown parsed.
A few notes about the sections above:
<ul>
<li>“Contributors” is a comma separated list of wp.org/wp-plugins.org usernames</li>
<li>“Tags” is a comma separated list of tags that apply to the plugin</li>
<li>“Requires at least” is the lowest version that the plugin will work on</li>
<li>“Tested up to” is the highest version that you’ve successfully used to test the plugin. Note that it might work on 
higher versions… this is just the highest one you’ve verified.</li>
<li>
Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use <code>/trunk/</code> for 
stable.
Note that the <code>readme.txt</code> of the stable tag is the one that is considered the defining one for the plugin, so 
if the <code>/trunk/readme.txt</code> file says that the stable tag is <code>4.3</code>, then it is <code>/tags/4.3/readme.txt</code> that’ll be used 
for displaying information about the plugin. In this situation, the only thing considered from the trunk <code>readme.txt</code> 
is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk <code>readme.txt</code> to reflect changes in 
your in-development version, without having that information incorrectly disclosed about the current stable version 
that lacks those changes — as long as the trunk’s <code>readme.txt</code> points to the correct stable tag.
If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where 
you put the stable version, in order to eliminate any doubt.
</li>
</ul>
<h3>Arbitrary section</h3>
You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated 
plugins where more information needs to be conveyed that doesn’t fit into the categories of “description” or 
“installation.” Arbitrary sections will be shown below the built-in sections outlined above.
<h3>A brief Markdown Example</h3>
Ordered list:
<ol>
<li>Some feature</li>
<li>Another feature</li>
<li>Something else about the plugin</li>
</ol>
Unordered list:
<ul>
<li>something</li>
<li>something else</li>
<li>third thing</li>
</ul>
Here’s a link to <a href="https://wordpress.org/" title="Your favorite software" rel="ugc">WordPress</a> and one to <a href="http://daringfireball.net/projects/markdown/syntax" title="Markdown is what the parser uses to process much of the readme file" rel="nofollow ugc">Markdown’s Syntax Documentation</a>. 
Titles are optional, naturally.
Markdown uses email style notation for blockquotes and I’ve been told:
<blockquote>
Asterisks for emphasis. Double it up for strong.
</blockquote>
<pre><code><?php code(); // goes in backticks ?>
</code></pre>

WP Battle by Alex Lundin

Here is a short description of the plugin.  This should be no more than 150 characters.  No markup here.

OpenWeb Admin

Comments Evolved ( formerly Google+ Comments for WordPress ) makes the comment section tabbed seamlessly adding tabs for G+ Comments, Facebook, Disqus, WordPress Comments, and Trackbacks
If a user is required to create an account with your site before they can comment, you might as well ask them to fetch you a soda from mars. It’s probably not going to happen. However, if you can give them the option to comment with an account they’ve already set up, then you will be much more likely to get some interaction.
**Source Code @ Github: ** <a href="https://github.com/bholtsclaw/comments-evolved" rel="nofollow ugc">comments-evolved@github</a>
Using this plugin or JavaScript to load comments does NOT have a negative effect on your SEO, Google now indexes content ( and specifically comments ) loaded via JavaScript. See <a href="http://blog.optimum7.com/safon/google/google-now-indexing-fb-comments.html" rel="nofollow ugc">this link</a> and also <a href="http://webmasters.stackexchange.com/questions/27042/effect-on-seo-of-lazy-scrolling-on-html-comments" rel="nofollow ugc">this one</a> for more details.
<ul>
<li>You should have <a href="http://plus.google.com/authorship" rel="nofollow ugc">Google Authorship</a> already setup and in use for your site.</li>
<li>I’ve setup a page so if you want to <a href="http://www.wepay.com/donations/brandonholtsclaw" rel="nofollow ugc">Donate</a> to this plugins development, now you can.</li>
</ul>
This plug-in is not endorsed or associated with the Google, Twitter, Disqus, Facebook, WordPress.org, Automattic, or WordPress HelpCenter.

Comments Evolved for WordPress

cool extension
Adds Google and Facebook in no time
Super simple to use!



Simple and nice looking

Comments Evolved ( formerly Google+ Comments for WordPress ) makes the comment section tabbed seamlessly adding tabs for Comments & More

WP Battle by Alex Lundin vs Comments Evolved for WordPress