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.

isabel104

Create documentation for any number of products, organized by product, and by sub-headings within each product. You can use this to create instruction guides for just about anything.
This is for you if any of these apply:
<ul>
<li>You need to create software documentation.</li>
<li>You need to create documentation for one or multiple products, and must have the docs organized neatly, by product. </li>
<li>You need to write instruction guides for virtually anything, whether it be products, games, topics, etc. You can label them as “Instructions” instead of “Docs”.</li>
<li>You don’t want to create a separate website for your docs. You simply want to add them on to your current WordPress site.</li>
</ul>
This plugin organizes your documentation articles into a visitor-friendly, browse-able format that fits right into your WordPress site. This takes the headache out of organizing documentation articles and instruction guides.
Built-in SEO
Documentation articles will have schema.org microdata. It adds TechArticle microdata to single Docs, and CollectionPage microdata to Docs archives. You can disable the microdata.
Documentation With a User-Friendly Structure For Your Visitors
The main “Docs Page” will list all the products. Clicking on a product will take you to the docs only for that product.
Each product’s docs are organized into subsections. The subsections list each individual article in that docs section.
A single docs post will have a Table of Contents widget added to the sidebar. This will show a Table of Contents for docs pertaining only to the product which this current single doc belongs to.
Organized Docs works on Multisite WordPress installations, as well as regular WordPress sites.
To Consider
This plugin focuses on 2 priorities: a user-friendly docs structure for your visitors, and fast, optimized pagespeed both on the front and back ends of your site (a very light footprint). So, we omit features that focus on backend ease and bloating. So, there is no drag-and-drop ordering of docs. This plugin uses categories to classify your docs rather than creating a whole new interface for docs.
<a href="https://isabelcastillo.com/docs/creating-docs" rel="nofollow ugc">Quick Start Guide</a>
For support, use the support forum link above.

Organized Docs

Create organized documentation for multiple products, organized by product and by subsections within each product.

WP Shortcode Shield vs Organized Docs