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.

webdevstudios

Michael Beckwith

pluginize

modemlooper

Brad Williams

John Hawkins

Custom Post Type UI provides an easy-to-use interface for registering and managing custom post types and taxonomies for your website.
<h4>Custom Post Type UI Extended</h4>
CPTUI helps create custom content types, but displaying that content can be a whole new challenge. <a href="https://pluginize.com/plugins/custom-post-type-ui-extended/?utm_source=cptui-desription&utm_medium=text&utm_campaign=wporg" rel="nofollow ugc">Custom Post Type UI Extended</a> was created to help with displaying your crafted content. <a href="https://pluginize.com/cpt-ui-extended-features/?utm_source=cptui-description-examples&utm_medium=text&utm_campaign=wporg" rel="nofollow ugc">View our Layouts page</a> to see available layout examples with Custom Post Type UI Extended.
<h4>Plugin development</h4>
Custom Post Type UI development is managed on GitHub, with official releases published on WordPress.org. The GitHub repo can be found at <a href="https://github.com/WebDevStudios/custom-post-type-ui" rel="nofollow ugc">https://github.com/WebDevStudios/custom-post-type-ui</a>. Please use the WordPress.org support tab for potential bugs, issues, or enhancement ideas.

Custom Post Type UI

Works well, but it's missing a number of CPT options: rest_namespace, capabilities, map_meta_cap, register_meta_box_cb, rewrite[feeds, pages, ep_mask], template, and template_lock. I realize these are not common, but it's a drag when you go to create your third CPT and realize you need to find a different solution that will accommodate one of the missing options. It's no good to have a few registered in CPTUI and a few by hand.

Good, but missing a bunch of options.


There is no documentation. In plugin description there is just a link to so called documentation that is just bunch of tutorial of doing specific stuff that are very scarce and targeted to people who already know how to use it. Nothing for first time users, to learn how to actually begin with plugin, or at least nothing that can be easily found.


One of the worst documented plugins I saw


Thank you very much for this amazing Plugin that serves us since years!


Amazing Plugin


speeds up development and has nice user-friendly UI. It was a nice experience working with this plugin.


really useful


Plugins like these make wordpress worthwile


Great piece of software

Admin UI for creating custom content types like post types and taxonomies

Word Count vs Custom Post Type UI