Vibeshots
← Sites

Hubtown

hubtown.co.in
Hubtown website, gallery screenshot

Gallery screenshot, saved 2026-10-24

How it’s built

Layout
Dark blue scene inside large inset rectangular panel; duplicated scene outside may be gallery framing. Wordmark upper-left, angular nav upper-right. Luminous cube floats over reflective plane between dark landforms. Short vertical values left; centered lower headline/support/action; bottom sound/chat controls.
Type
Small squared geometric uppercase brand; centered uppercase sans headline with tracking; tiny muted support/nav/footer. Exact metrics unknown.
Color and surface
Deep navy/black, electric blue and white. Thin panel/control borders. Outer duplicated scene not page background.
Components
Inset hero, identity/nav, central cube scene, side values, centered message/action, bottom utility bar.

What makes it work

  • Contained dark panel
  • One luminous central object
  • Peripheral index/nav and lower centered message/action
On a new subjectFor coastal flood warning, stage one luminous alert marker above reflective ground in contained hero, compact nav, side alert categories, and core preparedness message/action below; replace cube and property language.

Live behavior

Today
The later live frames show a dark navy and bright blue scene with a luminous geometric structure, reflective surface, layered hills, Hubtown wordmark, navigation, a list of six short labels, headline and supporting text, and edge controls for projects, sound, scrolling, and chat. Tablet and mobile frames rearrange the image, copy, navigation, and controls.
Responsive
Direct paired viewport measurements are 1440×1000 desktop, 768×1024 tablet, and 390×844 mobile. All six measurements report document dimensions equal to the viewport and scroll_y=0, including the state labelled desktop-scroll. Tablet and mobile show different copy wrapping and control arrangements than the desktop frame. Discrete snapshots do not establish responsive breakpoints or the complete page layout.
Scroll
The state named desktop-scroll is paired with scroll_y=0 and a document height equal to viewport height. Its image remains on the hero. No actual scroll movement or scroll-driven behavior is evidenced.

More like this