Obeyda Ferwana

<ul>
<li>Knowing the number of words within the published post .</li>
<li>Knowing the number of letters within the post.</li>
<li>Knowing the time of reading the publication.</li>
<li>to and is done through the Settings page: </li>
<li>The text of the title is selected by select at the beginning of the post or at the end of the post. </li>
<li>choosing the number of words, number of letters and reading time through Checkboxes .</li>
</ul>
A few notes about the sections above:
<ul>
<li>“Contributors” is a comma separated list of wordpress.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</li>
<li>Stable tag must indicate the Subversion “tag” of the latest stable version</li>
</ul>
Note that the <code>readme.txt</code> value of stable tag is the one that is the defining one for the plugin. 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.
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, your users may not get the correct version of your code.
<h3>A brief Markdown Example</h3>
Markdown is what the parser uses to process much of the readme file.
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>
Links require brackets and parenthesis:
Here’s a link to <a href="https://wordpress.org/" title="Your favorite software" rel="ugc">WordPress</a> and one to <a href="https://daringfireball.net/projects/markdown/syntax" rel="nofollow ugc">Markdown’s Syntax Documentation</a>. Link titles are optional, naturally.
Blockquotes are email style:
<blockquote>
Asterisks for emphasis. Double it up for strong.
</blockquote>
And Backticks for code:
<pre><code><?php code(); ?>
</code></pre>

Word Count

Tis plugin helps the admin to know the number of words and letters within the article and words to determine the reading time of the article.

Christian Gatti

Sort Any Posts is one of the several NutsForPress plugins providing some essential features that WordPress does not offer itself or offers only partially.  
Sort Any Posts allows you to:
<ul>
<li>decide which post or custom post should be orderable</li>
<li>set the order by dragging and dropping post elements into the “sort” page added to the post or post type admin menu</li>
<li>get the posts ordered in frontend, into your blog, your category or archive page</li>
</ul>
Sort Any Posts is full compliant with WPML (you don’t need to translate any option value)
Take a look at the others <a href="https://wordpress.org/plugins/search/nutsforpress/" rel="ugc">NutsForPress Plugins</a>
Whatever is worth doing at all is worth doing well
<h3>Translations</h3>
<ul>
<li>English: default language</li>
<li>Italian: entirely translated</li>
</ul>
<h3>Credits</h3>
<ul>
<li>Very many thanks to <a href="https://dkr.srl/" rel="nofollow ugc">DkR</a> and <a href="https://sviluppoeuropa.it/" rel="nofollow ugc">SviluppoEuropa</a>!</li>
</ul>

NutsForPress Sort Any Post

NutsForPress Sort Any Posts is a simple and lightweight plugin that allows you to sort any kind of posts and show them in the order you've decided.

Word Count vs NutsForPress Sort Any Post