About this template

Before rebuilding a 404 page for an education or community brand, read Fun 404 Page: the composition and the specification behind it are both here. The page's own headline reads “Oops, something went wrong!”, and the composition is built around those exact words. The colour scheme is bright orange #FF8233 underneath, and the page is set in Inter. Delivery is React and Tailwind CSS, captured at 1664x1248 so the frame is fixed before any code is written. Motion is limited to 500ms transitions, cubic-bezier(0.16,1,0.3,1) and a looping video bed. Start from the captured brief, then edit the 404 page rather than rebuilding it from scratch.

Designed for

  • In-house squads extending this 404 page who need 22vh sections and 200px spacing steps carried into the new blocks unchanged.
  • Studio leads who run several projects at once will use this 404 page as the pattern every other page copies.
  • This 404 page serves founders who need one screen of proof that education copy can carry 10s of looping video.

What's included

  • A bar with nothing spare. A short run of links and a single action sit over the 404 page, held at 22vh sections and 200px spacing steps so the bar never competes with the composition behind it. The bar sits over the 1664x1248 composition without a background of its own, so the media runs edge to edge underneath it.
  • A grid, not a text run. The grid does the reading order for you: panels of equal weight, one idea each, set in Inter at a small size so the structure stays visible. Spacing between panels is one value, which is what keeps a dense grid from looking crowded.
  • Links before the action. The mobile menu is part of the brief, so the collapsed state is designed rather than improvised. Give the wordmark no more room than its type needs.
  • Measured against the viewport. The layout works on absolute values rather than ratios: 22vh sections, 200px spacing steps, 500ms transitions and cubic-bezier(0.16,1,0.3,1) easing. Each value maps to one job: a type step, a gap, a radius or a transition.

Motion & interaction

The whole animation budget

Every state change in the specification has a duration attached: transitions settle around 500ms on cubic-bezier(0.16,1,0.3,1). Nothing is left at the browser default, which is why the page feels authored rather than animated. One value is reused across the controls, so their timing cannot drift apart.

Feedback on the controls

The interactive layer is small and predictable: hover states on the buttons and links rather than on every card. Everything else stays still, which keeps the emphasis on the composition. The states are named in the brief, so the page does not depend on a hover-effect library. Keep the interactive layer small.

How the 404 page reflows

Responsive here means the scale changes, not the hierarchy: the scale is fluid rather than stepped, the section is held at 22vh and the navigation collapses into a mobile menu. Text stays above the fold, controls stay large enough to tap, and reduced motion is honoured. Width changes the measurements, not the reading path.

How Fun 404 Page sequences the first read

A feature-led layout lists what the product does; this one routes the reader to a single decision. The route is visible in navigation, the announcement badge, the stats row, the card grid and the background clip and in how 22vh sections and 200px spacing steps space them. A education reader gets the offer before the options.

What to change first in Fun 404 Page

Where a theme hands you components, this brief hands you a composition: 22vh sections, 200px spacing steps, 500ms transitions and cubic-bezier(0.16,1,0.3,1) easing and a media frame, with the subject left to you. Set the new copy at the same display size and re-check the contrast before you add anything.

Frequently asked questions

What can I do with the Fun 404 Page brief once I have it?

Everything quoted on the page comes from the captured 6,085-character brief rather than from a description written afterwards. That is why the numbers and the prose agree.

What do I get when I copy the Fun 404 Page brief?

It is a build brief rather than a mood description: it names the composition at 1664x1248, the spacing and the motion values. Nothing in it treats the rendered image as the source of truth.

How much of Fun 404 Page depends on React and Tailwind CSS?

Fun 404 Page was built in React and Tailwind CSS, and the entry says so for provenance. The brief describes positions, sizes and timings, so it rebuilds in any framework that can set type and place elements.

Build it in Studio

Start with the reference, then adapt the content and visual details in Studio.