📦Context Managers

Context managers enrich the global Timber::context() with shared data that's available in every template. They're the quartermaster's store — making sure every template has the supplies it needs before setting sail.

How They Work

Context managers implement the ContextManagerInterface and are registered in config/context-managers.php. During boot, the TimberServiceProvider instantiates each one and hooks them into the timber/context filter.

Every time Timber::context() is called (typically once per request, in a controller's constructor), each registered context manager has a chance to add its data.

The Interface

src/ContextManagers/ContextManagerInterface.php

namespace PressGang\ContextManagers;

interface ContextManagerInterface {
    /**
     * @param array<string, mixed> $context
     * @return array<string, mixed>
     */
    public function add_to_context(array $context): array;
}

Built-in Context Managers

PressGang ships with five context managers out of the box:

SiteContextManager

Adds the Timber Site object and a cache-busted stylesheet URL to the context.

Context keys: site, site.stylesheet

views/layout.twig

<link rel="stylesheet" href="{{ site.stylesheet }}">
<h1>{{ site.name }}</h1>

The stylesheet URL is filterable via pressgang_stylesheet.

MenuContextManager

Adds all registered WordPress navigation menus as Timber Menu objects, keyed by location.

Context keys: menu_{location} (e.g. menu_primary, menu_footer)

views/partials/nav.twig

{% for item in menu_primary.items %}
    <a href="{{ item.link }}">{{ item.title }}</a>
{% endfor %}

Each menu is filterable via pressgang_context_menu_{location}.

ThemeModsContextManager

Adds all WordPress Customizer theme modifications to the theme object.

Context keys: properties on theme (e.g. theme.header_image, theme.custom_logo)

views/partials/header.twig

{% if theme.custom_logo %}
    <img src="{{ theme.custom_logo }}" alt="{{ site.name }}">
{% endif %}

Each value is filterable via pressgang_theme_mod_{key}.

AcfOptionsContextManager

Adds ACF (Advanced Custom Fields) options page fields to the context, converting values to Timber objects where appropriate. Results are cached via wp_cache.

Context key: options

views/partials/footer.twig

{{ options.company_name }}
{{ options.logo.src }}

This manager only runs when ACF is active and config/acf-options.php is configured.

WooCommerceContextManager

Adds WooCommerce-specific data to the context when WooCommerce is active.

Creating a Custom Context Manager

1

Create the class

src/ContextManagers/SocialLinksContextManager.php

namespace MyTheme\ContextManagers;

use PressGang\ContextManagers\ContextManagerInterface;

class SocialLinksContextManager implements ContextManagerInterface {

    public function add_to_context(array $context): array {
        $context['social_links'] = [
            'twitter'  => get_option('social_twitter'),
            'facebook' => get_option('social_facebook'),
            'instagram' => get_option('social_instagram'),
        ];

        return $context;
    }
}

2

Register in config

Add it to your child theme's config/context-managers.php:

config/context-managers.php

return [
    \PressGang\ContextManagers\SiteContextManager::class,
    \PressGang\ContextManagers\MenuContextManager::class,
    \PressGang\ContextManagers\ThemeModsContextManager::class,
    \PressGang\ContextManagers\AcfOptionsContextManager::class,
    \MyTheme\ContextManagers\SocialLinksContextManager::class,
];

3

Use in Twig

views/partials/social.twig

<a href="{{ social_links.twitter }}">Twitter</a>

Important Guidelines

Context managers run on every request — frontend, admin, AJAX, and CLI. Keep them lightweight!

• Cache non-trivial queries. If your context manager fetches data from the database, wrap it in wp_cache_get()/wp_cache_set().

• Only add data needed across many templates. Data specific to a single page should live in the controller, not a context manager.

• Keep it side-effect free. Context managers must not write to the database, send emails, or perform remote requests.

• Don't overwrite built-in Timber context keys like site, request, or user.