vicchi

This plugin allows you to refer to a WordPress shortcode within the content of posts and pages without that shortcode being automagically expanded by WordPress. The plugin takes advantage of the fact that the <a href="https://codex.wordpress.org/Shortcode_API" rel="nofollow ugc">WordPress ShortCode API</a> does not support nested shortcodes to allow this plugin’s shortcode to wrap the shortcode being documented.
<blockquote>
The shortcode parser uses a single pass on the post content. This means that if 
 the $content parameter of a shortcode handler contains another shortcode, it won’t 
 be parsed
</blockquote>
The plugin supports both the self closing <code>[shortcode]</code> and enclosing <code>[shortcode]content[/shortcode]</code> forms and supports a short form name of the shortcode, <code>[wp_scs]</code> as well as the more verbose <code>[wp_shortcode_shield]</code> form. For the sake of brevity, the remainder of this documentation will use the <code>[wp_scs]</code> short form name.
If using the self-closing form of the shortcode, you need to supply the name of the shortcode you are documenting using the <code>code</code> attribute but without using the enclosing <code>[</code> and <code>]</code> characters. This is because when parsing shortcodes, WordPress looks for the first occurrence of the ‘]’ character to terminate the shortcode. As a result of this, usage such as
<pre><code>[wp_scs code="[another-shortcode-name]"]
</code></pre>
… WordPress will use the ‘]’ character inside the <code>code</code> attribute to try and terminate the shortcode name, which is not what is desired. Instead, the plugin automagically adds the terminating ‘[‘ and ‘]’ characters to the plugin’s output, so that usage such as
<pre><code>[wp_scs code="another-shortcode-name"]
</code></pre>
… will display [another-shortcode-name] in your post’s of page’s content.
If you are using the enclosing form of the shortcode, you can either supply the shortcode to be documented with or without enclosing ‘[‘ and ‘]’ characters; if they are omitted, the plugin will add them for you, so that usage such as
<pre><code>[wp_scs][another-shortcode-name][/wp_scs]
</code></pre>
… and
<pre><code>[wp_scs]another-shortcode-name[/wp_scs]
</code></pre>
… will display the same results, namely [another-shortcode-name].
Finally a note of caution, you cannot mix the enclosing and self closing form of the plugin’s shortcode within the same post or page; this is not a limitation of the plugin, but the way in which WordPress implements the <a href="https://codex.wordpress.org/Shortcode_API" rel="nofollow ugc">ShortCode API</a> …
<blockquote>
The parser does not handle mixing of enclosing and non-enclosing forms of the same 
 shortcode as you would want it to. For example, if you have:
<code>[myshortcode example='non-enclosing' /] non-enclosed content [myshortcode] enclosed content 
 [/myshortcode]</code>
Instead of being treated as two shortcodes separated by the text ” non-enclosed content “, 
 the parser treats this as a single shortcode enclosing ” non-enclosed content [myshortcode] 
 enclosed content”.
</blockquote>

WP Shortcode Shield

Allows posts and pages to easily document WordPress shortcodes without the shortcode being expanded.

moon0326

WP OpenAPI is a WordPress plugin that generates OpenAPI 3.1.0 compatible documentation for your WordPress REST APIs.
It has two main features.
<ul>
<li>Outputs OpenAPI 3.1.0 spec at /wp-json-openapi</li>
<li>Provides OpenAPI viewer using Stoplight’s awesome Elements viewer </li>
</ul>
You can also export your documentation as a single HTML to host it in a server easily.
See more details at https://github.com/moon0326/wp-openapi

WP OpenAPI


Very useful, we are using this in our docs sites, we have added some filters to correct some stuff and then just load the file vis the API url.  Thanks for this!


Great Work

WP OpenAPI is a WordPress plugin to provide the OpenAPI spec and a beautifu viewer for your WordPress REST API.

WP Shortcode Shield vs WP OpenAPI