PowieT

Create textblocks, areas, sections or other default content and insert it into your pages using a shortcode. So you can simple update standard text. Ultimate Plugin if you have always same content on many posts or pages. Simple update the TextBlox post, and all content is changed on the pages that includes that TextBlox content.
To insert a TextBlox content on a page or post include Shortcode: [textblox id=123]. You can Pick the right content with the Picker in TinyMCE, where all TextBlox are listed.
<h4>Features:</h4>
creates a simple custom post style 
tinymce button to seelect content for simple shortcode creation
<h4>Documentation</h4>
Basic example:
[textblox id=”123″] where 123 is the ID of the TextBlox Post ID. 
This shortcode will show the text inside your page
<h4>Support</h4>
Support Forum @ <a href="https://forum.powie.de" rel="nofollow ugc">powie.de</a>

Powie's TextBlox

Create Textblocks and insert it into your pages using a shortcode. You can very simple update standard text

arnaudpf

This is the long description. No limit, and you can use Markdown (as well as in the following sections).
For backwards compatibility, if this section is missing, the full length of the short description will be used, and 
Markdown parsed.
A few notes about the sections above:
<ul>
<li>“Contributors” is a comma separated list of wordpress.org usernames</li>
<li>“Tags” is a comma separated list of tags that apply to the plugin</li>
<li>“Requires at least” is the lowest version that the plugin will work on</li>
<li>“Tested up to” is the highest version that you’ve successfully used to test the plugin. Note that it might work on 
higher versions… this is just the highest one you’ve verified.</li>
<li>
Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use <code>/trunk/</code> for 
stable.
Note that the <code>readme.txt</code> of the stable tag is the one that is considered the defining one for the plugin, so 
if the <code>/trunk/readme.txt</code> file says that the stable tag is <code>4.3</code>, then it is <code>/tags/4.3/readme.txt</code> that’ll be used 
for displaying information about the plugin. In this situation, the only thing considered from the trunk <code>readme.txt</code> 
is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk <code>readme.txt</code> to reflect changes in 
your in-development version, without having that information incorrectly disclosed about the current stable version 
that lacks those changes — as long as the trunk’s <code>readme.txt</code> points to the correct stable tag.
If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where 
you put the stable version, in order to eliminate any doubt.
</li>
</ul>
<h3>A brief Markdown Example</h3>
Ordered list:
<ol>
<li>Some feature</li>
<li>Another feature</li>
<li>Something else about the plugin</li>
</ol>
Unordered list:
<ul>
<li>something</li>
<li>something else</li>
<li>third thing</li>
</ul>
Here’s a link to <a href="https://wordpress.org/" title="Your favorite software" rel="ugc">WordPress</a> and one to <a href="https://daringfireball.net/projects/markdown/syntax" title="Markdown is what the parser uses to process much of the readme file" rel="nofollow ugc">Markdown’s Syntax Documentation</a>. 
Titles are optional, naturally.
Markdown uses email style notation for blockquotes and I’ve been told:
<blockquote>
Asterisks for emphasis. Double it up for strong.
</blockquote>
<pre><code><?php code(); // goes in backticks ?>
</code></pre>

Delivery Area

A WooCommerce extention that allows you to define one custom delivery area by drawing polygons on a Google Map !

Powie's TextBlox vs Delivery Area