jocke_gbg

When creating plugins nowadays it is very common that you want to use AJAX functions to get a better user experience. WordPress has built-in support in admin that can be used on your plugins. However sometimes you need very specific requests to get the result you need. This is a tutorial plugin that shows you a good structure for a starting process of your plugin.
Find more useful tips and plugins: <a href="http://www.ultimatewebtips.com/" title="More WordPress plugins" rel="nofollow ugc">Ultimate web tips</a>

AJAX Tutorial

Simple AJAX tutrial how to build a plugin on a good structure.

clevera

Clevera is an AI-powered product that turns screen recordings into narrated tutorial videos and step-by-step help articles. This plugin links your WordPress site to your Clevera workspace so you can build a public help experience on your site without copying embed codes by hand.
Once connected, editors can browse Clevera projects from inside the WordPress editor and add the Clevera Help Center block (or Elementor widget) to a page, then pick which project to show. Visitors get that project’s categories, screencasts, embedded videos, and related article content. When you update content in Clevera, the on-site experience reflects those changes on the next load — no re-exporting or republishing in WordPress.
<h4>What you can do</h4>
<ul>
<li>Connect your WordPress site to a Clevera workspace in a few clicks</li>
<li>Review a clear connection disclosure and explicitly confirm before any data is sent to Clevera</li>
<li>Browse and select Clevera projects inside the block editor and Elementor (for users with content-editing access)</li>
<li>Render a public help center for the project chosen on that page</li>
<li>Show project categories, screencasts, embedded videos, and related article content</li>
<li>Filter and search screencasts by project, category, or keyword where the UI exposes those controls</li>
<li>Rotate or disconnect the API key from WordPress, or manage the connection from the Clevera side</li>
</ul>
<h4>How the connection works</h4>
The plugin uses a guided setup flow instead of pasting a raw API key. From Settings → Clevera AI you are sent to Clevera to sign in and select a workspace. Clevera issues a short-lived exchange token; the plugin exchanges it for a site API key bound to your site URL. The key can be rotated automatically on a schedule and you can also rotate or disconnect manually.
<h4>Requirements</h4>
<ul>
<li>A Clevera account — <a href="https://clevera.ai/" rel="nofollow ugc">sign up at clevera.ai</a></li>
<li>WordPress 5.8 or later (as required by the plugin)</li>
<li>PHP 7.4 or later</li>
<li>Elementor (optional; required only for the Clevera Help Center Elementor widget)</li>
</ul>
<h3>External services</h3>
This plugin relies on external Clevera services to connect your site and to load help-center content.
By default, the plugin does not start the connection flow until an administrator explicitly confirms the disclosure on the settings screen.
<ol>
<li><code>https://app.clevera.ai</code> 
Used for:</li>
</ol>
* The connection flow between WordPress and Clevera 
* Exchanging the temporary connection token for the site API key 
* Validating the connection 
* Loading project, category, screencast, and article data for connected sites 
* Rotating and disconnecting the site API key
Data sent to <code>app.clevera.ai</code> may include: 
* Site URL 
* Site name 
* Return URL for the connection flow 
* Authorization state token 
* Site API key in authenticated server-to-server requests 
* Selected project and content request parameters needed to load help-center data
This service is contacted: 
* When an administrator connects the plugin 
* When an editor loads Clevera project choices 
* When the public help center loads data for the selected project 
* During scheduled connection validation, key rotation, or disconnect operations
Terms of service: 
* https://www.clevera.ai/terms
<ol>
<li><code>https://share.clevera.ai</code> 
Used for:</li>
</ol>
* Rendering Clevera-hosted embedded videos inside the help center
Data sent to <code>share.clevera.ai</code> depends on the embedded player URL and may include: 
* The embed identifier 
* An embed access token generated by Clevera 
* The selected content language 
* Standard browser request metadata
This service is contacted: 
* When a visitor loads a help center page that displays a Clevera video embed
<h3>Privacy</h3>
Site owners should review their own privacy disclosures if they use the public help center, because visitor browsers may load embedded content and assets from the Clevera domains above.
The plugin’s connection flow is opt-in. An administrator must explicitly confirm the connection disclosure before site URL, site name, return URL, and a signed state token are sent to Clevera. Privacy-related information for the Clevera service is described in the terms linked in External services.

Clevera — AI Tutorial Videos & Help Center

Connect your WordPress site to Clevera. Embed a project help center with AI videos & help articles (Gutenberg block, Elementor).

AJAX Tutorial vs Clevera — AI Tutorial Videos & Help Center