Bark: Twig implementation for WordPress. This is an extension to the Twig templating syntax to make theming WordPress fast, safe, and easy to read.
Bark uses the same template files that WordPress naturally selects (index.php, page.php, single.php, etc...) but you can designate whether or not the template file should be rendered by the twig engine. This allows you to have some templates be traditional PHP and retrofit older themes with twig gradually.
To process a template file with twig, it should contain "{%" or "{{" opening tags. This is the simplies way, since you can't really do much with twig without those tokens. If by chance, you are using PHP to display a twig code example and want to prevent this template from being processed by the twig engine, add a php "disable_twig" comment in the file:
<?php
// This file contains twig syntax examples like {% this } or {{ this }} in it,
// but should not be processed by the twig engine.
// Add the disable_twig PHP comment to prevent Twig from compiling the file.
/* disable_twig */
?>Twig eliminates the need for before and after includes like get_header, get_footer or anything with get_template_part. Instead, all Twig templates are complete HTML structures. Starting with a common root template is simple with the {% extend %} tag. This is similar to subclassing in object-oriented programming.
// base.twig
<!Doctype {% block doctype 'html' %}>
<html>
<head>
{% block head %}
<title>{% block title 'default title' %}</title>
{% block meta %}
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="referrer" content="always">
{% endblock %}
{% block head_icons '' %}
{{ wp_head() }}
{% endblock %}
</head>
<body {{ body_class() }}>
{{ do_action('neh_after_body_open') }}
{% block content '' %}
{% block footer '' %}
{{ wp_footer() }}
</body>
</html>Blocks are areas in a template that can be overridden by another template that either extends or embeds this template. It gives a designer an easy way to include default content so a theme never looks empty, but with the expectation that it will be replaced by a more specific template later. Blocks are the primary feature that makes twig templates reusable. This is an example of a WordPress template (index.php) that extends the root template above (base.twig). Any block that is not overridden in this "child template" will have present the content from the parent template.
// index.php
{% extends "base.twig" %}
{% block title %}Title for this page or template{% endblock %}
{% block content %}
<h1>Content Goes Here</h1>
{% endblock %}In this example I'm replacing the "content" and "title" blocks, but leaving the rest of the base template as-is. This is a much better way to have a common root template across all of your template files than using get_header() and get_footer().
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent