Bunting for Craft CMS

Bunting is a Craft 6 plugin. Craft 6 is still in beta, and so is Bunting (6.0.0-beta.1) — try it on staging first and use caution on production sites.

Craft 6 · Beta — use caution on production

Ship it dark. Switch it on in the CP.

Bunting puts Laravel Pennant feature flags in the Craft 6 control panel. Merge the new navigation behind a flag, turn it on for your staff group, then for 10% of signed-in visitors, then for the French site — and if anything goes wrong, switch it off on production without a deploy.

Bunting

One flag, everywhere you check it

Twig and Blade get the same answers — Blade through Pennant's own @feature directive. App code keeps using Feature::active(), and routes can require a flag.

twig
{# Twig #}
{% if feature('new-nav') %}
  {% include '_nav/new' %}
{% endif %}
{% requireFeature 'new-checkout' %}   {# 404 while off #}

{{-- Blade --}}
@feature('new-nav')
  @include('_nav.new')
@endfeature

// PHP and routes
Feature::active('new-nav');
Route::get('beta', BetaController::class)->middleware('bunting:new-nav');

Features

Flags that deploy with your code, roll out from the control panel, and answer the same way in every template engine.

Roll out the way you launch

Off, on for everyone, or by rules: user groups first, then a percentage of everyone else who's signed in. Percentages are sticky — each person keeps their place, so raising the number only adds people.

Per site, for multi-site launches

Every site can follow the flag or have its own mode: on for the French site, off everywhere else, or a 25% rollout in one market only.

Flippable on production

A flag's definition lives in project config, so it ships with the code that checks it. Its rollout lives in the database, so you can switch it off on production even with admin changes disallowed.

Overrides, previews and a “why” for every answer

Force a flag on or off for one person. Admins preview any page with ?bunting-preview=new-nav:on for their own session only. Check a user tells you whether a flag is on for someone, on a site, and which rule decided.

Gate pages, routes and conditions

List a flag's URIs and they 404 while it's off — every spelling of the URL. Laravel routes take a bunting:<flag> middleware, and element conditions get a “Feature flag is on” rule.

An audit log, and GraphQL that tells only what it should

Every change is recorded with who made it and what changed. Headless front ends read buntingFlags — the resolved value of public flags only, one schema permission per flag, never cached, never the rules.

Frequently Asked Questions

The questions worth answering before you install it.

Try it on staging today

Bunting is free. It's a Craft 6 beta plugin on a beta CMS — start on a development or staging site and use caution on production.

More plugins

Pairs well with Bunting