MikeShaw217

<p>This plugin provides a simple way for you to use the <a href="http://twig.sensiolabs.org/" rel="nofollow ugc">Twig templating engine</a> with <a href="https://wordpress.org/" rel="ugc">WordPress</a> themes. A problem with WordPress themes is that it is very easy to create templates that are a mess of PHP and HTML. This isn’t good for working with neither does it provide a separation of concerns. The <a href="http://twig.sensiolabs.org/" rel="nofollow ugc">Twig templating engine</a> is a great engine that allows you to separate out getting & manipulating your data and rendering it out. You create your themes in the same way as before, only you render a template instead of using PHP within your page structure.</p>
<p>The Installation section provides the steps to using this plugin with your theme.</p>
<p>In the Other Notes section, there is an easy reference for the different functions/filters and what they can be used for.</p>
<p>For Twig, the <a href="http://twig.sensiolabs.org/documentation" rel="nofollow ugc">Twig documentation</a> is the best resource I can offer. It is extremely well documented.</p>
<h3>Functions and Filters</h3>
<p></p>
<h4>Functions</h4>
<p></p>
<pre><code>twigpress_render_twig_template($vals = array(), $template = false, $echo = true)
</code></pre>
<p>Calling this function renders a <code>$template</code> with the values passed in <code>$vals</code>. You can also choose a specific template to render and whether you would like to echo the template or simply return it.</p>
<p>There is no need to explicitly set the <code>$template</code> name. If this is left to the default, the plugin will look for a template with the same name as the PHP file being rendered (with a ‘.twig’ extension). For example, if <code>front-page.php</code> is being rendered the plugin will attempt to find <code>front-page.twig</code>.</p>
<p>If you wish to simply return the rendered template, set <code>$echo</code> to <code>false</code>.</p>
<p></p>
<pre><code>twigpress_get_the_content()
</code></pre>
<p>Use this function to get the content for the post you are dealing with. If you use <code>get_the_content</code>, WordPress returns the unformatted content and the <code>the_content</code> filter is not applied. <code>twigpress_get_the_content()</code> takes care of both of these tasks.</p>
<p></p>
<h4>Filters</h4>
<p></p>
<pre><code>twigpress_twig_site_variables
</code></pre>
<p>This filter is applied when the plugin is instantiated, on the ‘init’ action, and allows you to alter the array of variables that are passed to the Twig environment when it is first created. As such, these variables are available to all templates. This filter is best suited for site-wide information. For post-specific variables, use the <code>twigpress_twig_post_template_vars</code> filter.</p>
<p>Defaults:</p>
<pre><code>'site' => array(
    'lang_attributes' => get_bloginfo('language'),
    'charset' => get_bloginfo('charset'),
    'url' => get_bloginfo('url'),
    'stylesheet_directory' => get_stylesheet_directory_uri(),
    'title' => get_bloginfo('name'),
    'description' => get_bloginfo('description')
)
</code></pre>
<p>In templates these would be accessible through, for example, <code>{{ site.stylesheet_directory }}</code>.</p>
<p></p>
<pre><code>twigpress_twig_global_functions
</code></pre>
<p>There will be times when you need to use PHP functions in your templates, and there is no way to capture their content to pass to the template when it is rendered. This filter gives you access to the array of functions that are added to the Twig environment, making them available for calling in your templates.</p>
<p>Defaults: <code>wp_head()</code>, <code>wp_footer()</code>, <code>wp_title()</code>, <code>body_class()</code>, <code>wp_nav_menu()</code></p>
<p></p>
<pre><code>twigpress_twig_post_template_vars
</code></pre>
<p>This filter is applied to your passed array of <code>$vars</code> immediately before the template is rendered. This filter is ideal for when you have a set of default variables you wish to include in every template, but are related to posts not the entire site.</p>


TwigPress

This plugin provides a simple way for you to use the Twig templating system within WordPress themes.

dweipert

<h3>Features</h3>
<ul>
<li>adds a metabox to configurable Post-Types to create and edit Twig templates</li>
<li>adds Twig support to the WP Theme & Plugin editors
<ul>
<li>you can even customize the CodeMirror theme</li>
</ul>
</li>
</ul>
<h3>Plugin Dependencies</h3>
<ul>
<li>https://wordpress.org/plugins/timber-library/</li>
<li>https://wordpress.org/plugins/classic-editor/</li>
</ul>
<h3>How to use the MetaBox Feature</h3>
<p>The plugin uses the path defined in <code>Timber::$locations</code> as the templates path or falls back to the uploads folder if none is provided.</p>
<p>Either adjust your <code>Timber::render('page.twig', $context)</code>-functions like this:</p>
<pre><code>$filenames = [TimberEditor::getTemplateFilename(), 'page.twig'];
Timber::render($filenames, $context);
</code></pre>
<p>like this</p>
<pre><code>TimberEditor::render('page.twig', $context);
# 'page.twig' serves as a fallback if the current posts's template doesn't exist
</code></pre>
<p>or like this</p>
<pre><code>TimberEditor::renderPost('page.twig', $context);
# renderPost() automatically adds ['post' => new Timber\Post()] to the $context
</code></pre>


Editor for Timber

Page, Theme & Plugin Editor Extension for Timber http://www.upstatement.com/timber/

TwigPress vs Editor for Timber