Case studies✦Plate V of VI
Fig. I — The case file, 2018–2020
BEN + Greenlight
BEN manages assets for entertainment marketing worldwide, alongside its branch Greenlight Rights. Two sites, one rebrand — the branch shipped first, and earned the parent company’s build.
01 Overview
BEN is a global company that manages assets for entertainment marketing. Together with its branch, greenlightrights.com, they needed both sites reworked with updated branding.
Two audiences, two marks, one editorial system underneath. The interesting constraint was that the second site had to inherit the first one’s decisions without inheriting its compromises.
The branch site was the argument. The parent site was the verdict.— Studio note, on being hired twice
02 The work
Content model. Custom post types modelling the asset catalogue, so the editorial team described their work in their own vocabulary rather than bending posts and pages into shape.
Custom Gutenberg components. Blocks built in React against the editor’s own APIs — composed by editors, not requested from developers. This is the part that decides whether a rebrand survives its first month.
Custom theme. PHP, HTML and SCSS, carrying the updated branding across both properties while keeping each one’s identity distinct.
03 Two sites, in order
- Site I
Greenlight Rights
The branch, rebuilt first: custom post types, Gutenberg components, and the custom theme that established the pattern.
- Site II
BEN
Having successfully deployed Greenlight Rights, the client hired us again for the parent company’s site — the same approach, applied with a year of hindsight.
04 Outcomes
- Two sites rebranded, Greenlight Rights first, then BEN.
- Custom Gutenberg components in React, built for the editors rather than for us.
- Custom post types modelling the asset catalogue.
- A custom theme in PHP and SCSS, consistent in approach across both builds.
- Hired again — the branch build earned the parent company’s.