Timothy Paustian

This plugin is a Gutenberg block that takes a collection of posts organized by category (book name) and subcategories (chapter names) 
and creates a table of contents from them. You simply choose the root category to use, and the plugin does the rest. Once 
the table of contents is made, you can sort the chapters and posts, and the plugin will remember the order. The plugin also 
creates links to the next and previous posts.
<h3>Source Code</h3>
The Pau Table of Contents Block is a Gutenberg block created as recommended in the Block Editor Handbook 
(https://developer.wordpress.org/block-editor/). As recommended by the handbook, the source code is minified by the 
build process for production. In keeping with the spirit of open source, the unminified code 
for Pau Table of Contents is available at GitHub (https://github.com/paustian/pau-table-of-contents-block/).
If you want to see an example of this used on a live site, check out my textbook Through the Microscope (https://textbookconsortia.com/through-the-microscope-table-of-contents/)
<h3>Minimum Requirements</h3>
<ul>
<li>WordPress version 6.8 or greater.</li>
<li>PHP version 7.4 or greater</li>
<li>MySQL version 5.7 or greater.</li>
</ul>
<h3>Recommended Requirements</h3>
<ul>
<li>Latest WordPress version.</li>
<li>PHP version 8.0 or greater.</li>
<li>MySQL version 8.0 or greater, or MariaDB 10.5 or greater.</li>
</ul>

Pau Table of Contents Block

A Gutenberg block plugin that displays a table of contents generated from Posts organized by a root category and subcategories.

cartpauj

Shortcode Redirect sends visitors from any post or page to another URL. No settings screens, no database tables — just drop it in where you need it.
There are two ways to use it, and both produce the exact same front-end output.
1. The Redirect block (new in 1.1.0)
In the block editor, add the Redirect block from the Widgets category. The block sidebar exposes three simple fields:
<ul>
<li>Destination URL — where the visitor should end up</li>
<li>Seconds to wait — how long to pause before redirecting (<code>0</code> = immediate)</li>
<li>Show “redirecting” message — toggle the visible “Please wait…” line on or off</li>
</ul>
The editor shows a live summary of what the block will do, e.g. “Redirects to https://example.com — after 3 seconds · message shown”. No shortcode syntax to memorize.
2. The classic shortcode
Paste into any post or page:
<pre><code>[redirect url='https://example.com' sec='3']
</code></pre>
Shortcode attributes:
<ul>
<li><code>url</code> — destination URL (required)</li>
<li><code>sec</code> — seconds to wait before redirecting (optional, default <code>0</code>)</li>
<li><code>show_message</code> — set to <code>false</code>, <code>0</code>, <code>no</code>, or <code>off</code> to hide the “redirecting” message (optional, default <code>true</code>, new in 1.1.0)</li>
</ul>
Example with all three:
<pre><code>[redirect url='https://example.com' sec='5' show_message='false']
</code></pre>
Same output either way
Block or shortcode, the front-end renders the same single <code><meta http-equiv="refresh"></code> tag (plus the optional one-line message). No JavaScript. No server-side redirect. No third-party tracking. Existing <code>[redirect]</code> shortcodes from earlier versions continue to work unchanged.
<h4>Features</h4>
<ul>
<li>Block editor support — native “Redirect” block (new in 1.1.0)</li>
<li>Classic shortcode — <code>[redirect]</code> works exactly like it always has</li>
<li>Optional delay — choose how many seconds to wait before redirecting</li>
<li>Silent mode — hide the “redirecting…” message for a clean, blank-page redirect (new in 1.1.0)</li>
<li>Lightweight — a single PHP file plus a small block; no settings, no tables, no dependencies</li>
<li>Backwards compatible — upgrading from 1.0.x is drop-in</li>
</ul>

Shortcode Redirect

Redirect any post or page — with a native block or a classic shortcode. Optional delay. Optional "redirecting" message. Zero configuration.

Pau Table of Contents Block vs Shortcode Redirect