Katsushi Kawamori

<h4>Requires</h4>
<ul>
<li>This plugin only supports execution from the command line using <a href="https://wp-cli.org/" rel="nofollow ugc">WP-CLI</a>.</li>
</ul>
<h4>Generate</h4>
<ul>
<li>Generated static site with WP-CLI command.</li>
<li>Replaces URLs or strings in content.</li>
<li>Supports custom post types.</li>
<li>Outputs the archive page for the year, month, and day.</li>
<li>Outputs category archives.</li>
<li>Outputs tag archives.</li>
<li>Outputs author archives.</li>
<li>Outputs feed.</li>
<li>Outputs categories feed.</li>
<li>Outputs tags feed.</li>
<li>Sitemap by default in WordPress.</li>
<li>Generates a file from a specified URL.</li>
</ul>
<h4>Copy</h4>
<ul>
<li>Copy the files that the following tags in the html read to the static site.</li>
</ul>
<pre><code><a href="...">
<img src="...">
<img srcset="...">
<video src="...">
<audio src="...">
<link href="...">
<script src="...">
<iframe src="...">
<source src="...">
<track src="...">
<object data="...">
<embed src="...">
<script>...</script>
CSS
</code></pre>
<h4>WP-CLI</h4>
<ul>
<li>1st argument(string) : <code>/home/www/localhost.test</code> : output path of full path</li>
<li>2nd argument(string) : <code>https://localhost.test</code> : url of output homepage</li>
<li>optional argument1(string) : <code>--cb1="site.com" --ca1="localhost.test"</code> : <code>cb1</code> -> Original string | <code>ca1</code> -> Changed string</li>
<li>optional argument2(string) : <code>--cb2="/wordpress" --ca2="/"</code> : <code>cb2</code> -> Original string | <code>ca2</code> -> Changed string</li>
<li>optional argument3(bool) : <code>--s</code> : Only arguments 4-7, which directly specify the URL and file name, are executed.</li>
<li>optional argument4(string) : <code>--file1="ja/feed/index.xml" --orgurl1="https://site.com/ja/feed/"</code> : <code>file1</code> -> Output filename | <code>orgurl1</code> -> Original url</li>
<li>optional argument5(string) : <code>--file2="ja/category/whatsnew-ja/feed/index.xml" --orgur2="https://site.com/ja/category/whatsnew-ja/feed/"</code> : <code>file2</code> -> Output filename | <code>orgurl2</code> -> Original url</li>
<li>optional argument6(string) : <code>--file3="feed/googleimagesitemap/index.xml" --orgurl3="https://site.com/feed/googleimagesitemap/"</code> : <code>file3</code> -> Output filename | <code>orgurl3</code> -> Original url</li>
<li>optional argument7(string) : <code>--file4="feed/googlevideossitemap/index.xml" --orgur4="https://site.com/feed/googlevideossitemap/"</code> : <code>file4</code> -> Output filename | <code>orgurl4</code> -> Original url</li>
<li>
<p>optional argument8(bool) : <code>--c</code> : Outputs file copy status to the console.</p>
</li>
<li>
<p>Example1 <code>wp static /home/www/localhost.test https://localhost.test</code></p>
</li>
<li>
<p>Example2 <code>wp static /home/www/localhost.test https://localhost.test --cb1="site.com" --ca1="localhost.test" --cb2="/wordpress" --ca2="/"</code><br />
In the html or xml, the original home page is converted to “https://localhost.test”, “site.com” is converted to “localhost.test”, and “/wordpress” is converted to “/”.</p>
</li>
</ul>


Static Site Generator

Dropndot Solutions

<p>The <strong>Content Revalidation Tracker</strong> plugin seamlessly connects your WordPress site with your frontend framework (such as <strong>Next.js</strong>, <strong>Nuxt</strong>, or <strong>Gatsby</strong>) to trigger revalidation via a secure API endpoint every time content changes — ensuring your site always serves the most up-to-date pages.</p>
<p>This plugin is ideal for <strong>headless WordPress</strong> setups that use static site generation or incremental static regeneration. Whenever you update, publish, or delete posts, pages, or taxonomies, the plugin automatically sends a secure API call to your frontend to revalidate the affected pages.</p>
<h3>Key Features</h3>
<ul>
<li><strong>Automatic Revalidation</strong> – Triggers a revalidation request whenever a post, user, or taxonomy is created, updated, trashed, or deleted.</li>
<li><strong>Custom Prefix Mapping (New in v2)</strong> – Define custom URL prefixes for your post types and taxonomies to match your frontend routing structure.</li>
<li><strong>Granular Configuration</strong> – Choose which post types and taxonomies are revalidated via filters.</li>
<li><strong>Secure API Communication</strong> – Use a secret key and domain configuration to ensure authorized revalidation requests.</li>
<li><strong>Admin Test Tool (New in v2)</strong> – Test revalidation manually from the settings page to confirm configuration.</li>
<li><strong>Developer Friendly</strong> – Includes hooks and filters for advanced customization.</li>
</ul>
<h3>Ideal For</h3>
<ul>
<li>WordPress sites powered by <strong>Next.js</strong>, <strong>Nuxt</strong>, or other static/hybrid frameworks.</li>
<li>Developers who want <strong>automated page revalidation</strong> after content changes.</li>
<li>Headless WordPress sites that require fast and fresh content delivery.</li>
</ul>
<h3>Support</h3>
<p>For support and troubleshooting, please visit <a href="https://dropndot.com" rel="nofollow ugc">Dropndot Solutions</a>.</p>


Content Revalidation Tracker

Auto-triggers frontend revalidation on post, page, user, or taxonomy updates. Ideal for Next.js and headless WordPress setups.

Static Site Generator vs Content Revalidation Tracker