GeroNikolov

This plugin is great for story tellers which have what to say and most of all, they want to share amazing stories with the world!
The idea of the AINOW plugin is very simple…
You are writing amazing stories for different themes from the world society. But with the time those stories become so many that your readers have lost their path of interest… Some of them even messaged you that your storyline is getting harder for reading…
So you’ve set down and think about what can you do?
The best solution for not losing your readers is to suggest the right stories to the right crowd! But this can be really hard if you had to do it manually… So the solution of this problem is the AINOW plugin which will do this for you, leaving only the great story telling for you!
How it works?
The plugin works really simple. 
You just have to create a new page and put this shortcode – [ainow_list] in its content. 
That will automatically tell the plugin that this page will show your blog posts. 
The shortcode has one attribute in which you can customize the text of the Load More button. It’s load_btn_text and it can be everything that you want it to be!

In the end shortcode looks like that – [ainow_list load_btn_text=”Load More”]
How to write great stories with AINOW?
You can find detailed article about how the AINOW plugin works and how you can use it in the best possible ways for your story <a href="http://dloober.com/writing-stories-ainow-plugin/" rel="nofollow ugc">here</a>.
Note:
The plugin comes with very minimalistic stylization with the idea to fit your design, leaving you to realise your imagination on it!
Demo:
You can find the demo <a href="http://testing.dloober.com/ainow-testing/" rel="nofollow ugc">here</a>.
For Developers:
The AINOW plugin is Open Source which means that you can join the contributions and build your idea on it! You can find the core <a href="https://github.com/Gero0Nikolov/AINOW" rel="nofollow ugc">here</a>.
Basically there aren’t any limits in the world of the AI, so let’s create something amazing, starting from TODAY!

AINow

This plugin will save you time by suggesting the right posts to the right readers.

Scott Reilly

Control the number of posts that appear on the front page, search results, and author, category, tag, custom post type, custom taxonomy, and date archives, independent of each other, including specific archives.
By default, WordPress provides a single configuration setting to control how many posts should be listed in each section of your blog. This value applies for the front page listing, author listings, archive listings, category listings, tag listings, custom post type listings, custom taxonomy listings, and search results. This plugin allows you to override that value for each of those different sections.
Specifically, this plugin allows you to define limits for:
<ul>
<li>Authors archives (the archive listing of posts for any author)</li>
<li>Authors archives non-first-page (when paging through authors archives listings, number of posts listed when not on the first page)</li>
<li>Author archives (the archive listing of posts for any specific author)</li>
<li>Categories archives (the archive listings of posts for any category)</li>
<li>Categories archives non-first-page (when paging through categories archives listings, number of posts listed when not on the first page)</li>
<li>Category archive (the archive listings of posts for any specific category)</li>
<li>Custom post type archives (the archive listings of posts for any specific custom post type)</li>
<li>Custom taxonomy (the archive listings of posts for any specific custom taxonomy)</li>
<li>Day archives (the archive listings of posts for any day)</li>
<li>Day archives non-first-page (when paging through day archives listings, number of posts listed when not on the first page)</li>
<li>Front page (the listing of posts on the front page of the blog)</li>
<li>Front page non-first-page (when paging through front page listings, number of posts listed when not on the first page)</li>
<li>Month archives (the archive listings of posts for any month)</li>
<li>Month archives non-first-page (when paging through month archives listings, number of posts listed when not on the first page)</li>
<li>Search results (the listing of search results)</li>
<li>Search results non-first-page (when paging through search results listings, number of posts listed when not on the first page)</li>
<li>Tags archives (the archive listings of posts for any tag)</li>
<li>Tags archives non-first-page (when paging through tags archives listings, number of posts listed when not on the first page)</li>
<li>Tag archive (the archive listings of posts for any specific tag)</li>
<li>Year archives (the archive listings of posts for any year)</li>
<li>Year archives non-first-page (when paging through year archives listings, number of posts listed when not on the first page)</li>
</ul>
If the limit field is empty or 0 for a particular section type, then the default post limit will apply. If the value is set to -1, then there will be NO limit for that section (meaning ALL posts will be shown). The Archives Limit value is also treated as the default limit for Day, Month, and Year archives, unless those are explicitly defined.
Links: <a href="https://coffee2code.com/wp-plugins/custom-post-limits/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/custom-post-limits/" rel="ugc">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/custom-post-limits/" rel="nofollow ugc">GitHub</a> | <a href="https://coffee2code.com" rel="nofollow ugc">Author Homepage</a>
<h3>Hooks</h3>
The plugin exposes a number of filters for hooking. Typically, code making use of filters should ideally be put into a mu-plugin or site-specific plugin (which is beyond the scope of this readme to explain).
c2c_cpl_enable_all_individual_limits (filter)
The ‘c2c_cpl_enable_all_individual_limits’ hook allows you to filter if individual limits are enabled for all archive types.
The ability to set individual limits (e.g. for per-author or per-category archives) isn’t simply enabled by default because it can have a negative performance impact depending on the number of items. Especially for a something most sites are unlikely to need.
Arguments:
<ul>
<li>$enabled (boolean): Enable individual limits for all archive types? Default false.</li>
</ul>
Example:
<pre><code>// Enable individual limits for all archives for Custom Post Limits plugin.
add_filter( 'c2c_cpl_enable_all_individual_limits', '__return_true' );
</code></pre>
c2c_cpl_enable_all_individual_{$type}_limits (filter)
The ‘c2c_cpl_enable_all_individual_{$type}_limits’ hook allows you to filter if individual limits are enabled for a specific archive type. The dynamic portion of the hook name, <code>$type</code>, refers to the type of archive with constituent individual archives. Can be ‘authors’, ‘categories’, or ‘tags’.
Arguments:
<ul>
<li>$enabled (boolean): Enable individual limits for given archive type? Default false.</li>
</ul>
Example:
<pre><code>// Enable individual limits for author archives for Custom Post Limits plugin.
add_filter( 'c2c_cpl_enable_all_individual_authors_limits', '__return_true' );
</code></pre>

Custom Post Limits

Independently control the number of posts listed on the front page, author/category/custom post type/custom taxonomy/tag archives, search results, etc …

AINow vs Custom Post Limits