launchmind

Display AI-powered Launchmind blog content on your WordPress site.
<h3>Testing</h3>
For WordPress.org Reviewers:
A demo API key is available for testing purposes:
<pre><code>lm_test_demo1234567890
</code></pre>
This key provides access to 6 sample blog articles for testing the plugin functionality.
Test the connection:
<ol>
<li>Install and activate the plugin</li>
<li>Go to Launchmind in the WordPress admin sidebar</li>
<li>Click the Settings tab</li>
<li>Enter the demo API key: <code>lm_test_demo1234567890</code></li>
<li>Click Save Settings</li>
<li>Click Test Connection – should show “Connection successful”</li>
<li>Go to the Articles tab to see 6 sample posts</li>
<li>Add the Gutenberg block (<code>Launchmind Blog</code>) or use shortcode <code>[launchmind_blog]</code> on any page</li>
</ol>
Sample articles included:
<ul>
<li>10 Tips to Boost Your E-commerce Conversion Rate</li>
<li>The Ultimate Guide to SEO for Online Stores</li>
<li>How to Create a Winning Product Description</li>
<li>Email Marketing Strategies That Actually Work</li>
<li>Social Media Marketing for Small Businesses</li>
<li>Customer Retention: How to Keep Customers Coming Back</li>
</ul>
Getting your own API key:
Sign up at <a href="https://launchmind.io" rel="nofollow ugc">launchmind.io</a> to get your personal API key for production use.
<h3>Privacy Policy</h3>
This plugin connects to external Launchmind.io servers to fetch blog content. By using this plugin, you agree to Launchmind’s <a href="https://launchmind.io/terms" rel="nofollow ugc">Terms of Service</a> and <a href="https://launchmind.io/privacy" rel="nofollow ugc">Privacy Policy</a>.
Data transmitted: 
* Your Launchmind API key (for authentication) 
* Content requests (post slugs, language preferences)
Data NOT transmitted: 
* Personal data of your WordPress site visitors 
* WordPress user information 
* Any other site data
All API communication uses HTTPS encryption.

Launchmind Blog

Display AI-powered Launchmind blog content on your WordPress site.

cfischer83

Does your website utilize categories and tags? Does it use custom taxonomies? If so, this plugin will find similar content 
based on all your taxonomies. There are two ways to show related posts within your page.
<ul>
<li>The first way to show related content on your post is to use the widget provided. This only works when is_single() is true</li>
<li>The second way to show similar content on your site is to use the pk_related_return($post->ID); function which can be 
called programmatically anywhere you wish!</li>
</ul>
The Widget included with this plugin gives you the option to limit the amount of posts; it allows you to determine which 
fields to show: Featured Image, Author, Date, and Excerpt (Title is required); it allows you to determine which 
variant of the featured image to show: thumbnail, medium, large, or full. As of version 2.0, you can now decide whether the 
‘similar posts’ sorting prefers posts that are newer or posts that were created closer to the date of the post you’re 
viewing.
If you find the Widget doesn’t meet your needs or is too limiting, you can call the functionality programmatically using 
this function:
<pre><code>pk_related_return($post->ID, $args);
</code></pre>
Where $post->ID is the ID of the post for which you are wanting to show related articles.
The $args parameter is an array with the following values available to you (more coming soon):
<ul>
<li>posts_per_page (int defaults to 5)</li>
<li>thumbnail_size (string consisting of one of these values: “thumbnail”, “medium”, “large”, “full”. Defaults to thumbnail).</li>
<li>sort_prefer (string consisting of one of these values: “newest”, “closest”. Defaults to newest).</li>
</ul>
An example might be:
<pre><code><?php
$args = array (
 'posts_per_page' => 6,
 'thumbnail_size' => 'medium',
 'sort_prefer' => 'closest'
);
</code></pre>
The return value of pk_related_return is an array of objects that includes most of the fields within WordPress’s posts 
table plus permalink and featured image.
Future Additions:
Allow the user to specify only certain content types (posts, pages, custom) in a request. This would allow you to specify 
only products get returned, or only blog posts. This would only be an issue if content types share taxonomies.

Launchmind Blog vs Similar Posts Ontology