Site DNA: taking game websites apart, file by file

I wanted to know exactly how two game studios build their websites, and I mean exactly rather than roughly, with every claim backed by the code they actually ship.

The problem

Official game sites ship as compiled, minified bundles, so screenshots can only show what they look like rather than how they work, and most write-ups of a site’s design end up being guesses.

What I built

I built a pipeline of Node scripts that drives headless Chromium through each site and keeps everything it finds, which covers:

  • Every response the first pages load, archived with its size and SHA-256 digest
  • Screenshots, computed styles and hover changes for every page, on desktop and phone
  • Bundles split into modules and renamed in stages until they read like source
  • Colour, type, spacing and motion measured from the live pages
  • Every interaction driven for real, with what it actually does recorded
  • A handbook that runs inside the site’s own article template, plus a printed PDF edition
Shippedone line, minified
function o(t){var e=document.documentElement,n=e.clientWidth;e.style.fontSize=100*n/2560+"px"}
Readableafter renaming
function setRootFontSize() {
  const width = html.clientWidth
  html.style.fontSize = 100 * width / DESIGN_WIDTH
} // 2560 on desktop, 750 on phones

Illustrative excerpt

Two studies

Zenless Zone Zero

850
responses captured
1,457
modules split out
107
renamed for reading
26
pages, desktop and phone
Repository

Arknights: Endfield

708
modules split out
45
renamed for reading
36
handbook chapters
69
captured screenshots

Nothing invented

Nothing in the handbooks is made up, because each statement is tagged Observed (read from shipped code or responses), Measured (reported by headless Chromium) or Inferred (my own interpretation). If I couldn't prove something, the page says so.

  • Nuxt 2 app, Vue 2.7.4, GSAPObserved
  • Two page trees, picked by deviceObserved
  • 850 responses on the first pagesMeasured
  • What each click actually doesMeasured
  • Anything not proven by eitherInferred

Proving it works

To test the Zenless Zone Zero DNA, I built an example portfolio page as a child site, using nothing but that site’s own stylesheets, markup and dictionary keys, so nothing on it is drawn or styled specifically for it.

The page you're reading right now follows the same idea, except it's built from resend.com’s design DNA.

The studied sites, along with their artwork and code, belong to HoYoverse / COGNOSPHERE and Gryphline, and the studies exist purely to learn how they're built.

C

Calyndrae

Designer and developer

Next case studyAction Sandbox