How designsystems.surf is designed

Overview

designsystems.surf presents a mixed light and dark surface treatment in the captured pages. The system is anchored by #000000, #ffffff, and #f5f5f5, with typography led by System, Inter, and Ibm Plex Mono. The guide below names reusable design roles only where the captured evidence supports them.

The reference set uses representative captured pages. It is a design reference, not a claim about the site's private source code or a complete responsive specification.

Design tokens

The token names are practical labels for the recorded values. They are not claims about the source site's variable names.

Colors

Typography

Spacing

Shape and depth

The captured pages use 0px none 16px, 0px none 100px, 0px none 24px, 0px none 12px, 0px none 32px, 0px none 10px, 0px none 8px, and 0px none 200px border treatments. Recorded gradients include radial-gradient(50% 50%, rgb(0, 0, 0) 0%, rgb(0, 0, 0) 100%) and radial-gradient(75% 150% at 100% 114.2%, rgb(255, 183, 15) 0%, rgb(255, 84, 0) 100%).

Colors

The visual system is mixed light and dark surface treatment. Surface colors include #000000, #ffffff, and #f5f5f5. Text colors include #0000ee. Keep image-derived colors separate from interface colors.

Typography

The captured type system uses System, Inter, and Ibm Plex Mono. The table records measured size, weight, leading, and tracking where available; it does not establish licensing or a complete fallback stack.

Layout

The captured pages use values such as 124px 0px 0px, 100px 0px 0px, 16px, 16px 16px 16px 20px, and 124px 22px 32px for padding and margin. These are measured usages, not a resolved scale. The available evidence does not establish container widths, grid rules, or breakpoints.

Visual language

The captured visual language is mixed light and dark surface treatment. Surface treatment centers on #000000, #ffffff, #f5f5f5, and #fafafa. Depth is supported by the returned gradients.

Components and states

The captured pages include repeated styling on <a>, <div>, <button>, <p>, <h1>, <h2>, <span>, and <ul> elements. The evidence does not identify reusable component boundaries or interaction states. Treat loading, focus, hover, pressed, error, and disabled states as implementation work to validate rather than as captured facts.

Responsive behavior

The captured token set does not establish breakpoint values or mobile behavior. Validate stacking, navigation changes, image treatment, and type scaling against the representative captures before implementing a responsive adaptation.

Practical implementation guidance

• Preserve the mixed light/dark surface relationship and the measured type hierarchy before adding decorative treatment.
• Start from the returned typography, spacing, color, and border values; name any new scale or semantic role as an adaptation rather than as a source fact.
• Keep the captured font families separate from licensing decisions.
• Use screenshots to validate component anatomy, responsive behavior, focus treatment, and motion before shipping.
• Avoid introducing gradients or shadows beyond the captured treatment; the returned evidence includes those treatments.

Scope note

The guide uses representative captured pages. The evidence supports the values and observations above; it does not establish component semantics, interaction states, motion timing, breakpoint rules, font licensing, or a complete source stylesheet.