Vibeshots
← Sites

WHY Zero

why.zero.university
WHY Zero website, gallery screenshot

Gallery screenshot, saved 2026-10-24

How it’s built

Layout
A green-blue watery surround frames a large rounded, white-bordered inset. Inside, a luminous storybook meadow has a pool, flowers, small ruins/columns and stylized vegetation. One green hand enters at upper left and a human hand from lower right reaches into the scene. “zero” is centered; a thin status gauge and -75 B2 appear near top, 100 XP badge upper-right, and Join Beta plus menu pill at bottom center. Outer surround may be gallery composition.
Type
Large lowercase black sans “zero” with slight dimensional shadow; tiny status labels and compact control text. Exact type metrics unknown.
Color and surface
Bright sky/water, greens, flower pink and white; darker teal outside; pale rounded frame, off-white and black UI pills.
Components
Immersive scene, two hands, center identity, top gauge/status, XP badge, bottom beta action and menu. Function not proven.

What makes it work

  • Luminous environmental scene and central short dark identity.
  • Pale bounded field with small peripheral status elements and a low compact pill action group.
On a new subjectFor an independent music discovery service, use an original luminous miniature soundscape, a short dark central identity and compact lower browsing actions. Retain peripheral interface restraint; include progress only if real. Keep external hands and watery mockup setting outside the required website design.

Live behavior

Today
The recovered browser frames show an introductory interaction screen: a full-viewport mottled aquatic green surface, a centered small white monospaced instruction, a bright circular trace and a distorted green hand. The gallery may be a composed promotional image; its framing is not assumed to be the live page.
Responsive
The tablet capture retains the textured green full-screen field and centered instruction, while the white trace and hand are in different visible phases. The capture stopped before a phone state; responsive behavior beyond these partial introductory views remains unknown.
Scroll
The scroll-labeled capture reports scrollY 0 and a viewport-height document. The hand has moved away, but the still cannot identify whether this resulted from time, pointer movement or the attempted scroll.

More like this