Entertainment
Campaign and franchise sites that spike hard on launch night, hold, and are retired on a schedule.
A trailer drops, an episode airs, a nomination lands, and everyone arrives in the same minute. We build campaign, title and franchise sites on Drupal, publish them as static files at the edge so the spike is absorbed, handle media with the rights in mind, and take them down cleanly when the campaign ends.
Talk about your next launch- Static output that absorbs an awards-night spike
- Launch sites built and retired on a schedule
- Rights-aware media handling
What an entertainment platform has to do
Hold at nine-oh-one when the trailer drops at nine. Serve video, stills and key art that someone else owns the rights to, in the territories and windows the contract allows. Look like the title, not like the studio's last site. Launch on a date that will not move, and disappear on another, without leaving a decade of dead microsites behind. And meet an accessibility standard, because a fan with a screen reader is still a fan.
What we do for entertainment
We build campaign, title and franchise sites on Drupal and publish them as static files on an edge network, so the spike hits the edge and never reaches a server. The CMS stays private for the marketing team. Media is handled with rights metadata attached: which territory, which window, which credit, so an expired asset comes down on the day. Each site launches on its date, runs at WCAG 2.2 AA, and is retired on a schedule with redirects, not left to rot. The same platform serves the next title with a new skin.
How we work with studios and labels
A launch has a date, so the plan runs backward from it: the content model and design system for the franchise first, then the title's skin, then the assets with their rights, then a load test at the spike you expect and one beyond it. Launch day is watched by a named engineer. Afterwards, the site runs at almost no cost until its retirement date, when it is archived and redirected.
Why now
Static delivery at the edge has made the launch-night spike a solved problem, at a cost close to nothing per site. Core Web Vitals now measure responsiveness with Interaction to Next Paint, since March 12, 2024, which punishes the heavy, script-laden campaign page. WCAG 2.2 is the standard partners and platforms ask about. And Drupal 10 ends on December 9, 2026, so a franchise platform on an old version has a date of its own.
The numbers behind a launch
0
Public servers on launch night
The site is files on an edge network; the spike never reaches a server. This site runs the same way.
Static & edge delivery200 ms
INP for a "good" page
Interaction to Next Paint, a Core Web Vital since March 12, 2024. Heavy campaign pages fail it.
INP on web.dev1
Platform for every title
One franchise platform; each title is a skin, a set of assets and two dates.
Dec 9, 2026
Drupal 10 end of life
Planned to coincide with the release of Drupal 12.
Drupal core release scheduleI want to …
hold on launch night
The site as static files at the edge, load tested at the spike you expect and one beyond it, with a named engineer watching the launch.
- Static output, invalidated on publish, served from the nearest edge
- Load tested at the peak you have seen, then double
- A named engineer on the night
build a franchise platform, not another microsite
One Drupal platform with a content model and design system for the franchise; each title is a skin, a set of assets and a launch date.
- A content model for titles, talent, episodes, events and assets
- A design system that holds the franchise and lets each title differ
- A new title in days, not a project
handle media with the rights attached
Video, stills and key art carry their territory, window and credit, so an expired asset comes down on the day and a wrong-territory asset never goes up.
- Rights metadata on every asset, enforced by the platform
- Territory and window rules in the delivery, not in a spreadsheet
- Credits rendered where the contract says
retire campaigns without leaving wreckage
A site launches on one date and is archived on another, with redirects, so a decade of dead microsites never accumulates.
- A retirement date set at launch
- Archive and redirect on the day, automatically
- A franchise home that outlives every campaign
keep campaign pages fast
Trailers, galleries and third-party scripts make heavy pages. We keep Core Web Vitals green, INP included, under load.
- A performance audit with the scripts ranked by cost
- Media delivered at the right size for the device
- Numbers before and after, in writing
make it accessible to every fan
WCAG 2.2 AA on a campaign site: captions, keyboard paths, contrast over key art, and motion that respects the reduce-motion setting.
- An audit with a screen reader on the real pages
- Fixes in the design system, so every title inherits them
- A conformance statement the partner can see
A launch, backward from the date
The date does not move, so the plan runs from it. Decisions above the line, the steps that run on every build below.
Launch night is rehearsed at full load before it happens. The retirement date is set the same day as the launch date.
What is changing for entertainment
Checked on web.dev, w3.org and drupal.org on September 12, 2026.
The spike is a solved problem
Static files at the edge absorb launch night at a cost close to nothing per site. The server that used to fall over is gone.
Heavy pages are measured
Interaction to Next Paint has been a Core Web Vital since March 12, 2024, and 200 milliseconds is the bar. Trailers, galleries and third-party scripts have to earn their place.
Rights live in the metadata
Territory, window and credit attached to every asset, enforced by the platform, is what keeps a campaign out of trouble on the day an asset expires.
Drupal 10 ends in December
December 9, 2026, alongside the planned release of Drupal 12. A franchise platform on an old version has a date of its own.
Services for entertainment
The three most studios and labels buy first.
-
Static & edge delivery
Editors work in Drupal as always; on publish the site becomes plain files on a content delivery network, so the public never touches a server, a database or a login form. Almost nothing to attack, pages from the nearest edge, and this very site is built this way.
-
Drupal development
New builds, major-version upgrades, module and theme work, and migrations from Drupal 7 onward. Every site we build is one we can keep patched, accessible and on a supported version for years, because that is the job after launch.
-
Cloud engineering
We design and run the cloud your platform lives on, in your own account, as code, with monitoring, patching and a monthly cost review in writing. We do not resell hosting, and everything we build is documented so the next engineer can run it.
Tell us about the launch.
The date, the spike you expect, the assets and their rights, and what the last launch taught you. We come back with what we would do first and what it would take.
Talk about your next launch