DV.OS 8.X/WORK/THIS WEBSITE
Skip to the case study
Digital Vision
~/digital-vision/work/this-website.md

Website · wearedigitalvision.com

A studio site that plays.
Built the way I build everything else.

~/digital-vision/work/walkthrough.md

Walk through it

Tap the pulsing marker, or use Next.

Open it full screen →

~/digital-vision/work/brief.md

The brief

wearedigitalvision.com is the front door of a small studio in Wales. It has to start conversations with people who give it ten seconds on a phone, and show that the studio builds real, finished things. It started in May 2026 as a 1990s desktop on warm paper and has grown one dated decision at a time.

Most studio sites look alike: a hero, three service cards, a logo wall. A one-person studio cannot win on that template, and the people it wants to reach can tell when a site was put together from defaults.

So the site had to be made like the things the studio builds: small, playable and finished, with every claim on it true.

  • Work on a phone first, for people arriving from a post or a shared link.
  • Lead to the real pages, not replace them.
  • No invented numbers, reviews or followers.
  • Anything playful is labelled: games say GAME, counters say score.
~/digital-vision/work/build.md

The build

On a laptop the homepage is a desktop: folders down both sides, windows with title bars, a sticky note with the house motto. Every inner page uses the same window on the same paper, so the site feels like one place.

On a phone the desktop would be cramped, so phones open on the Feed instead: story bubbles, filters and posts, shaped like the apps people already scroll. Some posts are small games and toys, built on one shared engine. A switch at the top goes back to the folders.

Around that sit a blog in series, sticker sheets from the studio's own sets, a games folder and pages for each service. Each new piece was added when it earned its place, and the commit history shows when.

~/digital-vision/work/result.md

Where it stands

The site is live, deployed by hand after each change and checked on the live address. It is also where the studio tries ideas before using them for clients: the walkthroughs on these case study pages, the motion layer and the form protections all started here.

  • 180commits since the first one on 7 May 2026
  • 55pages in the sitemap
  • 0cookies set
  • 7.7days of build time, from the studio’s work log (calls and planning not counted)

The story of the rebrand is in A new brand, a new website. Have a look round: stickers, games, blog.

~/digital-vision/work/design.md

Design decisions

The palette is warm paper, ink, coral and amber, with no gradients. Depth comes from paper tones and a hard three-pixel ink shadow rather than blur, which keeps the 1990s desktop honest and keeps one accent colour meaning something when it appears.

Type does the rest of the work. Headings are set in a dot-matrix face, window chrome and labels in a pixel font, body copy in Plus Jakarta Sans for easy reading, and sticky notes in a handwritten face. Each face has one job, so the retro parts never get in the way of reading.

Motion is small and optional. Windows rise into place as they scroll in, headings type in with a stepped wipe, and stickers can be picked up and moved with a mouse. All of it sits behind the reduced-motion preference, and without the script nothing is hidden.

~/digital-vision/work/stack.md

Architecture

The site is static HTML, CSS and plain JavaScript, with no framework and no build step. For a content site that changes a page at a time, that means nothing to upgrade, nothing to break between deploys, and pages that load fast on a phone.

The Feed runs on one small engine: one animation loop and one input router, with each playable post a separate module that knows how to reset, step, draw and respond to taps and keys. Sounds are generated in the browser rather than downloaded. Phones narrower than 640 pixels are sent to the Feed; crawlers and anyone who picks the folders view are not.

Two serverless functions handle the forms: the contact form and a short questionnaire with an optional document upload. Both validate every field on the server, trim and cap its length, and send the message by email through Resend. The recipient is fixed in the code and never taken from the request.

For search engines and AI assistants, pages carry structured data (the studio as an organisation with a catalogue of services), alongside a sitemap and an llms.txt file that describes the studio in plain words.

~/digital-vision/work/security.md

Security and privacy

Both form handlers have automated tests that run the bot checks, the validation and the server-side checks end to end.

  • No cookies. The site sets none. The only thing stored in the browser is a game's best score, kept on the visitor's own device.
  • Cookieless analytics. Page views are counted with Vercel Web Analytics, which does not use cookies, so there is no consent banner to click through.
  • Headers on every response: content-type sniffing off, a strict referrer policy, camera, microphone, location and payment access switched off, framing limited to the site itself, and HTTPS enforced.
  • Bot protection on the forms: a hidden field bots fill in and a check that drops anything sent faster than a person can type.
  • Uploads are checked on the server: an allowed list of document types, a size cap, and file names cleaned before anything is attached.
~/digital-vision/work/hosting.md

Hosting and delivery

The site runs on Vercel's edge network. It is deployed from the command line from one folder rather than on every push, so a change goes live only when it is meant to, and is then checked on the live address. The domain stays registered at Wix, with its DNS pointing to Vercel.

Fonts are self-hosted, split into language subsets and preloaded where they matter, so no visitor's browser calls out to a font service. Font files are cached for a year because their names change whenever they do; pages themselves are revalidated on every visit, so a deploy shows at once.

A single routing table gives every page a clean address, sends retired pages to their replacements with permanent redirects, and serves a styled 404 for anything else.

~/digital-vision/work/next.md

Got something like this?

Tell me what you need and I'll tell you what it would take.

More work →