The Rite Sites

With the increasing popularity of blocks, developers and store owners alike have been finding some templating features missing normally available through the use of PHP and <a href="https://developer.wordpress.org/plugins/hooks/" rel="nofollow ugc">WordPress Hooks</a>. 
The WordPress community is <a href="https://www.npmjs.com/package/@wordpress/hooks" rel="nofollow ugc">hard at work</a> to create the extensibility tools and framework that exists in PHP into javascript, but some of the tools are not quite there!
This plugin creates a couple new shortcodes to help bridge the gap temporarily, as well as help users/admins with “templating” without going into your theme or plugins.
The first shortcode is in relation to <a href="https://developer.wordpress.org/plugins/hooks/actions/" rel="nofollow ugc">WordPress Actions</a> and aptly follows the parameter naming convention.
<pre><code>[action_runner_trs name="woocommerce_before_cart"]
</code></pre>
The second shortcode, in relation to <a href="https://developer.wordpress.org/plugins/hooks/filters/" rel="nofollow ugc">WordPress Filters</a>
<pre><code>[filter_runner_trs name="woocommerce_shipping_estimate_html" content="Shipping options will be updated during checkout."]
</code></pre>
There are serious limitations these shortcodes have to offer users. The functions do_action() and apply_filters() can have complex code attached to them, and may rely on global variables that are typically accessible on pages the Hooks have existed on. 
The code is written in a way that even in the block editor, the shortcodes will not attempt to execute in the administrative side of your website. This is especially notable as the Block Editor attempts to render the code of a shortcode as a preview and writing in the database as post_content. 
We recommend users to put this plugin on a staging server and do a test of the specific Hooks you would like to use on the applicable page(s) as to not break any user experiences.
Originally designed to work with the <a href="https://wordpress.org/plugins/woo-gutenberg-products-block/" rel="ugc">WooCommerce Blocks</a> Cart and Checkout pages, we needed to enable users to have the message that notified users can apply their <a href="https://woocommerce.com/products/woocommerce-points-and-rewards/" rel="nofollow ugc">Points and Rewards</a>, 
it also works with plugins that hook into upsell actions or couponing like <a href="https://www.theritesites.com/plugins/pretty-coupons-for-woocommerce/" rel="nofollow ugc">Pretty Coupons</a>, <a href="https://woocommerce.com/products/smart-coupons/" rel="nofollow ugc">Smart Coupon</a>, or even your own custom action, which can be created on the fly!
This plugin pairs nicely with getting custom solutions to your front end quickly for testing or quick notices on your website, especially when using a snippets plugin.

Action Runner by The Rite Sites

New Blocks can often ignore action and filter hooks in php or theme templates. This plugin hopes to solve that using shortcodes!

abigegg

Hatch is a helper library for developers which makes it more pleasant to build websites using Timber, Advanced Custom Fields Pro and other common plugins.
<h3>What is this thing?</h3>
Hatch is a helper library for developers which makes it more pleasant to build websites using Timber, Advanced Custom Fields Pro and other common plugins.
<h3>Requirements</h3>
Timber (latest version.)
<h3>A better way to use Timber</h3>
Using <a href="https://en-gb.wordpress.org/plugins/timber-library/" rel="nofollow ugc">Timber</a> we can use Twig templates to build our sites rather than PHP.
Typically we set up a Timber context like this:
<pre><code>$context = Timber::get_context();

$context['post'] = Timber::get_post();

function website_get_related_posts() {
 // do something fancy here

 return [];
}

$context['related_posts'] = website_get_related_posts();

Timber::render( 'post.twig', $context );
</code></pre>
This is fine but it can get a bit mucky – especially if we have complicated page templates with lots of variables.
Hatch provides a tidier way of setting up contexts for Timber and other popular libraries:
<pre><code>// 'post' is already added by default

Hatch::add_context( 'related_posts', function() {
 // do something fancy
 return [];
} );

Hatch::render( 'post.twig' ); // no need to pass $context in 
</code></pre>
More & better documentation to come! Look in abe-hatch.php for more info
<h3>License</h3>
Copyright 2020 A Big Egg (David Hewitson Ltd)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.%

Hatch

Hatch is a helper library for developers which makes it more pleasant to build websites using Timber, Advanced Custom Fields Pro and other common plug …

Action Runner by The Rite Sites vs Hatch